-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mobile app deleting photos with file manager #12692
Comments
Hello, thank you for the report, is this always reproducible? |
Yes, it is |
The photos with the exclamation mark, was it uploaded before you delete it?
…On Thu, Sep 19, 2024 at 3:26 AM CyberZeus ***@***.***> wrote:
Yes, it is
—
Reply to this email directly, view it on GitHub
<#12692 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGONL7X5ZGSTXBHBVOKX2UTZXHOYDAVCNFSM6AAAAABOHSPCMCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJZGM2DENZRGI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Yes, it was uploaded before I deleted it outside Immich |
just updated immich to 1.118.1 |
I can reproduce this on a Pixel 8 running grapheneOS by deleting photos with the native AOSP gallery app rather than with google photos. A friend can also reproduce on a samsung galaxy s22 running android 14, deleting photos from the samsung gallery app. |
The bug
There is a problem when I delete some photos from file manager, or Google Photo, in general outside Immich app, when the photo isn't yet uploaded to the server.
The photos in Immich app show an exclamation mark and you cannot do nothing with them, including delete. I want to delete those photos but I cannot, the delete button does nothing. It's really annoying.
The OS that Immich Server is running on
Pixel 8 (Android 14)
Version of Immich Server
115
Version of Immich Mobile App
115
Platform with the issue
Your docker-compose.yml content
Your .env content
Reproduction steps
...
Relevant log output
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: