Error in android app while syncing
Hi everyone,
I’m having a recurring issue on the Android app where remote sync keeps failing with this error:
SqliteException(787): FOREIGN KEY constraint failed
Causing statement:
INSERT INTO memory_asset_entity ("asset_id", "memory_id") VALUES (?, ?)
ON CONFLICT("asset_id", "memory_id") DO NOTHING
parameters:
cla5838f-ef10-405e-97f3-11dffe4d4360, b3ae0974-b1ac-4e5c-9cf9-77c720f937fd
FROM DriftSyncStreamRepository
When this happens, the entire remote sync stops working, uploads fail and nothing new gets synced.
I already tried updating the Immich server with docker compose pull && docker compose up -d, but the issue is still there. I haven’t rebuilt or reset the local database yet because I don’t want to re-sync everything from scratch.
I’m running the app version 2.2.0 (build 3023), with a server on version 2.2.1 The app also says “App update is available,” but there’s no update showing on the Play Store.
Has anyone run into this before or found a fix? Could it be caused by orphaned records or a mismatch between app and server versions? I’d really like to solve it without resetting or losing sync data.
Thanks!
I’m having a recurring issue on the Android app where remote sync keeps failing with this error:
SqliteException(787): FOREIGN KEY constraint failed
Causing statement:
INSERT INTO memory_asset_entity ("asset_id", "memory_id") VALUES (?, ?)
ON CONFLICT("asset_id", "memory_id") DO NOTHING
parameters:
cla5838f-ef10-405e-97f3-11dffe4d4360, b3ae0974-b1ac-4e5c-9cf9-77c720f937fd
FROM DriftSyncStreamRepository
When this happens, the entire remote sync stops working, uploads fail and nothing new gets synced.
I already tried updating the Immich server with docker compose pull && docker compose up -d, but the issue is still there. I haven’t rebuilt or reset the local database yet because I don’t want to re-sync everything from scratch.
I’m running the app version 2.2.0 (build 3023), with a server on version 2.2.1 The app also says “App update is available,” but there’s no update showing on the Play Store.
Has anyone run into this before or found a fix? Could it be caused by orphaned records or a mismatch between app and server versions? I’d really like to solve it without resetting or losing sync data.
Thanks!
