Since apk v1.105.0 login/upload possible but timeline won't refresh, keeps spinning #9534
Comments
|
The app will need to finish indexing/hashing all the assets on your device (spinning circle) to show them in the app properly |
|
After hours it does not seem to be moving along in any way, still spinning. Especially the second device wasn't used with immich before and I've only added one folder with 2 photos to backup. With v1.104.0. it does take less then a minute to be ready, but with v1.105.0. it looks awfully similar to #9018 #8023 #7498 The server has 128gb RAM, backed by a 13600k and all assets are on an nvme. 110000 assets total, my account about 45k. My wifes android phone 35k assets seems to work just fine. So the problem might be specific to my account. edit: There are orphaned files in the repair section, which ironically all belong to my wifes problem-free account🤡 mobile logs since phone reboot: full mobile log |
Deathproof76
changed the title
Deathproof76
changed the title
|
I think I have the same issue. |
|
I have to correct myself when I said "v1.104.0. works perfectly on the secondary phone". It may actually finish indexing/hashing but only photos up until april are shown in the timeline. No problems in the webui. So it's likely that it's not just contained to the mobile app but in combination with the server. I will test downgrading server and app, when I can, to see if it works when both are on an older release. |
|
I'm on Android and I upgraded my server and mobile app version yesterday. Couldn't replicate this though but wondering if you tried clearing your mobile app's cache (in phone settings)? |
|
I already tried it, but it only clears the thumbnails and not the amount of assets downloaded. Error in the logs: |
|
Same here. As I said, still confused that my wifes account/mobile app (also android/Samsung on latest Oneui) works/syncs without a problem. Which seems to narrow the bug down to being account specific. @wardwygaerts did you use https://github.com/vale46n1/immich_duplicate_finder by any chance? I've tried it a week and a half before running into this, even though everything seemed fine until now. It's the only thing I can think about regarding differences between my admin account and the one my wife uses. Even though it should just analyze the photos and delete them via api request. update: used my secondary phone to log in to my wifes and also my mothers account and then back to my account. Their accounts sync without a hitch, only mine doesn't: |
|
@Deathproof76 can you check the server log to see if there is error when you sync your account? |
|
@alextran1502 doesn't look like it. The logs show the exact time my Account logged in:
Edit: I just came back home, connected to my Wi-Fi and immich uploaded the screenshot I made for you. It's visible in the web ui, but the mobile app keeps spinning and doesn't refresh 🤷 |
|
@Deathproof76 And it works fine on 1.104 APK? |
Well, yes and no. The syncing on my backup phone seems to finish on 1.104 without errors (no spinning or refresh problem), but the timeline stops last Month. I can only see photos up until April. Similar to @wardwygaerts |
|
@Deathproof76 Thank you, let me look at the stack trace to see what can be the potential issue |
|
@Deathproof76 Can you try accessing your instance over local IP on your account? |
@alextran1502 same problem. This is a log from just now. I logged in using the local IP (20:58:07) -> waited for a few minutes > still building timeline, won't go away for hours -> I then turned off WiFi -> the connection switches to mobile data (21:06:22) -> I'm able to see all photos-> but can't refresh them -> if I'd take a photo and turn wifi on, it wouldn't be added to the timeline (on mobile app), but still uploaded to the server and be visible in webui. |
|
I also tested with my local ip, but even less assets are loaded. |
|
I just uninstalled v1.105 and reinstalled v1.104. The timeline was completely build after 15seconds. |
|
@wardwygaerts what is your server version? |
1.105.1 |
|
I meet this issue too. You need to pull down refresh, then the sync state on photos will become ok . Android App version: 1.105.0 build.139 |
|
@alextran1502 I downgraded the server to v1.104.0 and everything works with apk v1.104.0 on my secondary phone (No errors in logs, indexing/caching/refreshing working, all photos visible in timeline). Also tried with apk v1.105.0 and server v1.104.0 which sadly shows the same errors as apk v1.105.0 with server v1.105.1. server v1.104.0 and apk v1.105.0 logs: what I understand so far: It's a user specific problem (my other users work without a problem on v1.105.0) and it definitely happened between v1.104.0 and v1.105.0 for both apk and server. server v1.104.0 and apk v1.104.0 logs: |
|
@alextran1502 sorry to bother you, but do you have any guidance on how I could debug this further? Or maybe a workaround? Maybe like creating a new account and migrating the assets/created and shared albums to the new account via db queries? I mean with errors like: and Isn't there a way to find out what is wrong with the user token? Maybe what it should look like and a way to modify it? (I don't know if it even is part of the problem and not just a red herring) I would love to be able to use immich on my phone again. If there's anything I can do, I'd be glad if you could tell me. |
|
@Deathproof76 Did you try with the previous mobile version? For me it works with app v1.104.0 |
Yeah, it works on my main phone when installing the v1.104.0 apk from github. But the problem is that all the already backed up photos in the selected backup albums will be re-uploaded again, creating duplicates due to #9495 (comment) as I've been using the playstore version. I'd have to create new albums and/or clear the old ones. And there's no guarantee that the next version e.g. v1.106.0 won't have the same problem. Even if it works, I'd have to duplicate and reclear the albums again for not having duplicate photos in the account. |
I also switched from the PlayStore version to the GitHub apk. The backup indeed started from scratch, but I don't have duplicates. |
|
you're right. It works just as you said 😄👍 |
|
Same problems over here with Play store version 1.105. Downgrading to 1.104 worked! 👍 |
|
Really good to know that this problem affects more than two people 👀. Makes it much more likely of it being a "true" bug and not just some isolated incident related to rare user specific shenanigans. @xs2usun you don't happen to have any logs from v1.105? |
|
Unfortunately I have not. I searched Google with the following error in the log of 1.105: ApiException 400: HTTP connection failed: POST /sync/full-sync (Inner exception: Software caused connection abort) That led me to this bug and the solution. I have similar problems with the iOS app, but I can't downgrade on iOS. |
|
@xs2usun is your server on 1.105 as well? |
Ah, this part then: |
Definitely not the only one. Been having this issue for a while now too. Details: Stack trace: |
|
@fyfrey Hi Fynn, do you have any pointer that I should look into regarding this bug? I can't seem to find a way to reproduce it. Ever |
|
I think there are two different issues mentioned here
|
|
For all of the users in this thread, are you guys connecting to your instance over dns/reverse proxy? |
#9534 (comment) I tried direct and via caddy to the same effect. And as I said the weirdest part is, that other accounts using the same instance, like if I log in using my wifes account with my phone on 1.105 for server and apk, work without a problem. |
|
By default, I connect via reverse proxy (traefik), but also tried it locally. |
|
Do all affected accounts use the stacking feature extensively? |
My server is 1.105.1. It runs as a docker container in Unraid. |
|
I've attached 3 logfiles. Timeline works on 1.104. But on 1.105 the timeline never gets updated past March 10.
Android_1_104_0_build_2138_Immich_log_2024-06-01T12_29_27.445240.log |
|
I deinstalled v1.105 on my Android phone and installed v1.104 apk. Timeline is fine again. |
To be honest I don't even know how to do that or search for stacks in immich. Does it happen automatically? Like if I'd set my phone to output raw and heic/jpeg at the same time when shooting a photo, the uploaded files will be part of a stack? If that's the case than no. If it's something that one would have to do manually then also no. |
The bug
Using the android mobile app from the playstore on a Samsung S23U: Since v1.105.0 I get weird errors where photos will get uploaded but not refreshed in the app. Tried to logout and in again via google oauth and mail/pw. But after relogin the timelime is building indefinitely.
I also tried direct ip in LAN. It somehow helps switching between Wifi and mobile Data. After doing that I'm able to see the remote photos and can upload photos but the gallery won't refresh and the backup cloud icon is crossed out*. The uploaded photos can be seen in the Webui though. I used a secondary android phone (some rooted xiaomi with a custom rom) to install v1.105.0 from github and compare with v1.104.0. due to #9495 (comment)
v1.104.0. works perfectly on the secondary phone but v1.105.0 shows the exact same issues as on the primary android phone.
*(after turning wifi off and waiting for mobile data, the "building timeline" vanishes and I can see photos but it seems to keep building in the background, down left "fotos" is still spinning)
update: I can access remote albums, which also show the correct backup status (only on server/on device and server) it seems to be mainly a problem with the timeline. I can search things and filter people/places.
Can't see any unusual in the docker logs, no warnings, errors, nothing:
The mobile logs show Key 'currentUser' not found in Store, Error while getting remote assets | ApiException 401: {"message":"Invalid user token","error":"Unauthorized","statusCode":401} , PersonService | Error while fetching curated people | ApiException 400: Socket operation failed: GET /person (Inner exception: Failed host lookup: 'immich.mydomain.com')
The OS that Immich Server is running on
docker
Version of Immich Server
v1.105.1
Version of Immich Mobile App
v1.105.0
Platform with the issue
Your docker-compose.yml content
irrelevantYour .env content
Reproduction steps
1. install apk v1.105.0 2. try to open or login 3. gallery won't refresh or stuck on timeline buildingRelevant log output
Additional information
I'm using the https://github.com/imagegenius/docker-immich monolythic dockerimage with tensorchord/pgvecto-rs:pg16-v0.2.0
The text was updated successfully, but these errors were encountered: