I
Immich5d ago
xslrx

Sync on iphone xr does not work since upgrade to 1.142.0

Hi. It is as the title says. After logging out and back in, selecting the Recents album for sync, new photos remain unsynced. In Immich app, I can still see photos that are already on the server. But new photos on the phone remain unsynced and show a crossed out cloud. This is the case also on another iphone 12 (on ios 26) syncing to the same server. Hashed file count in app matches local file count (704). Immich app: 1.143.1 Immich server: 1.143.1 ios version: 18.7 Based on other posts, i've tried the following without success: - logging out and back in - reset sqlite database Server and app logs are attached. Server upgrade path involved breaking releases. I followed the steps noted for breaking changes according to github.
1.143.1 am 24. Sept. 2025 installiert
1.142.0 am 14. Sept. 2025 installiert
1.137.0 am 14. Sept. 2025 installiert
1.136.0 am 14. Sept. 2025 installiert
1.133.0 am 14. Sept. 2025 installiert
1.143.1 am 24. Sept. 2025 installiert
1.142.0 am 14. Sept. 2025 installiert
1.137.0 am 14. Sept. 2025 installiert
1.136.0 am 14. Sept. 2025 installiert
1.133.0 am 14. Sept. 2025 installiert
7 Replies
Immich
Immich5d ago
:wave: Hey @xslrx, 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. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy). 6. :blue_square: 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.
Alex Tran
Alex Tran5d ago
Can you post the mobile app logs? Are you using self-signed cert?
xslrx
xslrxOP5d ago
Hi @Alex Tran . Sure, here's the mobile log
xslrx
xslrxOP5d ago
I am using a self signed cert. Mobile app was asked to allow self signed cert
Alex Tran
Alex Tran5d ago
The new upload mechanism doesn’t work with self signed cert at the moment
xslrx
xslrxOP5d ago
aha. that explains it! after your question, i could get sync working via syncing directly against the ip of the server which doesn't have ssl i'll keep an eye out for this fix in future releases. thanks!
Immich
Immich5d ago
This thread has been closed. To re-open, use the button below.

Did you find this page helpful?