-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Backup from IOS stalls after an indeterminate number of files #4868
Comments
+1. I'm confirm it. Also, i found addition problem which related current issue. When all photos is uploaded, ios app trying uploading same files (50%). But all here photos already saved on my server |
I have the same. When the upload stalled last time, i had this in the logs (the filename matches with last one it uploaded, or got to 100% with) Catch all error: PathNotFoundException: Cannot delete file, path = '/private/var/mobile/Containers/Data/Application/53F7766C-501C-4C40-B50A-E0515EE50008/tmp/.image/CA0A67DB-D081-4FED-8BE3-A3A98E7E26C8_L0_001_1700603484.737668_o_IMG_7393.HEIC' (OS Error: No such file or directory, errno = 2) - PathNotFoundException: Cannot delete file, path = '/private/var/mobile/Containers/Data/Application/53F7766C-501C-4C40-B50A-E0515EE50008/tmp/.image/CA0A67DB-D081-4FED-8BE3-A3A98E7E26C8_L0_001_1700603484.737668_o_IMG_7393.HEIC' (OS Error: No such file or directory, errno = 2) And |
1.89. Same issue. Me first time Immich user. First time iOS app to backup. It uploaded to about 100, then stalls. Wait an undeterministic amount of time, it went up ato about 125-150, and stalls again. I didn't Pause or Stop it. I let it sit overnight. Then worse comes worse. All my 355 albums (selected and wanted to backup) has gone. Backup list shows 0. Spinning wheel again. Spins for a long time without seeing the 355 albums again. Killed the app and it continue to spin. Albums never show up again after 30mins. |
@charleslcso are you using iCloud? |
Yes Alex. |
@charleslcso we haven't put in a mechanism to handle user with iCloud usage properly since I don't use it. The stalling mean the app trying to download the photo on iCloud first before uploading it to the Immich server |
@alextran1502 great to learn iCloud is not being handled. However, the other issue is that the full, manually selected albums reverted to 0. I believe that's another issue. What do ya think? I believe immich is not for iCloud users, yet. Put it this way, I have been on the side line for 2 years. During this time I got FileRun up and running. Eager to give Immich a try now. You don't know how excited I was when I see I can backup ALL my iCloud albums in 1 single Immich.app! No more icloudpd and shell script! But unfortunately my excitement died the same night. 😔😔😔 |
Handled backup iCloud asset |
The bug
I have been trying to do the initial backup from IOS to my server with about 48,000 images/videos. Even with the app in the foreground (on the Backup page), it will upload anywhere between 10 and 100 images quickly, and then stall. Sometimes, it will restart after some amount of time, but often the only way to get it to resume backing up is to click the Cancel button and then Start Backup again.
When it stalls, it has always just finished uploading a file. I have confirmed that the last file it says it uploaded is in fact in my library and displays in the UI, so it seems to be in the app. I don't see any errors or anything unusual in the server logs.
The OS that Immich Server is running on
Ubuntu 22.04.3 LTS x86_64
Version of Immich Server
v1.84.0
Version of Immich Mobile App
1.84.0 build.124
Platform with the issue
Your docker-compose.yml content
Your .env content
Reproduction steps
1. Have a large number of images to back up 2. Open the iOS app 3. Watch it back up some number of images and then stop
Additional information
Not sure if turning on more debugging on the server would help. As I mentioned, I don't see anything in the logs on the server that indicates a problem. Not sure if there is a way to get debugging out of the ios client.
This is the second time (from a completely new install) that I have experienced this problem.
The text was updated successfully, but these errors were encountered: