API exception when logging into Android app v1.105.1 about immich

[elliotclee]

I've been running into this as well for the past day or so.

[mmomjian]

@martin-a-barlow please post the entire docker-compose.yml and .env that you are using - don't just say "default docker-compose from repo". We need to see what version you are pulling. My guess is you are using main, not release.

@elliotclee , you can post the same if you are also having an issue, thanks!

[martin-a-barlow]

issue resolved by using release, I was using main

[bo0tzz]

@GrumpyMeow are you sure your server and client are both definitely on 1.106.1?

[alextran1502]

@elliotclee is your server on the same version?

[martin-a-barlow]

@martin-a-barlow please post the entire docker-compose.yml and .env that you are using - don't just say "default docker-compose from repo". We need to see what version you are pulling. My guess is you are using main, not release.

@elliotclee , you can post the same if you are also having an issue, thanks!

Thanks @mmomjian, I have included the docker-compose and env file. I did try from main and some older PRs, thought that maybe the mobile app may have a build referencing some older api.

I'll try some older mobile app versions as well to see.

[martin-a-barlow]

As @mmomjian predicted i was using main, I will close this issue as the problem is resolved by using release.

The reason why I got into that state is that the default docker engine installed by debian has an issue where the immich-server constantly restarts, no logs to troubleshoot, on main it works as expected, except for communication with the mobile app.

I have used the official docker binary on debian and all is working as expected. Thanks all for your speedy response.

[GrumpyMeow]

I used "main" for a while. But switched back to "release" and am now at v0.106.1. But the issue still remmains.
I hope that i don't need to ditch the database :-(

[GrumpyMeow]

I've just followed the release notes of v1.106.1.
My iOS Immich app was still at v1.105.0.. I was able to trigger the update of the iOS app by navigating to the app in the AppStore-app. app.app.app.
Anyway. Now everything is working again... Pfffff. Thank god i did NOT have to ditch the db.

[avephill]

I've just followed the release notes of v1.106.1. My iOS Immich app was still at v1.105.0.. I was able to trigger the update of the iOS app by navigating to the app in the AppStore-app. app.app.app. Anyway. Now everything is working again... Pfffff. Thank god i did NOT have to ditch the db.

I've been trying to figure this out for the last two hours and this is exactly what fixed it. The iOS app didn't auto-update and I needed to delete it and download it again to update. Thank you!

[Arcturuss]

Happened to me today when using latest release server (1.106.4) and latest app from F-droid (1.105.1)

[jrasm91]

Happened to me today when using latest release server (1.106.4) and latest app from F-droid (1.105.1)

Unless both are on 1.106 you won't be able to login.

[GRbit]

That's quit a boomer that when I use latest release and latest F-Droid app it doesn't work.
I know that F-Droid review takes quite a time, but still, maybe it makes sense to delay the release? At least in case there are breaking API changes?

[bo0tzz]

We already delayed the release this time around for the google and apple app stores to approve the app. Waiting for F-Droid is simply not feasible, since it can easily take weeks sometimes.

[GRbit]

Thank you for answering. I wasn't aware of release cycle of the project. Weeks sounds totally fine for me, but it looks like developers and community want it to be faster.

Also, the project is amazing. Thank you very much for your contribution!