You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the existing issues, both open and closed, to make sure this is not a duplicate report.
Yes
The bug
Hello,
when locking a photo and then deleting it, it will arrive in the trash as expected. However it is not possible to recover it from there. Trying this just keeps the image in the trash.
I am currently unable to test on other platforms, but the issue is happening on Android with the 1.133.0 release
The OS that Immich Server is running on
Debian
Version of Immich Server
1.133.0
Version of Immich Mobile App
1.133.0
Platform with the issue
Server
Web
Mobile
Your docker-compose.yml content
Unable to retrieve ATM and probably unrelated to the issue
Your .env content
Unable to retrieve ATM and probably unrelated to the issue
Reproduction steps
on Android lock a photo
Delete it
go to Immich's trashbin and try to recover/restore it
The image stays in the trashbin.
Relevant log output
Additional information
No response
The text was updated successfully, but these errors were encountered:
I have searched the existing issues, both open and closed, to make sure this is not a duplicate report.
The bug
Hello,
when locking a photo and then deleting it, it will arrive in the trash as expected. However it is not possible to recover it from there. Trying this just keeps the image in the trash.
I am currently unable to test on other platforms, but the issue is happening on Android with the 1.133.0 release
The OS that Immich Server is running on
Debian
Version of Immich Server
1.133.0
Version of Immich Mobile App
1.133.0
Platform with the issue
Your docker-compose.yml content
Unable to retrieve ATM and probably unrelated to the issue
Your .env content
Reproduction steps
The image stays in the trashbin.
Relevant log output
Additional information
No response
The text was updated successfully, but these errors were encountered: