Images not marked "backed up" when using beta timeline on iOS app #7211

Closed
opened 2026-02-05 12:52:19 +03:00 by OVERLORD · 5 comments
Owner

Originally created by @benlenau on GitHub (Sep 14, 2025).

I have searched the existing issues, both open and closed, to make sure this is not a duplicate report.

  • Yes

The bug

The latest forced Beta timeline on iOS doesn't quite work for my two iPhones. Memories missing (present on web) and my phone images have the "not backed up"-cloud on them. Switching to old timeline and everything is there, including the right "backup"-cloud.

ps. No migration pop-up when opening after app update, just an empty timeline, I marked "latest" for backup and it populated the timeline but with above caveats. returning to old timeline via settings restores everything.

The OS that Immich Server is running on

iOS

Version of Immich Server

v1.142.0

Version of Immich Mobile App

v1.142.0 build.223

Platform with the issue

  • Server
  • Web
  • Mobile

Device make and model

iPhone 13 and 16

Your docker-compose.yml content

#
# WARNING: To install Immich, follow our guide: https://immich.app/docs/install/docker-compose
#
# Make sure to use the docker-compose.yml of the current release:
#
# https://github.com/immich-app/immich/releases/latest/download/docker-compose.yml
#
# The compose file on main may not be compatible with the latest release.

name: immich

services:
  immich-server:
    container_name: immich_server
    image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
    # 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
      - ${UPLOAD_LOCATION}:/data
      - /etc/localtime:/etc/localtime:ro
      - /media/photos:/media/photos:ro
    env_file:
      - .env
    ports:
      - '127.0.0.1:2283:2283'
    depends_on:
      - redis
      - database
    restart: always
    healthcheck:
      disable: false

  immich-machine-learning:
    container_name: immich_machine_learning
    # For hardware acceleration, add one of -[armnn, cuda, rocm, openvino, rknn] to the image tag.
    # Example tag: ${IMMICH_VERSION:-release}-cuda
    image: ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release}
    # extends: # uncomment this section for hardware acceleration - see https://immich.app/docs/features/ml-hardware-acceleration
    #   file: hwaccel.ml.yml
    #   service: cpu # set to one of [armnn, cuda, rocm, openvino, openvino-wsl, rknn] for accelerated inference - use the `-wsl` version for WSL2 where applicable
    volumes:
      - model-cache:/cache
    env_file:
      - .env
    restart: always
    healthcheck:
      disable: false

  redis:
    container_name: immich_redis
    image: docker.io/valkey/valkey:8-bookworm@sha256:fea8b3e67b15729d4bb70589eb03367bab9ad1ee89c876f54327fc7c6e618571
    healthcheck:
      test: redis-cli ping || exit 1
    restart: always

  database:
    container_name: immich_postgres
    image: ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0@sha256:8d292bdb796aa58bbbaa47fe971c8516f6f57d6a47e7172e62754feb6ed4e7b0
    environment:
      POSTGRES_PASSWORD: ${DB_PASSWORD}
      POSTGRES_USER: ${DB_USERNAME}
      POSTGRES_DB: ${DB_DATABASE_NAME}
      POSTGRES_INITDB_ARGS: '--data-checksums'
      # Uncomment the DB_STORAGE_TYPE: 'HDD' var if your database isn't stored on SSDs
      # DB_STORAGE_TYPE: 'HDD'
    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
      - ${DB_DATA_LOCATION}:/var/lib/postgresql/data
    shm_size: 128mb
    restart: always

volumes:
  model-cache:

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=./library

# The location where your database files are stored. Network shares are not supported for the database
DB_DATA_LOCATION=./postgres

# To set a timezone, uncomment the next line and change Etc/UTC to a TZ identifier from this list: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones#List
TZ=Europe/Copenhagen

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

# Connection secret for postgres. You should change it to a random password
# Please use only the characters `A-Za-z0-9`, without special characters or spaces
DB_PASSWORD=nope

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

Reproduction steps

  1. Open iOS app
  2. Activate timeline beta
  3. Missing memories + "backup"-clouds wrong.
    ...

Relevant log output


Additional information

No response

Originally created by @benlenau on GitHub (Sep 14, 2025). ### I have searched the existing issues, both open and closed, to make sure this is not a duplicate report. - [x] Yes ### The bug The latest forced Beta timeline on iOS doesn't quite work for my two iPhones. Memories missing (present on web) and my phone images have the "not backed up"-cloud on them. Switching to old timeline and everything is there, including the right "backup"-cloud. ps. No migration pop-up when opening after app update, just an empty timeline, I marked "latest" for backup and it populated the timeline but with above caveats. returning to old timeline via settings restores everything. ### The OS that Immich Server is running on iOS ### Version of Immich Server v1.142.0 ### Version of Immich Mobile App v1.142.0 build.223 ### Platform with the issue - [ ] Server - [ ] Web - [x] Mobile ### Device make and model iPhone 13 and 16 ### Your docker-compose.yml content ```YAML # # WARNING: To install Immich, follow our guide: https://immich.app/docs/install/docker-compose # # Make sure to use the docker-compose.yml of the current release: # # https://github.com/immich-app/immich/releases/latest/download/docker-compose.yml # # The compose file on main may not be compatible with the latest release. name: immich services: immich-server: container_name: immich_server image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release} # 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 - ${UPLOAD_LOCATION}:/data - /etc/localtime:/etc/localtime:ro - /media/photos:/media/photos:ro env_file: - .env ports: - '127.0.0.1:2283:2283' depends_on: - redis - database restart: always healthcheck: disable: false immich-machine-learning: container_name: immich_machine_learning # For hardware acceleration, add one of -[armnn, cuda, rocm, openvino, rknn] to the image tag. # Example tag: ${IMMICH_VERSION:-release}-cuda image: ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release} # extends: # uncomment this section for hardware acceleration - see https://immich.app/docs/features/ml-hardware-acceleration # file: hwaccel.ml.yml # service: cpu # set to one of [armnn, cuda, rocm, openvino, openvino-wsl, rknn] for accelerated inference - use the `-wsl` version for WSL2 where applicable volumes: - model-cache:/cache env_file: - .env restart: always healthcheck: disable: false redis: container_name: immich_redis image: docker.io/valkey/valkey:8-bookworm@sha256:fea8b3e67b15729d4bb70589eb03367bab9ad1ee89c876f54327fc7c6e618571 healthcheck: test: redis-cli ping || exit 1 restart: always database: container_name: immich_postgres image: ghcr.io/immich-app/postgres:14-vectorchord0.4.3-pgvectors0.2.0@sha256:8d292bdb796aa58bbbaa47fe971c8516f6f57d6a47e7172e62754feb6ed4e7b0 environment: POSTGRES_PASSWORD: ${DB_PASSWORD} POSTGRES_USER: ${DB_USERNAME} POSTGRES_DB: ${DB_DATABASE_NAME} POSTGRES_INITDB_ARGS: '--data-checksums' # Uncomment the DB_STORAGE_TYPE: 'HDD' var if your database isn't stored on SSDs # DB_STORAGE_TYPE: 'HDD' 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 - ${DB_DATA_LOCATION}:/var/lib/postgresql/data shm_size: 128mb restart: always volumes: model-cache: ``` ### Your .env content ```Shell # 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=./library # The location where your database files are stored. Network shares are not supported for the database DB_DATA_LOCATION=./postgres # To set a timezone, uncomment the next line and change Etc/UTC to a TZ identifier from this list: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones#List TZ=Europe/Copenhagen # The Immich version to use. You can pin this to a specific version like "v1.71.0" IMMICH_VERSION=release # Connection secret for postgres. You should change it to a random password # Please use only the characters `A-Za-z0-9`, without special characters or spaces DB_PASSWORD=nope # The values below this line do not need to be changed ################################################################################### DB_USERNAME=postgres DB_DATABASE_NAME=immich ``` ### Reproduction steps 1. Open iOS app 2. Activate timeline beta 3. Missing memories + "backup"-clouds wrong. ... ### Relevant log output ```shell ``` ### Additional information _No response_
Author
Owner

@alextran1502 commented on GitHub (Sep 14, 2025):

Hello, you can fix this issue by log out and log in on both devices, it will pull the correct data.

@alextran1502 commented on GitHub (Sep 14, 2025): Hello, you can fix this issue by log out and log in on both devices, it will pull the correct data.
Author
Owner

@benlenau commented on GitHub (Sep 14, 2025):

Hello, you can fix this issue by log out and log in on both devices, it will pull the correct data.

Valuable intel. Thanks. It now works on both devices. Keep up the good work :-)

@benlenau commented on GitHub (Sep 14, 2025): > Hello, you can fix this issue by log out and log in on both devices, it will pull the correct data. Valuable intel. Thanks. It now works on both devices. Keep up the good work :-)
Author
Owner

@aksdb commented on GitHub (Sep 15, 2025):

I have the same issue, but logging out and in didn't change anything. Also under settings -> sync it shows "0" for in the "Server" tile. When enabling synchronization, it starts uploading everything. I also reset the sqlite db and logged back in, but same issue. Disabling the beta timeline works, though (in the sense that it afterwards detects the libraries to be in sync again; even when switching the beta timeline back on). Server and client are both up 2 date.

It looks like the beta timeline fails to "bootstrap" the sync status when the sqlite db is fresh. Migrating over from the old timeline seems to work.

@aksdb commented on GitHub (Sep 15, 2025): I have the same issue, but logging out and in didn't change anything. Also under settings -> sync it shows "0" for in the "Server" tile. When enabling synchronization, it starts uploading _everything_. I also reset the sqlite db and logged back in, but same issue. Disabling the beta timeline works, though (in the sense that it afterwards detects the libraries to be in sync again; even when switching the beta timeline back on). Server and client are both up 2 date. It looks like the beta timeline fails to "bootstrap" the sync status when the sqlite db is fresh. Migrating over from the old timeline _seems_ to work.
Author
Owner

@benlenau commented on GitHub (Sep 15, 2025):

I have the same issue, but logging out and in didn't change anything. Also under settings -> sync it shows "0" for in the "Server" tile. When enabling synchronization, it starts uploading everything. I also reset the sqlite db and logged back in, but same issue. Disabling the beta timeline works, though (in the sense that it afterwards detects the libraries to be in sync again; even when switching the beta timeline back on). Server and client are both up 2 date.

  • Mine did the same, but seemed like it only checked hashes because it went super quick for 2.000+ photos (doing the switch (beta --> old --> beta ... log-out / log-in) made things normal)
  • Initially my memories where still missing, but a did at pull-down refresh (iOS) and it apeared.

It looks like the beta timeline fails to "bootstrap" the sync status when the sqlite db is fresh. Migrating over from the old timeline seems to work.

  • Yeah that would explain why I needed to switch from beta --> old --> beta and then the "migration" worked.

I now realise how convoluted this is, and certainly isn't a great user expirience even considering "very active development."

@benlenau commented on GitHub (Sep 15, 2025): > I have the same issue, but logging out and in didn't change anything. Also under settings -> sync it shows "0" for in the "Server" tile. When enabling synchronization, it starts uploading _everything_. I also reset the sqlite db and logged back in, but same issue. Disabling the beta timeline works, though (in the sense that it afterwards detects the libraries to be in sync again; even when switching the beta timeline back on). Server and client are both up 2 date. > - Mine did the same, but seemed like it only checked hashes because it went super quick for 2.000+ photos (doing the switch (beta --> old --> beta ... log-out / log-in) made things normal) - Initially my memories where still missing, but a did at pull-down refresh (iOS) and it apeared. > It looks like the beta timeline fails to "bootstrap" the sync status when the sqlite db is fresh. Migrating over from the old timeline _seems_ to work. - Yeah that would explain why I needed to switch from beta --> old --> beta and then the "migration" worked. I now realise how convoluted this is, and certainly isn't a great user expirience even considering "very active development."
Author
Owner

@bigbeka commented on GitHub (Sep 15, 2025):

Hello, you can fix this issue by log out and log in on both devices, it will pull the correct data.

It worked, thank you!

@bigbeka commented on GitHub (Sep 15, 2025): > Hello, you can fix this issue by log out and log in on both devices, it will pull the correct data. It worked, thank you!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: immich-app/immich#7211