Not uploading in background on Samsung S25 Ultra.
Photos were taken at 8:43 and 8:46 app was left closed until around 9:04 didnt upload until app opened.
18 Replies
:wave: Hey @Socal_Rv14a,
Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:.
References
- Container Logs:
docker compose logs docs
- Container Status: docker ps -a docs
- Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
- Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA
Checklist
I have...
1. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time).
2. :blue_square: read applicable release notes.
3. :blue_square: reviewed the FAQs for known issues.
4. :blue_square: reviewed Github for known issues.
5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
6. :blue_square: uploaded the relevant information (see below).
7. :blue_square: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable
(an item can be marked as "complete" by reacting with the appropriate number)
Information
In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:
- Your docker-compose.yml and .env files.
- Logs from all the containers and their status (see above).
- All the troubleshooting steps you've tried so far.
- Any recent changes you've made to Immich or your system.
- Details about your system (both software/OS and hardware).
- Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h).
- The version of the Immich server, mobile app, and other relevant pieces.
- Any other information that you think might be relevant.
Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)
If this ticket can be closed you can use the /close command, and re-open it later if needed.
This shows that the upload did run. But not sure why the websocket events are processed. We stop listening to it when the app is paused :monkaHmm:
Do you have the camera album selected for backup btw?
Has to cuz when I opened the app at 9:04 it automatically works and uploads
Right, If you don't mind me asking, Can you take one now, wait for a minute and see if it uploads. And if not, share the timestamp of the events along with the app log? Before doing all these, Can you close the app completely and open it once
Ok
Just took a pic
10:08 pic was taken its now 10:10
Not uploaded yet but as soon as I open the app to get the log it will send it.
Something else happend this time. It didn't upload or find my pic when I went back to the app
I had to close the app and reopen then it started the upload process
There is something definitely weird going on here, but we have made some improvements to this in the next version of the same. I'm afraid we've to wait for it to confirm if that fixes it for you
I could see traces for multiple background works being fired at the same time when you took multiple photos in succession. This might be locking something when all of those try to sync and back things up at the same time
Ok so not sure whats going on but now its working mostly
If the app is open in the background it works now. But if I close all the open windows it will not
Which is probley how I normally run it
Alot of times I have a ton of apps opened and I do a close all which will stop this app from background uploads. Is that how its supposed to work?
Not really. It should work even when you swipe the app away from the recents screen. However, few OEMs force stop them when you swipe it away and not schedule alarms, stopping all background tasks etc. which would make the background upload
Well as of right now thats my only problem. It doesnt work when its swipped away. For andriod a big thing is to make sure it unrestricted so it will no sleep in the background which i have done so dont think thats it.
To add to this, if a device manufacturer has decided to modify stock Android to force-stop the app, WorkManager will stop working (as will JobScheduler, alarms, broadcast receivers, etc.). There is no way to work around this. Some device manufacturers do this, unfortunately, so in those cases WorkManager will stop working until the next time the app is launched.https://issuetracker.google.com/issues/113676489
I don't expect Samsung to be doing this. But most reports we've seen recently are from Samsung