-
Notifications
You must be signed in to change notification settings - Fork 27
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
Android App icon indicates photos not uploaded, but they appear on the web #348
Comments
Hi! |
Thanks. So what I ended up doing was clearing my appdata folder and signing out of immich on my phone. When I signed back in, all photos just showed an empty cloud, indicating in the cloud only, even though they are definitely on my phone. So I restarted my phone. Now the photos seem to be uploaded, with the proper clouds with check marks in them. The only weird thing that remains is the Total versus Backup is still off by 54, even though they were in-sync before as I recall. |
Me and my wife have the same problem. Sometimes in between the crossed out cloud and different numbers for total and backup |
Had mined fixed, but as soon as I took more photos, it did it again. Photos are definitely uploaded, but show a cloud with a line through it. I don't think this is a problem specific to the AIO container. Probably need to post on the main github page (if there isn't already an issue for this). |
Same issue here. Some photos are crossed out clouds, some are instantly up and no indicator issue. Direct connection, over local wifi. |
Not sure if this is an issue for the main app GitHub or not. I'll start here...
For the past couple weeks the Android app shows none of the latest photos have been uploaded (cloud icon with a line through it). But if I look on the web, the photos have been uploaded. In the backup setting on the app, the Total and Backup numbers have been in-sync for months, but now Total is 7374 and Backup is 7428. I stay on top of the updates as they come out. Just updated to version 1.102.3.
Thanks!
The text was updated successfully, but these errors were encountered: