iOS Memories Widget "Unable to connect to your Immich instance"

[prestr]

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

• Yes

The bug

On iOS 26.5.2 when I try to add the Memories widget it shows this:

The Random widget works fine and Memories within the app work fine too, no connection issues when I open the app. This used to work but maybe it stopped working on v3.0.3 (I cannot be sure though).

I've also deleted and reinstalled the app.

The OS that Immich Server is running on

MacOS 26 - Docker

Version of Immich Server

v3.0.3

Version of Immich Mobile App

v3.0.3

Platform with the issue

• Server
• Web
• Mobile

Device make and model

iPhone 16 Pro - iOS 26.5.2

Your docker-compose.yml content

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/timezone:/etc/timezone:ro
      - /etc/localtime:/etc/localtime:ro
    env_file:
      - .env
    # ports:
    #  - "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://docs.immich.app/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:9@sha256:546304417feac0874c3dd576e0952c6bb8f06bb4093ea0c9ca303c73cf458f63
    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:bcf63357191b76a916ae5eb93464d65c07511da41e3bf7a8416db519b40b1c23
    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
    healthcheck:
      disable: false
volumes:
  model-cache: null
networks:
  default:
    external: true
    name: shared_bridge

Your .env content

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

# The location where your uploaded files are stored
UPLOAD_LOCATION=/Volumes/Immich/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$
TZ=America/Toronto

# The Immich version to use. You can pin this to a specific version like "v2.1.0"
IMMICH_VERSION=v3

# 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=xxxxxxxxxxxxxxxxx

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

Reproduction steps

1. Attempt to add the Memories widget
2. See error image above
3. This is how it appears once added:

Relevant log output

Additional information

No response

[mmomjian]

How are you connecting to the immich server? Are you using custom headers, mTLS, self signed cert, etc?

[prestr]

How are you connecting to the immich server? Are you using custom headers, mTLS, self signed cert, etc?

Over my local network using nginx proxy manager. (ie. https://immich.domain.com) with a Let's Encrypt signed cert.

[mmomjian]

Please test using local IP: port 2283 to see if that fixes the problem. If not, we can reopen

[prestr]

Please test using local IP: port 2283 to see if that fixes the problem. If not, we can reopen

Similar issue, in the preview it shows the same error but once added it doesn't show blank, instead it says "Login to Immich" but I am logged in and can sync fine (using local IP and port).

[mmomjian]

I am unable to replicated on iOS 26 and iPhone. I recommend checking the app and server logs. We haven't seen anyone else with this issue either. Maybe reinstalling the app might help. you are not using the URL switching feature correct?

[prestr]

I am unable to replicated on iOS 26 and iPhone. I recommend checking the app and server logs. We haven't seen anyone else with this issue either. Maybe reinstalling the app might help. you are not using the URL switching feature correct?

As mentioned I did reinstall and it had been working for months until the last few days (around when client and server were updated from 3.0.2 to 3.0.3).

Not using the URL switching feature.

In the client logs I do see "MESSAGE: Using server URL: null" "FROM: AppLifeCycleNotifier".

[knackerbrot]

I believe I've found the root cause (Claude actually) - this is a client/server date-format mismatch introduced in server v3.0.3, and it affects every iOS user on server ≥ v3.0.3 regardless of network setup. Could this be reopened?

Root cause

The iOS Memories widget sends a full ISO 8601 datetime for the for query param:

https://github.com/immich-app/immich/blob/main/mobile/ios/WidgetExtension/ImmichAPI.swift

let memoryParams = [URLQueryItem(name: "for", value: date.ISO8601Format())]
// → GET /memories?for=2026-07-19T08:15:00Z

But since #29907 (merged into server v3.0.3), MemorySearchDto.for is validated with isoDateToDate (z.iso.date()), which only accepts YYYY-MM-DD. The widget's request now returns 400, the response body fails to decode as [MemoryResult], and the widget surfaces WidgetError.fetchFailed → "Unable to connect to your Immich instance".

That PR updated web (memory-manager.svelte.ts → yyyy-MM-dd) and #29913 reverted the Android change to match, but the iOS widget was missed. This also explains why the Random widget still works (/search/random takes no date param) and why in-app Memories are fine.

Note: #29368 (open) changes this same line to send noon-UTC — that's still a full datetime, so it would also 400 against the new validation and needs updating.

Suggested client fix (also fixes the timezone issue from #19985, matching what web sends):

// /memories expects a date-only value (YYYY-MM-DD) since server v3.0.3 (#29907).
// Use the local calendar day so evening users don't get tomorrow's memories.
let localDay = date.formatted(
  Date.ISO8601FormatStyle(timeZone: .current).year().month().day().dateSeparator(.dash)
)
let memoryParams = [URLQueryItem(name: "for", value: localDay)]

Suggested server hardening: since all released iOS apps (≤ v3.0.3) send a datetime, the server could accept both formats for for (e.g. z.union([isoDateToDate, isoDatetimeToDate.transform(...)])) so existing clients aren't broken while app updates roll out.

Secondary bug while in there: in MemoryWidget.swift getTimeline, let memories = try await api.fetchMemory(for: Date.now) is a bare try inside Task {} — on failure the error is swallowed and the timeline completion is never called, which is why the added widget shows stale/odd states instead of the error card.

Reproduce against any v3.0.3 server:

curl -s -o /dev/null -w "%{http_code}\n" -H "x-api-key: $KEY" \
  "http://<server>:2283/api/memories?for=2026-07-19"              # 200
curl -s -o /dev/null -w "%{http_code}\n" -H "x-api-key: $KEY" \
  "http://<server>:2283/api/memories?for=2026-07-19T12:00:00.000Z" # 400

[mmomjian]

Done. Thanks for your great investigation.

[prestr]

Thanks @knackerbrot and @mmomjian

[alextran1502]

Cc @santoshakil

[Stevie-zylstra]

I'm running the same version of server and app as you. I am not experiencing this issue when adding this widget. It adds and shows my memories perfectly.
Also on the same iOS version.