immich-app/immich
1
0
Fork 0
mirror of https://github.com/immich-app/immich.git synced 2026-02-05 08:41:28 +03:00
Code Issues 26 Packages Projects Releases 10 Wiki Activity

iOS app stops uploading/backup as soon as it leaves the foreground #1056

New Issue
Closed
opened 2026-02-05 00:14:37 +03:00 by OVERLORD · 13 comments
OVERLORD commented 2026-02-05 00:14:37 +03:00
Owner
Copy Link

Originally created by @nickian on GitHub (Jul 3, 2023).

The bug

I have 4,843 photos/videos to back up, so it would take a while. However, anytime the screen turns off, I jump to another app, or even pull down the notification center, the backup stops in its tracks and restarts from the beginning.

I have automatic background enabled and the permissions are fully enabled in settings. This doesn't make a difference. It does not upload anything in the background.

You can see what I mean in this screen recording: https://nick.nyc3.digitaloceanspaces.com/immich.mov

The OS that Immich Server is running on

Ubuntu 22.04

Version of Immich Server

v1.65.0

Version of Immich Mobile App

v1.65.0

Platform with the issue

  • Server
  • Web
  • Mobile

Your docker-compose.yml content

version: "3.8"

services:
  immich-server:
    container_name: immich_server
    image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
    command: [ "start.sh", "immich" ]
    volumes:
      - ${UPLOAD_LOCATION}:/usr/src/app/upload
    env_file:
      - .env
    depends_on:
      - redis
      - database
      - typesense
    restart: always

  immich-microservices:
    container_name: immich_microservices
    image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
    command: [ "start.sh", "microservices" ]
    volumes:
      - ${UPLOAD_LOCATION}:/usr/src/app/upload
    env_file:
      - .env
    depends_on:
      - redis
      - database
      - typesense
    restart: always

  immich-machine-learning:
    container_name: immich_machine_learning
    image: ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release}
    volumes:
      - model-cache:/cache
    env_file:
      - .env
    restart: always

  immich-web:
    container_name: immich_web
    image: ghcr.io/immich-app/immich-web:${IMMICH_VERSION:-release}
    env_file:
      - .env
    restart: always

  typesense:
    container_name: immich_typesense
    image: typesense/typesense:0.24.1@sha256:9bcff2b829f12074426ca044b56160ca9d777a0c488303469143dd9f8259d4dd
    environment:
      - TYPESENSE_API_KEY=${TYPESENSE_API_KEY}
      - TYPESENSE_DATA_DIR=/data
    logging:
      driver: none
    volumes:
      - tsdata:/data
    restart: always

  redis:
    container_name: immich_redis
    image: redis:6.2-alpine@sha256:70a7a5b641117670beae0d80658430853896b5ef269ccf00d1827427e3263fa3
    restart: always

  database:
    container_name: immich_postgres
    image: postgres:14-alpine@sha256:28407a9961e76f2d285dc6991e8e48893503cc3836a4755bbc2d40bcc272a441
    env_file:
      - .env
    environment:
      POSTGRES_PASSWORD: ${DB_PASSWORD}
      POSTGRES_USER: ${DB_USERNAME}
      POSTGRES_DB: ${DB_DATABASE_NAME}
      PG_DATA: /var/lib/postgresql/data
    volumes:
      - pgdata:/var/lib/postgresql/data
    restart: always

  immich-proxy:
    container_name: immich_proxy
    image: ghcr.io/immich-app/immich-proxy:${IMMICH_VERSION:-release}
    environment:
      # Make sure these values get passed through from the env file
      - IMMICH_SERVER_URL
      - IMMICH_WEB_URL
    ports:
      - 2283:8080
    depends_on:
      - immich-server
      - immich-web
    restart: always

volumes:
  pgdata:
  model-cache:
  tsdata:

Your .env content

###################################################################################
# Database
###################################################################################

# NOTE: The following four database variables support Docker secrets by adding a *_FILE suffix to the variable name
# See the docker-compose documentation on secrets for additional details: https://docs.docker.com/compose/compose-file/compose-file-v3/#secrets
DB_HOSTNAME=immich_postgres
DB_USERNAME=postgres
DB_PASSWORD=postgres
DB_DATABASE_NAME=immich

# Optional Database settings:
# DB_PORT=5432

###################################################################################
# Redis
###################################################################################

REDIS_HOSTNAME=immich_redis

# REDIS_URL will be used to pass custom options to ioredis.
# Example for Sentinel
# {"sentinels":[{"host":"redis-sentinel-node-0","port":26379},{"host":"redis-sentinel-node-1","port":26379},{"host":"redis-sentinel-node-2","port":26379}],"name":"redis-sentinel"}
# REDIS_URL=ioredis://eyJzZW50aW5lbHMiOlt7Imhvc3QiOiJyZWRpcy1zZW50aW5lbDEiLCJwb3J0IjoyNjM3OX0seyJob3N0IjoicmVkaXMtc2VudGluZWwyIiwicG9ydCI6MjYzNzl9XSwibmFtZSI6Im15bWFzdGVyIn0=

# Optional Redis settings:

# Note: these parameters are not automatically passed to the Redis Container
# to do so, please edit the docker-compose.yml file as well. Redis is not configured
# via environment variables, only redis.conf or the command line

# REDIS_PORT=6379
# REDIS_DBINDEX=0
# REDIS_USERNAME=
# REDIS_PASSWORD=
# REDIS_SOCKET=

###################################################################################
# Upload File Location
#
# This is the location where uploaded files are stored.
###################################################################################

UPLOAD_LOCATION=/home/nick/photos


###################################################################################
# Typesense
###################################################################################
TYPESENSE_API_KEY=some-random-text
# TYPESENSE_ENABLED=false
# TYPESENSE_URL uses base64 encoding for the nodes json.
# Example JSON that was used:
# [
#      { "host": "typesense-1.example.net", "port": "443", "protocol": "https" },
#      { "host": "typesense-2.example.net", "port": "443", "protocol": "https" },
#      { "host": "typesense-3.example.net", "port": "443", "protocol": "https" },
# ]
# TYPESENSE_URL=ha://WwogIHsgImhvc3QiOiAidHlwZXNlbnNlLTEuZXhhbXBsZS5uZXQiLCAicG9ydCI6ICI0NDMiLCAicHJvdG9jb2wiOiAiaHR0cHMiIH0sCiAgeyAiaG9zdCI6ICJ0eXBlc2Vuc2UtMi5leGFtcGxlLm5ldCIsICJwb3J0IjogIjQ0MyIsICJwcm90b2NvbCI6ICJodHRwcyIgfSwKICB7ICJob3N0IjogInR5cGVzZW5zZS0zLmV4YW1wbGUubmV0IiwgInBvcnQiOiAiNDQzIiwgInByb3RvY29sIjogImh0dHBzIiB9Cl0=

###################################################################################
# Reverse Geocoding
#
# Reverse geocoding is done locally which has a small impact on memory usage
# This memory usage can be altered by changing the REVERSE_GEOCODING_PRECISION variable
# This ranges from 0-3 with 3 being the most precise
# 3 - Cities > 500 population: ~200MB RAM
# 2 - Cities > 1000 population: ~150MB RAM
# 1 - Cities > 5000 population: ~80MB RAM
# 0 - Cities > 15000 population: ~40MB RAM
####################################################################################

# DISABLE_REVERSE_GEOCODING=false
# REVERSE_GEOCODING_PRECISION=3

####################################################################################
# WEB - Optional
#
# Custom message on the login page, should be written in HTML form.
# For example:
# PUBLIC_LOGIN_PAGE_MESSAGE="This is a demo instance of Immich.<br><br>Email: <i>demo@demo.de</i><br>Password: <i>demo</i>"
####################################################################################

PUBLIC_LOGIN_PAGE_MESSAGE=

####################################################################################
# Alternative Service Addresses - Optional
#
# This is an advanced feature for users who may be running their immich services on different hosts.
# It will not change which address or port that services bind to within their containers, but it will change where other services look for their peers.
# Note: immich-microservices is bound to 3002, but no references are made
####################################################################################

IMMICH_WEB_URL=http://immich-web:3000
IMMICH_SERVER_URL=http://immich-server:3001
IMMICH_MACHINE_LEARNING_URL=http://immich-machine-learning:3003

####################################################################################
# Alternative API's External Address - Optional
#
# This is an advanced feature used to control the public server endpoint returned to clients during Well-known discovery.
# You should only use this if you want mobile apps to access the immich API over a custom URL. Do not include trailing slash.
# NOTE: At this time, the web app will not be affected by this setting and will continue to use the relative path: /api
# Examples: http://localhost:3001, http://immich-api.example.com, etc
####################################################################################

#IMMICH_API_URL_EXTERNAL=http://localhost:3001

###################################################################################
# Immich Version - Optional
#
# This allows all immich docker images to be pinned to a specific version. By default,
# the version is "release" but could be a specific version, like "v1.59.0".
###################################################################################

#IMMICH_VERSION=

Reproduction steps

1. Hit the start backup button, starts uploading
2. Change app or open notification center
3. Backup stops (or if automatic foreground backup is enabled, it simply restarts from the first image again)

Additional information

No response

Originally created by @nickian on GitHub (Jul 3, 2023). ### The bug I have 4,843 photos/videos to back up, so it would take a while. However, anytime the screen turns off, I jump to another app, or even pull down the notification center, the backup stops in its tracks and restarts from the beginning. I have automatic background enabled and the permissions are fully enabled in settings. This doesn't make a difference. It does not upload anything in the background. You can see what I mean in this screen recording: https://nick.nyc3.digitaloceanspaces.com/immich.mov ### The OS that Immich Server is running on Ubuntu 22.04 ### Version of Immich Server v1.65.0 ### Version of Immich Mobile App v1.65.0 ### Platform with the issue - [ ] Server - [ ] Web - [X] Mobile ### Your docker-compose.yml content ```YAML version: "3.8" services: immich-server: container_name: immich_server image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release} command: [ "start.sh", "immich" ] volumes: - ${UPLOAD_LOCATION}:/usr/src/app/upload env_file: - .env depends_on: - redis - database - typesense restart: always immich-microservices: container_name: immich_microservices image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release} command: [ "start.sh", "microservices" ] volumes: - ${UPLOAD_LOCATION}:/usr/src/app/upload env_file: - .env depends_on: - redis - database - typesense restart: always immich-machine-learning: container_name: immich_machine_learning image: ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release} volumes: - model-cache:/cache env_file: - .env restart: always immich-web: container_name: immich_web image: ghcr.io/immich-app/immich-web:${IMMICH_VERSION:-release} env_file: - .env restart: always typesense: container_name: immich_typesense image: typesense/typesense:0.24.1@sha256:9bcff2b829f12074426ca044b56160ca9d777a0c488303469143dd9f8259d4dd environment: - TYPESENSE_API_KEY=${TYPESENSE_API_KEY} - TYPESENSE_DATA_DIR=/data logging: driver: none volumes: - tsdata:/data restart: always redis: container_name: immich_redis image: redis:6.2-alpine@sha256:70a7a5b641117670beae0d80658430853896b5ef269ccf00d1827427e3263fa3 restart: always database: container_name: immich_postgres image: postgres:14-alpine@sha256:28407a9961e76f2d285dc6991e8e48893503cc3836a4755bbc2d40bcc272a441 env_file: - .env environment: POSTGRES_PASSWORD: ${DB_PASSWORD} POSTGRES_USER: ${DB_USERNAME} POSTGRES_DB: ${DB_DATABASE_NAME} PG_DATA: /var/lib/postgresql/data volumes: - pgdata:/var/lib/postgresql/data restart: always immich-proxy: container_name: immich_proxy image: ghcr.io/immich-app/immich-proxy:${IMMICH_VERSION:-release} environment: # Make sure these values get passed through from the env file - IMMICH_SERVER_URL - IMMICH_WEB_URL ports: - 2283:8080 depends_on: - immich-server - immich-web restart: always volumes: pgdata: model-cache: tsdata: ``` ### Your .env content ```Shell ################################################################################### # Database ################################################################################### # NOTE: The following four database variables support Docker secrets by adding a *_FILE suffix to the variable name # See the docker-compose documentation on secrets for additional details: https://docs.docker.com/compose/compose-file/compose-file-v3/#secrets DB_HOSTNAME=immich_postgres DB_USERNAME=postgres DB_PASSWORD=postgres DB_DATABASE_NAME=immich # Optional Database settings: # DB_PORT=5432 ################################################################################### # Redis ################################################################################### REDIS_HOSTNAME=immich_redis # REDIS_URL will be used to pass custom options to ioredis. # Example for Sentinel # {"sentinels":[{"host":"redis-sentinel-node-0","port":26379},{"host":"redis-sentinel-node-1","port":26379},{"host":"redis-sentinel-node-2","port":26379}],"name":"redis-sentinel"} # REDIS_URL=ioredis://eyJzZW50aW5lbHMiOlt7Imhvc3QiOiJyZWRpcy1zZW50aW5lbDEiLCJwb3J0IjoyNjM3OX0seyJob3N0IjoicmVkaXMtc2VudGluZWwyIiwicG9ydCI6MjYzNzl9XSwibmFtZSI6Im15bWFzdGVyIn0= # Optional Redis settings: # Note: these parameters are not automatically passed to the Redis Container # to do so, please edit the docker-compose.yml file as well. Redis is not configured # via environment variables, only redis.conf or the command line # REDIS_PORT=6379 # REDIS_DBINDEX=0 # REDIS_USERNAME= # REDIS_PASSWORD= # REDIS_SOCKET= ################################################################################### # Upload File Location # # This is the location where uploaded files are stored. ################################################################################### UPLOAD_LOCATION=/home/nick/photos ################################################################################### # Typesense ################################################################################### TYPESENSE_API_KEY=some-random-text # TYPESENSE_ENABLED=false # TYPESENSE_URL uses base64 encoding for the nodes json. # Example JSON that was used: # [ # { "host": "typesense-1.example.net", "port": "443", "protocol": "https" }, # { "host": "typesense-2.example.net", "port": "443", "protocol": "https" }, # { "host": "typesense-3.example.net", "port": "443", "protocol": "https" }, # ] # TYPESENSE_URL=ha://WwogIHsgImhvc3QiOiAidHlwZXNlbnNlLTEuZXhhbXBsZS5uZXQiLCAicG9ydCI6ICI0NDMiLCAicHJvdG9jb2wiOiAiaHR0cHMiIH0sCiAgeyAiaG9zdCI6ICJ0eXBlc2Vuc2UtMi5leGFtcGxlLm5ldCIsICJwb3J0IjogIjQ0MyIsICJwcm90b2NvbCI6ICJodHRwcyIgfSwKICB7ICJob3N0IjogInR5cGVzZW5zZS0zLmV4YW1wbGUubmV0IiwgInBvcnQiOiAiNDQzIiwgInByb3RvY29sIjogImh0dHBzIiB9Cl0= ################################################################################### # Reverse Geocoding # # Reverse geocoding is done locally which has a small impact on memory usage # This memory usage can be altered by changing the REVERSE_GEOCODING_PRECISION variable # This ranges from 0-3 with 3 being the most precise # 3 - Cities > 500 population: ~200MB RAM # 2 - Cities > 1000 population: ~150MB RAM # 1 - Cities > 5000 population: ~80MB RAM # 0 - Cities > 15000 population: ~40MB RAM #################################################################################### # DISABLE_REVERSE_GEOCODING=false # REVERSE_GEOCODING_PRECISION=3 #################################################################################### # WEB - Optional # # Custom message on the login page, should be written in HTML form. # For example: # PUBLIC_LOGIN_PAGE_MESSAGE="This is a demo instance of Immich.<br><br>Email: <i>demo@demo.de</i><br>Password: <i>demo</i>" #################################################################################### PUBLIC_LOGIN_PAGE_MESSAGE= #################################################################################### # Alternative Service Addresses - Optional # # This is an advanced feature for users who may be running their immich services on different hosts. # It will not change which address or port that services bind to within their containers, but it will change where other services look for their peers. # Note: immich-microservices is bound to 3002, but no references are made #################################################################################### IMMICH_WEB_URL=http://immich-web:3000 IMMICH_SERVER_URL=http://immich-server:3001 IMMICH_MACHINE_LEARNING_URL=http://immich-machine-learning:3003 #################################################################################### # Alternative API's External Address - Optional # # This is an advanced feature used to control the public server endpoint returned to clients during Well-known discovery. # You should only use this if you want mobile apps to access the immich API over a custom URL. Do not include trailing slash. # NOTE: At this time, the web app will not be affected by this setting and will continue to use the relative path: /api # Examples: http://localhost:3001, http://immich-api.example.com, etc #################################################################################### #IMMICH_API_URL_EXTERNAL=http://localhost:3001 ################################################################################### # Immich Version - Optional # # This allows all immich docker images to be pinned to a specific version. By default, # the version is "release" but could be a specific version, like "v1.59.0". ################################################################################### #IMMICH_VERSION= ``` ### Reproduction steps ```bash 1. Hit the start backup button, starts uploading 2. Change app or open notification center 3. Backup stops (or if automatic foreground backup is enabled, it simply restarts from the first image again) ``` ### Additional information _No response_
OVERLORD commented 2026-02-05 00:14:44 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Jul 3, 2023):

Hello, this is expected. Foreground and background upload is separated. Once the app is in the background and the background upload is enabled, the OS will schedule for the foreground task to run at a later time, usually, every 10 or 30 minutes depending on the frequency you are using the app and wether or not the phone is plugged in.

For initial upload, I recomended leaving the app stay on foreground :)

@alextran1502 commented on GitHub (Jul 3, 2023): Hello, this is expected. Foreground and background upload is separated. Once the app is in the background and the background upload is enabled, the OS will schedule for the foreground task to run at a later time, usually, every 10 or 30 minutes depending on the frequency you are using the app and wether or not the phone is plugged in. For initial upload, I recomended leaving the app stay on foreground :)
OVERLORD commented 2026-02-05 00:14:47 +03:00
Author
Owner
Copy Link

@nickian commented on GitHub (Jul 3, 2023):

I left the phone plugged in overnight and had background upload enabled. It didn't upload anything. How is this usable? You can't leave your phone on in the foreground all day to do this. Shouldn't it be able to upload while the app is open but running behind other apps? If someone calls or anything happens, it restarts from the beginning. Can't it at least pick up where it left off?

@nickian commented on GitHub (Jul 3, 2023): I left the phone plugged in overnight and had background upload enabled. It didn't upload anything. How is this usable? You can't leave your phone on in the foreground all day to do this. Shouldn't it be able to upload while the app is open but running behind other apps? If someone calls or anything happens, it restarts from the beginning. Can't it at least pick up where it left off?
OVERLORD commented 2026-02-05 00:14:50 +03:00
Author
Owner
Copy Link

@nickian commented on GitHub (Jul 3, 2023):

Even when I disable auto-screen lock (setting it to never), the app crashes after a couple of minutes of backing up in the foreground. (iOS 16.5.1)

@nickian commented on GitHub (Jul 3, 2023): Even when I disable auto-screen lock (setting it to never), the app crashes after a couple of minutes of backing up in the foreground. (iOS 16.5.1)
OVERLORD commented 2026-02-05 00:14:55 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Jul 3, 2023):

For initial backup, if you are on WIFI 5GHz band it should tackle 10000 within an hour.

Foreground backup is for incremental backup after the initial bulk import. The usability is iOS limitation, Apple doesn't let an app take all the resources and run, so it has AI built into the OS to schedule the background task, and this is something none of the developers have control over.

The upload is always starting where it is left off, meaning only the not-yet-uploaded-asset will be uploaded.

From the video you posted, it actually ran

image

The issue could be it gets to a large video that takes a while to sync and the OS only allows the background task to run for 30 seconds before killing it.

@alextran1502 commented on GitHub (Jul 3, 2023): For initial backup, if you are on WIFI 5GHz band it should tackle 10000 within an hour. Foreground backup is for incremental backup after the initial bulk import. The usability is iOS limitation, Apple doesn't let an app take all the resources and run, so it has AI built into the OS to schedule the background task, and this is something none of the developers have control over. The upload is always starting where it is left off, meaning only the not-yet-uploaded-asset will be uploaded. From the video you posted, it actually ran ![image](https://github.com/immich-app/immich/assets/27055614/3f937be3-c7b6-4cad-b573-e0b5a1ec188c) The issue could be it gets to a large video that takes a while to sync and the OS only allows the background task to run for 30 seconds before killing it.
OVERLORD commented 2026-02-05 00:15:03 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Jul 3, 2023):

Even when I disable auto-screen lock (setting it to never), the app crashes after a couple of minutes of backing up in the foreground. (iOS 16.5.1)

Is it always crashing or only crashing once, if it always crashes, can you help open a different issue and post the mobile app log? Thank you

@alextran1502 commented on GitHub (Jul 3, 2023): > Even when I disable auto-screen lock (setting it to never), the app crashes after a couple of minutes of backing up in the foreground. (iOS 16.5.1) Is it always crashing or only crashing once, if it always crashes, can you help open a different issue and post the mobile app log? Thank you
OVERLORD commented 2026-02-05 00:15:06 +03:00
Author
Owner
Copy Link

@nickian commented on GitHub (Jul 3, 2023):

Ok, I will check the log and see if I can create a separate issue. If I copy all of my photos onto my computer, then upload via the CLI, will the iPhone app be smart enough to see those photos are already uploaded and start uploading only new photos?

@nickian commented on GitHub (Jul 3, 2023): Ok, I will check the log and see if I can create a separate issue. If I copy all of my photos onto my computer, then upload via the CLI, will the iPhone app be smart enough to see those photos are already uploaded and start uploading only new photos?
OVERLORD commented 2026-02-05 00:15:09 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Jul 4, 2023):

Ok, I will check the log and see if I can create a separate issue. If I copy all of my photos onto my computer, then upload via the CLI, will the iPhone app be smart enough to see those photos are already uploaded and start uploading only new photos?

It will still upload those assets but the server will reject it, then the phone will put it into a blacklist to not upload it again in future runs. The plan is to have the same thing you describe in the future

@alextran1502 commented on GitHub (Jul 4, 2023): > Ok, I will check the log and see if I can create a separate issue. If I copy all of my photos onto my computer, then upload via the CLI, will the iPhone app be smart enough to see those photos are already uploaded and start uploading only new photos? It will still upload those assets but the server will reject it, then the phone will put it into a blacklist to not upload it again in future runs. The plan is to have the same thing you describe in the future
OVERLORD commented 2026-02-05 00:15:12 +03:00
Author
Owner
Copy Link

@srvprivate commented on GitHub (Jul 10, 2023):

So just to confirm, after reading all of this (had this issue with Synology Photos and they add a foreground "black screen" feature) there's no way around these apple security limitations to allow background? I imagine Android does fine, but as for iOS, are we saying background (unless a HUGE file) can only handle certain session limits? You mentioned 30 seconds...does that mean it runs for 30 seconds and then kills? How can we be certain that, say... I have 250 photos in a day, that I can trust the background to upload, does it tackle it throughout the day instead of just one go? (say 250 uploads in 5min). Just looking for the specifics, I know apple is being difficult on this feature and basically locks you into iCloud photos...(however my Google Photos would auto upload. Sorry for a lot here, just trying to make sure I settle on a solid Google Photos/iCloud replacement :)

@srvprivate commented on GitHub (Jul 10, 2023): So just to confirm, after reading all of this (had this issue with Synology Photos and they add a foreground "black screen" feature) there's no way around these apple security limitations to allow background? I imagine Android does fine, but as for iOS, are we saying background (unless a HUGE file) can only handle certain session limits? You mentioned 30 seconds...does that mean it runs for 30 seconds and then kills? How can we be certain that, say... I have 250 photos in a day, that I can trust the background to upload, does it tackle it throughout the day instead of just one go? (say 250 uploads in 5min). Just looking for the specifics, I know apple is being difficult on this feature and basically locks you into iCloud photos...(however my Google Photos would auto upload. Sorry for a lot here, just trying to make sure I settle on a solid Google Photos/iCloud replacement :)
OVERLORD commented 2026-02-05 00:15:16 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Jul 10, 2023):

So just to confirm, after reading all of this (had this issue with Synology Photos and they add a foreground "black screen" feature) there's no way around these apple security limitations to allow background? I imagine Android does fine, but as for iOS, are we saying background (unless a HUGE file) can only handle certain session limits? You mentioned 30 seconds...does that mean it runs for 30 seconds and then kills? How can we be certain that, say... I have 250 photos in a day, that I can trust the background to upload, does it tackle it throughout the day instead of just one go? (say 250 uploads in 5min). Just looking for the specifics, I know apple is being difficult on this feature and basically locks you into iCloud photos...(however my Google Photos would auto upload. Sorry for a lot here, just trying to make sure I settle on a solid Google Photos/iCloud replacement :)

Hello, what you describe is correct. AFAIK, at night, when you have your phone plugged it, the background tasks can have a longer time splice, up to 5 or more minutes to upload videos file.

@alextran1502 commented on GitHub (Jul 10, 2023): > So just to confirm, after reading all of this (had this issue with Synology Photos and they add a foreground "black screen" feature) there's no way around these apple security limitations to allow background? I imagine Android does fine, but as for iOS, are we saying background (unless a HUGE file) can only handle certain session limits? You mentioned 30 seconds...does that mean it runs for 30 seconds and then kills? How can we be certain that, say... I have 250 photos in a day, that I can trust the background to upload, does it tackle it throughout the day instead of just one go? (say 250 uploads in 5min). Just looking for the specifics, I know apple is being difficult on this feature and basically locks you into iCloud photos...(however my Google Photos would auto upload. Sorry for a lot here, just trying to make sure I settle on a solid Google Photos/iCloud replacement :) Hello, what you describe is correct. AFAIK, at night, when you have your phone plugged it, the background tasks can have a longer time splice, up to 5 or more minutes to upload videos file.
OVERLORD commented 2026-02-05 00:15:18 +03:00
Author
Owner
Copy Link

@srvprivate commented on GitHub (Jul 10, 2023):

So just to confirm, after reading all of this (had this issue with Synology Photos and they add a foreground "black screen" feature) there's no way around these apple security limitations to allow background? I imagine Android does fine, but as for iOS, are we saying background (unless a HUGE file) can only handle certain session limits? You mentioned 30 seconds...does that mean it runs for 30 seconds and then kills? How can we be certain that, say... I have 250 photos in a day, that I can trust the background to upload, does it tackle it throughout the day instead of just one go? (say 250 uploads in 5min). Just looking for the specifics, I know apple is being difficult on this feature and basically locks you into iCloud photos...(however my Google Photos would auto upload. Sorry for a lot here, just trying to make sure I settle on a solid Google Photos/iCloud replacement :)

Hello, what you describe is correct. AFAIK, at night, when you have your phone plugged it, the background tasks can have a longer time splice, up to 5 or more minutes to upload videos file.

Fair enough, I finally got docker-compose up and running, definitely a lot going on (I know it's under heavy prod) but you've done really well on the front end. Like your backstory to this, I have the same one! Hopefully I can help contribute in any way, God bless you.

@srvprivate commented on GitHub (Jul 10, 2023): > > So just to confirm, after reading all of this (had this issue with Synology Photos and they add a foreground "black screen" feature) there's no way around these apple security limitations to allow background? I imagine Android does fine, but as for iOS, are we saying background (unless a HUGE file) can only handle certain session limits? You mentioned 30 seconds...does that mean it runs for 30 seconds and then kills? How can we be certain that, say... I have 250 photos in a day, that I can trust the background to upload, does it tackle it throughout the day instead of just one go? (say 250 uploads in 5min). Just looking for the specifics, I know apple is being difficult on this feature and basically locks you into iCloud photos...(however my Google Photos would auto upload. Sorry for a lot here, just trying to make sure I settle on a solid Google Photos/iCloud replacement :) > > Hello, what you describe is correct. AFAIK, at night, when you have your phone plugged it, the background tasks can have a longer time splice, up to 5 or more minutes to upload videos file. Fair enough, I finally got docker-compose up and running, definitely a lot going on (I know it's under heavy prod) but you've done really well on the front end. Like your backstory to this, I have the same one! Hopefully I can help contribute in any way, God bless you.
OVERLORD commented 2026-02-05 00:15:19 +03:00
Author
Owner
Copy Link

@Guruleenyc commented on GitHub (Apr 19, 2025):

I'm experiencing the same, with backup and upload enabled with wifi and charging not required, it stops backing up and stops uploading anything. It will sit at 59 photos uploaded and 6000 remaining for hours. I'm on Android latest.

@Guruleenyc commented on GitHub (Apr 19, 2025): I'm experiencing the same, with backup and upload enabled with wifi and charging not required, it stops backing up and stops uploading anything. It will sit at 59 photos uploaded and 6000 remaining for hours. I'm on Android latest.
OVERLORD commented 2026-02-05 00:15:21 +03:00
Author
Owner
Copy Link

@navirius commented on GitHub (Aug 5, 2025):

experinece the same, background backup is activated, when screen is on, background backup running, when timeout it will stop immedietly, FYI, I monitor my local server traffic, I am on iphone, running immich server 1.137.3 and immich for ios 1.137.3

@navirius commented on GitHub (Aug 5, 2025): experinece the same, background backup is activated, when screen is on, background backup running, when timeout it will stop immedietly, FYI, I monitor my local server traffic, I am on iphone, running immich server 1.137.3 and immich for ios 1.137.3
OVERLORD commented 2026-02-05 00:15:23 +03:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 5, 2025):

ios 18, same issue. only foreground works, as soon as phone sleeps, it's gone, plus it doesn't resume once connected to wifi.

@ghost commented on GitHub (Aug 5, 2025): ios 18, same issue. only foreground works, as soon as phone sleeps, it's gone, plus it doesn't resume once connected to wifi.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
accessibility
changelog:enhancement
changelog:security
changelog:skip
changelog:translation
cli
date-time
documentation
external-library
format
good first issue
needs-answer
nice to have
sharing
tech-debt
📱mobile
🖥️web
🗄️server
🧠machine-learning
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: immich-app/immich#1056
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?