Skip to content
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

iOS app never finish backup #13562

Open
1 of 3 tasks
an0o0nym opened this issue Oct 17, 2024 · 3 comments
Open
1 of 3 tasks

iOS app never finish backup #13562

an0o0nym opened this issue Oct 17, 2024 · 3 comments

Comments

@an0o0nym
Copy link

an0o0nym commented Oct 17, 2024

The bug

Immich iOS 18.0 mobile app gets stuck at 1 asset remaining.
IMG_7013

  • Total: 990
  • Backup: 989
  • Remainder: 1
  • Uploading file info: is empty. There is no file name no ID, and Created on seems to be set to some default placeholder date.

The cloud icon on the home screen in the immich app has 'loading circle' always spinning. The upload is stuck at 1 remaining asset. Which I believe may be a bug, cause there is no details about which asset it is, nor it ever starts the upload.

I've tried different things, from force quiting app, to restarting the server etc, But nothing works.

After some time error came up in the logs about missing asset:

IMG_7012

It would be super nice to be able to click on that 'Remainder' to see a list of what exact assets are being stuck in the queue. [perhaps this could be a feature request?]

But for now, can you point me in some direction on how to debug and fix the issue?

The OS that Immich Server is running on

Debian 6.1.112-1

Version of Immich Server

v.1.118.0

Version of Immich Mobile App

v.1.118.0

Platform with the issue

  • Server
  • Web
  • Mobile

Your docker-compose.yml content

name: immich

services:
  immich-server:
    container_name: immich-server
    image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
    ports:
      - "2283:2283"
    # extends:
    #  file: hwaccel.transcoding.yml
    #  service: cpu # set to one of [nvenc, quicksync, rkmpp, vaapi, vaapi-wsl] for accelerated transcoding
    volumes:
      # Do not edit the next line. If you want to change the media storage location on your system, edit the value of UPLOAD_LOCATION in the .env file
      - ${PATH_TO_DOCKER_DATA}/immich/library:/usr/src/app/upload
      - /etc/localtime:/etc/localtime:ro
    env_file:
      - immich.env
    depends_on:
      - immich-redis
      - immich-database
    networks:
      - npm_default
      - immich_default
    restart: always
    healthcheck:
      disable: false

  immich-redis:
    container_name: immich-redis
    image: docker.io/redis:6.2-alpine@sha256:2d1463258f2764328496376f5d965f20c6a67f66ea2b06dc42af351f75248792
    networks:
      - immich_default
    healthcheck:
      test: redis-cli ping || exit 1
    restart: always

 immich-database:
    container_name: immich-postgres
    image: docker.io/tensorchord/pgvecto-rs:pg14-v0.2.0@sha256:90724186f0a3517cf6914295b5ab410db9ce23190a2d9d0b9dd6463e3fa298f0
    environment:
      POSTGRES_PASSWORD: ${DB_PASSWORD}
      POSTGRES_USER: ${DB_USERNAME}
      POSTGRES_DB: ${DB_DATABASE_NAME}
      POSTGRES_INITDB_ARGS: '--data-checksums'
    volumes:
      # Do not edit the next line. If you want to change the database storage location on your system, edit the value of DB_DATA_LOCATION in the .env file
      - ${PATH_TO_APPDATA}/immich/postgres:/var/lib/postgresql/data
    networks:
      - immich_default
    healthcheck:
      test: pg_isready --dbname='${DB_DATABASE_NAME}' --username='${DB_USERNAME}' || exit 1; Chksum="$$(psql --dbname='${DB_DATABASE_NAME}' --username='${DB_USERNAME}' --tuples-only --no-align --command='SELECT COALESCE(SUM(checksum_failures), 0) FROM pg_stat_database')"; echo "checksum failure count is $$Chksum"; [ "$$Chksum" = '0' ] || exit 1
      interval: 5m
      start_interval: 30s
      start_period: 5m
    command: ["postgres", "-c", "shared_preload_libraries=vectors.so", "-c", 'search_path="$$user", public, vectors', "-c", "logging_collector=on", "-c", "max_wal_size=2GB", "-c", "shared_buffers=512MB", "-c", "wal_compression=on"]
    restart: always

networks:
  npm_default:
    external: true
  immich_default:
    external: true

Your .env content

IMMICH_VERSION=v1.118.0

DB_PASSWORD=<redacted>
DB_USERNAME=postgres
DB_DATABASE_NAME=immich

REDIS_HOSTNAME=immich-redis
DB_HOSTNAME=immich-database

Reproduction steps

  1. Install Immich
  2. Start backup of a 'recent' folder on iPhone
  3. Wait until it finishes uploading all files
  4. Observe the behavior

Relevant log output

Attached in the issue description

Additional information

No response

@an0o0nym
Copy link
Author

an0o0nym commented Oct 17, 2024

It turns out the issue was caused by a photo from the Nextcloud app, which I no longer use. Once I removed the photo, the backup process finished successfully.

I suspect the photo wasn't an original, but rather an optimized copy, similar to how iCloud handles storage. That might explain why it showed no asset details in the 'Uploading file info' section.

I remember seeing a post where someone experienced the same issue, and their solution was to disable storage optimization in iCloud settings. While I'm not entirely sure, this could be related.

As I mentioned in the ticket, it would be great to have a list of remaining assets (perhaps even with thumbnails) in the app. The logs took a long time to show up, and there wasn’t any specific error message in the mobile app itself. I had to manually dig through the logs to identify the problem. A better user experience might be to display an alert or snackbar with the error details directly in the app.

It would also be helpful if the app could handle these types of scenarios more gracefully. While I haven’t done thorough research, there might be a way to detect if a photo is an optimized copy rather than the original. In such cases, the app could either mark the backup as "completed with errors" or prompt the user to retry or finish the sync with a warning.

@chen-chao
Copy link

Same issue here. There is no file name nor ID.

it would be great to have a list of remaining assets (perhaps even with thumbnails) in the app

That'll be nice. For now I still don't know which pictures stuck the backup process.

@her-cat
Copy link

her-cat commented Oct 18, 2024

I'm having the same problem.

App Version: 1.118.0 build.180
Server Version: 1.118.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants