Apparently I have a database issue. It tries two photos and both fail with a foreign key error and then the process stops. I had deleted both photos it initially complained about, but then it complained about the next two. I fear I’m going to have to reinstall.
the log message contains coordinates and city names, you may want to redact it.
also this is a database issue in the app. what version is this? you should probably report it, but with a redacted log line before you publish where you live
I upgraded from a pre 1.32 server, and needs an update to a 1.33 to 1.36 server version and opening app once before moving to server 2.0. So it could definitely be the server database end. It does an auto migrate of server database with the proper steps.
Ever since the upgrade to 2.0 I’ve been unable to sync the photos on my phone. “Sync failed, cannot process backup” and I don’t know why.
Check Docker logs.
Apparently I have a database issue. It tries two photos and both fail with a foreign key error and then the process stops. I had deleted both photos it initially complained about, but then it complained about the next two. I fear I’m going to have to reinstall.
Same for me, but without updating the backend. Probably an app bug.
Went into the app’s logs (tap your icon in the upper right corner and choose Logs)
And in my case it’s a database issue:
SqliteException(787): while executing statement, FOREIGN KEY constraint failed, constraint failed (code 787) Causing statement: INSERT INTO “remote_exif_entity” (“asset_id”, “city”, “state”, “country”, “date_time_original”, “description”, “height”, “width”, “exposure_time”, “f_number”, “file_size”, “focal_length”, “latitude”, “longitude”, “iso”, “make”, “model”, “lens”, “orientation”, “time_zone”, “rating”, “projection_type”) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) ON CONFLICT(“asset_id”) DO UPDATE SET “city” = ?, “state” = ?, “country” = ?, “date_time_original” = ?, “description” = ?, “height” = ?, “width” = ?, “exposure_time” = ?, “f_number” = ?, “file_size” = ?, “focal_length” = ?, “latitude” = ?, “longitude” = ?, “iso” = ?, “make” = ?, “model” = ?, “lens” = ?, “orientation” = ?, “time_zone” = ?, “rating” = ?, “projection_type” = ?, parameters: ffc547f5-78ad-42b9-856b-fdd9df8f6586, placename, state, country, 2025-05-24T14:43:35.000Z, , 1440, 1920, null, null, 3850688, null, 00.0000, 00.0000, null, Apple, iPhone 16 Pro, null, 1, Europe/Brussels, null, null, placename, state, country, 2025-05-24T14:43:35.000Z, , 1440, 1920, null, null, 3850688, null, 00.0000, 00.0000, null, Apple, iPhone 16 Pro, null, 1, Europe/Brussels, null, null.
(redacted lat/long positions a bit)
I think I’m going to reinstall. This issue is over my paygrade.
the log message contains coordinates and city names, you may want to redact it.
also this is a database issue in the app. what version is this? you should probably report it, but with a redacted log line before you publish where you live
the app version is also 2.0.0 on iOS, upgraded from the previous version.
So this isn’t a database issue on the server? But one in the app?
I upgraded from a pre 1.32 server, and needs an update to a 1.33 to 1.36 server version and opening app once before moving to server 2.0. So it could definitely be the server database end. It does an auto migrate of server database with the proper steps.
yeah, it must be an app issue. log out and reinstall, and then set up the tracked albums again and it should work.