Have to re-hash all assets on iOS after app upgrade
Hi, I have about 84k assets (with iCloud Photos enabled) on my iPhone. I had previously completed hashing all my assets, but after upgrading my server from
v2.2.3 to v2.3.1 and app from v2.2.3 to v2.3.0, the app indicates that only 4k assets are backed up. I now have to re-hash the remaining 80k assets.
Any tips to prevent this issue? Thanks!
My immich is deployed via Helm chart
I've checked the app log and server log, but there is no obvious error log25 Replies
:wave: Hey @瀚瀚不可愛,
Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:.
References
- Container Logs:
docker compose logs docs
- Container Status: docker ps -a docs
- Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
- Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA
Checklist
I have...
1. :ballot_box_with_check: verified I'm on the latest release(note that mobile app releases may take some time).
2. :ballot_box_with_check: read applicable release notes.
3. :ballot_box_with_check: reviewed the FAQs for known issues.
4. :ballot_box_with_check: reviewed Github for known issues.
5. :ballot_box_with_check: tried accessing Immich via local ip (without a custom reverse proxy).
6. :ballot_box_with_check: uploaded the relevant information (see below).
7. :ballot_box_with_check: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable
(an item can be marked as "complete" by reacting with the appropriate number)
Information
In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:
- Your docker-compose.yml and .env files.
- Logs from all the containers and their status (see above).
- All the troubleshooting steps you've tried so far.
- Any recent changes you've made to Immich or your system.
- Details about your system (both software/OS and hardware).
- Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h).
- The version of the Immich server, mobile app, and other relevant pieces.
- Any other information that you think might be relevant.
Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)
If this ticket can be closed you can use the /close command, and re-open it later if needed.Can you help take a screenshot of App Settings > Sync Status?
Cc @shenlong-tanwen
Yes, this. Can you share a screenshot of that page? We truncate the remote tables but not the local tables with hash
Sure! Here is the screenshot on sync status page and also backup page, and I'm quite sure I've hashed all the assets before, I even backed them up yesterday.


🧐
Here is the app log if this can help, I think the issue I'm running into is somewhat similar to what's described in this post: https://github.com/immich-app/immich/issues/22248, though I haven't encountered the problem of uploads getting stuck yet.
Something might have gone wrong or a bug that we haven’t discovered yet. So sorry about this
NVM! Interestingly, I exported the SQLite database using the
Export Database button in the sync status page, and I can see all the data for local_asset_entity is still present.
I'm not sure why the Immich app showed only 4,373 assets have been hashed.Can you help query how many doesn't have the hash information?
@瀚瀚不可愛
SELECT * FROM local_asset_entity WHERE checksum IS NULLJust want to add that this happened to me too after updating. Interestingly it doesn’t seem to have happened on first launch after updating; maybe second or third. Would my mobile logs be of any extra help?
Yes please
My hunch is that the known problem with stale cache key in the store cause the app to run other migration paths that are left in the code
Hmmm.. It seems that their checksum disappear 🙁
If that's the case, then the stale value would've caused issues already, irrespective of the update as the migration is executed on each app launch :monkaHmm:
I remember seeing some weird logic execution in that function
You should have them printed out and test different variation
Upgrading from previous version, from the same version, etc. Scenario with existing migration version or not having migration version
the "hashing took - 40738ms" is where it happened (all my files are local so hashing everything doesn't take super long). start of log should be first boot after updating.
pay attention to this call specifically
migrateStoreToSqlite method will remove all exisitng hashIt was on my second launch, too. After updating through the iOS app store, the first launch had everything (seemingly) synced up perfect.
Second launch started completely reuploading all photos/etc.
**rehashing - I’ve been told they won’t be reuploaded.
Does the hash keep resetting for any of you facing the issue?
Just force-closed and re-opened on my iPhone - my assets seem stable so far.
Thanks for the update
Happy to help
Haven’t seen it reset on my end either