Some Assets Ignored on Android
Hi, on the android app under backup albums I have selected DCIM which it says has 1391 photos. This is the only album selected everything else is excluded. However, it says total unique assets is 1270 but is refusing to find those 121 photos.
I have checked the immich data folder and the thumbnails and they have definitely not been uploaded and thumbnails not generated. There are 1270 files in the main data folder and 2540 in the thumbs (2 per asset).
Is this an issue that you are aware of/has been reported before?
Do you think if I run the bulk upload from the server (which also has the folder with all 1391 files) it will duplicate all the files or should it hopefully just find the missing assets to upload.
I can't see any errors in the logs to indicate anything.
Versions:
Android app version: 1.40.0 build.63 (installed from f-droid)
Server version: 1.40.0 (running in docker)
Compose file and .env (see attached)
Many thanks in advance and let me know if there's any other information I can provide.
15 Replies
If you just chose one DCIM folder to upload, does it show the number of asset correctly?
Can you help take a screenshot of the album selection page?
I think I only have one DCIM folder selected. (Sorry about the blur)
You don't have to exclude the rest, instead just choose the DCIM folder to be backed up
if some of the photos in DCIM assets is in other excluded folder, it will be filtered out
that is why you are seeing the incorrect number of 1391 vs 1270
I'll try un-excluding them now although they should be separate photos and I'm almost certain there's some in DCIM that haven't been included that aren't in any of the other folders.
The reason I excluded them was because the other day I updated the mobile app, got signed out and when I logged in it then selected "Recent" which uploaded everything which I didn't want so I had to purge and restart so just excluded everything to be safe.
Will update in a min if that worked
With just "DCIM" included and nothing else selected or excluded it is the same. I force closed the app and re-opened so foreground backup would pick any changes up but still says 1270
Can you help take a screenshot again?
Took a blank picture to save needing to blur which is why there's one extra asset in each - but shows that it is working as expected on the most part
My only thoughts are:
- purge and restart to see if it happens again (could indicate something wrong with those images)
- purge and restart with almost default docker/.env (I modified to run as non-root but haven't seen any issues with microservers/reverse-geocoding dump other people have run into with that)
- bulk upload that whole folder from my computer and hope just those missing files are ingested
Another thought is that DCIM folder is synced using syncthing but that hasn't seemed to be an issue before
Can you help performing the first option? If it doesn’t help it would be a bug then, can you then help open an issue so we can track it?
If you choose other folder does it display correctly?
As in include another folder as well as DCIM?
I selected "Download" here and it backed up as expected taking the total to 1272 assets
Will reset now and update once everything has re-backed up. If they are still missing I'll raise a bug report
It's currently backing up all the assets but it says its found 1392 which is all of them (yay!)
but - after the initial reset the app was still at 1270 assets. I then deleted all storage from android settings for the app and then when I re-signed in it found all the assets.
I wonder if just deleting the storage of the app before resetting would've made it find the assets. This could indicate there was some corrupt or leftover state that was preventing it from seeing those pictures before but I cannot test that now
Hmm I think there might be some duplicated asset in the folder
I haven't seen any duplicates in the folder but it's possible. But good to know clearing the storage/cache resolved it if this happens to anyone else and may prevent having to reset everything
I'm not sure if there's enough to go on to raise a bug for it - what do you think?
I agree, if we have more users with similar issue we will take a look into this
Thank you very much for your rapid support and for all the hard work that goes into this project!!
No problem 🙂 I am glad you are enjoying it