[BUG] iOS foreground backup re-uploads files when returning to foreground

[f1sherman]

The bug

I have thousands of photos/videos I'm trying to back up from my iPhone. I start a foreground backup, but if my phone goes to the Lock Screen, gets a notification, etc., it starts uploading the same files that it already uploaded over and over again. I also noticed that the "Backed up photos and videos" number does not increase.

The OS that Immich Server is running on

Docker

Version of Immich Server

v1.83.0

Version of Immich Mobile App

1.83.0 build.123

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
      - /etc/localtime:/etc/localtime:ro
    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}
    # extends:
    #   file: hwaccel.yml
    #   service: hwaccel
    command: ["start.sh", "microservices"]
    volumes:
      - ${UPLOAD_LOCATION}:/usr/src/app/upload
      - /etc/localtime:/etc/localtime:ro
    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
      # remove this to get debug messages
      - GLOG_minloglevel=1
    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}
    volumes:
      - pgdata:/var/lib/postgresql/data
    restart: always

  immich-proxy:
    container_name: immich_proxy
    image: ghcr.io/immich-app/immich-proxy:${IMMICH_VERSION:-release}
    ports:
      - 2283:8080
    depends_on:
      - immich-server
      - immich-web
    restart: always

volumes:
  pgdata:
  model-cache:
  tsdata:

Your .env content

# You can find documentation for all the supported env variables at https://immich.app/docs/install/environment-variables

# The location where your uploaded files are stored
UPLOAD_LOCATION=/srv/media/immich

# The Immich version to use. You can pin this to a specific version like "v1.71.0"
IMMICH_VERSION=v1.83.0

# Connection secrets for postgres and typesense. You should change these to random passwords
TYPESENSE_API_KEY=<REDACTED>
DB_PASSWORD=<REDACTED>

# The values below this line do not need to be changed
###################################################################################
DB_HOSTNAME=immich_postgres
DB_USERNAME=postgres
DB_DATABASE_NAME=immich

REDIS_HOSTNAME=immich_redis

Reproduction steps

1. Open Immich app
2. Go to backup --> observe that files created on Oct. 29 are uploading
3. Lock the phone
4. Open Immich app
5. Go to backup --> observe that files created on Oct. 29 are uploading again

Additional information

No response

[alextran1502]

Hello, in your step 2 - did the file successfully upload in the foreground context?

[f1sherman]

It appears to have, is there some way I can check?

[alextran1502]

Ah wait, you are talking about the same file is reuploading i.e not continuing in the foreground context, correct?

[alextran1502]

We don't have the notion of continuous/resume upload, if you put the app to background, the upload will be terminated and will start over again the next time is app is opened

[f1sherman]

Several files appear to upload successfully, then when the app comes back to the foreground those same files re-upload. It appears to start with the most recent files, so the older files never get uploaded. Is that expected?

[alextran1502]

Are you accessing over local IP or DNS?

Can you walk me through how you can determine older files never gets uploaded?

What do the logs on the server say about when these files get uploaded?

[f1sherman]

I'm using DNS. I'm not sure that the older files never get uploaded, it's more like the same files get uploaded over and over again. I'm running Docker, which container should I use to look at the logs?

[alextran1502]

Can you try local IP. You seem to not have client max body size setting in your reverse proxy setup

[f1sherman]

Ah, good catch! That does seem to have fixed it. I will also try setting the client max body size, I somehow missed that in the instructions. Thank you!

[alextran1502]

@f1sherman You can set to 0 to allow any size