#Error in runInIsolateGentle for remote-sync in iOS app 2.7.5 build.256 on iOS 26.5

1 messages · Page 1 of 1 (latest)

safe jacinth
#

Since a few days I am receiving below errors (within the iOS app logs) and sync does not work anymore:
Error in runInIsolateGentle for remote-sync

When drilling down, the details show:
Null check operator used on a null value

Source (From) shows IsoLateLogger

and the Stack Trace reports:
#0 SyncMemoryV1.fromJson (package:openapi/model/sync_memory_v1.dart:148)
#1 SyncApiRepository._parseLines (package:immich_mobile/infrastructure/repositories/sync_api.repository.dart:139)
#2 SyncApiRepository.streamChanges (package:immich_mobile/infrastructure/repositories/sync_api.repository.dart:111) <asynchronous suspension>
#3 SyncStreamService.sync (package:immich_mobile/domain/services/sync_stream.service.dart:85) <asynchronous suspension>
#4 runInIsolateGentle.<anonymous closure>.<anonymous closure> (package:immich_mobile/utils/isolate.dart:56) <asynchronous suspension>
#5 runInIsolateGentle.<anonymous closure> (package:immich_mobile/utils/isolate.dart:36) <asynchronous suspension>
#6 WorkerImpl._anotherIsolate.<anonymous closure> (package:worker_manager/src/worker/worker_io.dart:106) <asynchronous suspension>

OS the Immich Server is running on:
Ubuntu 26 server

Version of Immich Server:
2.7.5

Version of Immich Mobile App:
2.7.5 build.256

Platform with the issue:
mobile

Device make and model:
iPhone 17 pro, iOS 26.5

Reproduction:
deleted iOS app
also set back SQLite database in iOS app

Access:
test1 (usual connection): using access through netbird (cloud) and therefor using netbird IP
test2: via local server ip (through ubiquiti teleport) -> same issue
test3: immich app on macbooc no issue via hostname.netbird.cloud:immichport

severe radishBOT
#

:wave: Hey @safe jacinth,

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

#

Checklist

I have...

  1. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time).
  2. :blue_square: read applicable release notes.
  3. :blue_square: reviewed the FAQs for known issues.
  4. :blue_square: 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. :blue_square: 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.

severe radishBOT
wispy mauve
#

I just analyzed the logs and code and reproduced it. one memory with a bad date (from an image with a date way out of range) makes the server send that memory with an empty date, and the app crashes while parsing it, which kills the whole sync. i made a bad image on my end and got the exact same crash. we will work on this issue. so one bad memory cant take down sync anymore.

safe jacinth
wispy mauve
#

appreciate it! 🙂 its not your local iphone library. its a memory on the server side (the "on this day" feature). thats also why reinstalling + resetting the app db didnt help, the bad one just re-syncs from the server every time.

it most likely got built from one of your photos that has a broken / way out of range date (bad metadata), and that photo lives on the server.

honestly you dont need to do anything the app fix will just skip it so sync keeps working. but if you wanna clear it sooner and you have db access i can hand you a quick query to find it. or in the web app, look for a photo with a wrong date, thats probably the one.