immich-app/immich
1
0
Fork 0
mirror of https://github.com/immich-app/immich.git synced 2026-07-25 14:00:45 +03:00
Code Issues 783 Packages Projects Releases 22 Wiki Activity

Immich times in Immich web show properly, but on my phone they show +8 #6512

New Issue
Open
opened 2026-02-05 12:20:22 +03:00 by OVERLORD · 14 comments
OVERLORD commented 2026-02-05 12:20:22 +03:00
Owner
Copy Link

Originally created by @JayCroghan on GitHub (Jul 24, 2025).

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

  • Yes

The bug

Immich is the latest as of today on both phone and host.

In my .env file, I have TZ=CN because that's the timezone I am in.

My photos are all (most) taken in this timezone but I am concentrating on the last few to see if we can fix the issue.

In Immich Web, they all show perfect; for instance, a photo I took at 20:31 yesterday (it's now 2 am Friday) shows as yesterday in Immich Web and shows 20:31 for the time the image was taken in the info. However, on my iPhone's Immich phone app, it appears in the Today category. When I click it and check the info, it shows the time as 4:31 AM UTC +08:00.

Why is my phone adding another 8 hours to a photo that was already taken in the same time zone? My phone has its timezone auto-set to Beijing, as that's the country I am in, so I am unsure of what to do next.

Is there a quick fix?

The OS that Immich Server is running on

Ubuntu 22.04.5 LTS

Version of Immich Server

v1.136.0

Version of Immich Mobile App

v1.136.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}
    # 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}:/usr/src/app/upload
      - /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://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:fec42f399876eb6faf9e008570597741c87ff7662a54185593e74b09ce83d177
    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
    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
    restart: always

volumes:
  model-cache:

Your .env content

# The location where your uploaded files are stored
UPLOAD_LOCATION=/media/Shared/Immich

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

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

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

Reproduction steps

  1. Take a photo
  2. Sync with Immich
  3. View the photo in Immich iOS app

Relevant log output

Additional information

No response

Originally created by @JayCroghan on GitHub (Jul 24, 2025). ### I have searched the existing issues, both open and closed, to make sure this is not a duplicate report. - [x] Yes ### The bug Immich is the latest as of today on both phone and host. In my .env file, I have `TZ=CN` because that's the timezone I am in. My photos are all (most) taken in this timezone but I am concentrating on the last few to see if we can fix the issue. In Immich Web, they all show perfect; for instance, a photo I took at 20:31 yesterday (it's now 2 am Friday) shows as yesterday in Immich Web and shows 20:31 for the time the image was taken in the info. However, on my iPhone's Immich phone app, it appears in the Today category. When I click it and check the info, it shows the time as `4:31 AM UTC +08:00`. Why is my phone adding another 8 hours to a photo that was already taken in the same time zone? My phone has its timezone auto-set to Beijing, as that's the country I am in, so I am unsure of what to do next. Is there a quick fix? ### The OS that Immich Server is running on Ubuntu 22.04.5 LTS ### Version of Immich Server v1.136.0 ### Version of Immich Mobile App v1.136.0 ### Platform with the issue - [ ] Server - [ ] Web - [x] Mobile ### Your docker-compose.yml content ```YAML 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}:/usr/src/app/upload - /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://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:fec42f399876eb6faf9e008570597741c87ff7662a54185593e74b09ce83d177 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 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 restart: always volumes: model-cache: ``` ### Your .env content ```Shell # The location where your uploaded files are stored UPLOAD_LOCATION=/media/Shared/Immich # 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=CN # 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=<PASSWORD> # The values below this line do not need to be changed ################################################################################### DB_USERNAME=postgres DB_DATABASE_NAME=immich ``` ### Reproduction steps 1. Take a photo 2. Sync with Immich 3. View the photo in Immich iOS app ### Relevant log output ```shell ``` ### Additional information _No response_
OVERLORD added the 📱mobile label 2026-02-05 12:20:22 +03:00
OVERLORD commented 2026-02-05 12:20:24 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Jul 24, 2025):

is this in the new timeline or the old one?

@alextran1502 commented on GitHub (Jul 24, 2025): is this in the new timeline or the old one?
OVERLORD commented 2026-02-05 12:20:25 +03:00
Author
Owner
Copy Link

@JayCroghan commented on GitHub (Jul 24, 2025):

Both. Switching back to the old timeline brings weird old photos to today
but when I switch back to Beta it goes back to the normal broken one with
photos from today that were shot yesterday.

On Fri 25 Jul 2025 at 02:57, Alex @.***> wrote:

alextran1502 left a comment (immich-app/immich#20148)
https://github.com/immich-app/immich/issues/20148#issuecomment-3114531289

is this in the new timeline or the old one?

—
Reply to this email directly, view it on GitHub
https://github.com/immich-app/immich/issues/20148#issuecomment-3114531289,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAI55THTGCACA6Z7CEEGV4D3KET75AVCNFSM6AAAAACCJTRQLSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCMJUGUZTCMRYHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

@JayCroghan commented on GitHub (Jul 24, 2025): Both. Switching back to the old timeline brings weird old photos to today but when I switch back to Beta it goes back to the normal broken one with photos from today that were shot yesterday. On Fri 25 Jul 2025 at 02:57, Alex ***@***.***> wrote: > *alextran1502* left a comment (immich-app/immich#20148) > <https://github.com/immich-app/immich/issues/20148#issuecomment-3114531289> > > is this in the new timeline or the old one? > > — > Reply to this email directly, view it on GitHub > <https://github.com/immich-app/immich/issues/20148#issuecomment-3114531289>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAI55THTGCACA6Z7CEEGV4D3KET75AVCNFSM6AAAAACCJTRQLSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCMJUGUZTCMRYHE> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >
OVERLORD commented 2026-02-05 12:20:26 +03:00
Author
Owner
Copy Link

@JayCroghan commented on GitHub (Jul 24, 2025):

What’s weird is it doesn’t even call them today it just says Friday so it’s
an even weirder weird.

On Fri 25 Jul 2025 at 03:00, Jason Croghan @.***> wrote:

Both. Switching back to the old timeline brings weird old photos to today
but when I switch back to Beta it goes back to the normal broken one with
photos from today that were shot yesterday.

On Fri 25 Jul 2025 at 02:57, Alex @.***> wrote:

alextran1502 left a comment (immich-app/immich#20148)
https://github.com/immich-app/immich/issues/20148#issuecomment-3114531289

is this in the new timeline or the old one?

—
Reply to this email directly, view it on GitHub
https://github.com/immich-app/immich/issues/20148#issuecomment-3114531289,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAI55THTGCACA6Z7CEEGV4D3KET75AVCNFSM6AAAAACCJTRQLSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCMJUGUZTCMRYHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

@JayCroghan commented on GitHub (Jul 24, 2025): What’s weird is it doesn’t even call them today it just says Friday so it’s an even weirder weird. On Fri 25 Jul 2025 at 03:00, Jason Croghan ***@***.***> wrote: > Both. Switching back to the old timeline brings weird old photos to today > but when I switch back to Beta it goes back to the normal broken one with > photos from today that were shot yesterday. > > On Fri 25 Jul 2025 at 02:57, Alex ***@***.***> wrote: > >> *alextran1502* left a comment (immich-app/immich#20148) >> <https://github.com/immich-app/immich/issues/20148#issuecomment-3114531289> >> >> is this in the new timeline or the old one? >> >> — >> Reply to this email directly, view it on GitHub >> <https://github.com/immich-app/immich/issues/20148#issuecomment-3114531289>, >> or unsubscribe >> <https://github.com/notifications/unsubscribe-auth/AAI55THTGCACA6Z7CEEGV4D3KET75AVCNFSM6AAAAACCJTRQLSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCMJUGUZTCMRYHE> >> . >> You are receiving this because you authored the thread.Message ID: >> ***@***.***> >> >
OVERLORD commented 2026-02-05 12:20:28 +03:00
Author
Owner
Copy Link

@JayCroghan commented on GitHub (Jul 27, 2025):

Can I please have confirmation this looks like a defect and not something I
may have done wrong?

On Fri, 25 Jul 2025 at 03:00, Jason Croghan @.***> wrote:

What’s weird is it doesn’t even call them today it just says Friday so
it’s an even weirder weird.

On Fri 25 Jul 2025 at 03:00, Jason Croghan @.***> wrote:

Both. Switching back to the old timeline brings weird old photos to today
but when I switch back to Beta it goes back to the normal broken one with
photos from today that were shot yesterday.

On Fri 25 Jul 2025 at 02:57, Alex @.***> wrote:

alextran1502 left a comment (immich-app/immich#20148)
https://github.com/immich-app/immich/issues/20148#issuecomment-3114531289

is this in the new timeline or the old one?

—
Reply to this email directly, view it on GitHub
https://github.com/immich-app/immich/issues/20148#issuecomment-3114531289,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAI55THTGCACA6Z7CEEGV4D3KET75AVCNFSM6AAAAACCJTRQLSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCMJUGUZTCMRYHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

@JayCroghan commented on GitHub (Jul 27, 2025): Can I please have confirmation this looks like a defect and not something I may have done wrong? On Fri, 25 Jul 2025 at 03:00, Jason Croghan ***@***.***> wrote: > What’s weird is it doesn’t even call them today it just says Friday so > it’s an even weirder weird. > > On Fri 25 Jul 2025 at 03:00, Jason Croghan ***@***.***> wrote: > >> Both. Switching back to the old timeline brings weird old photos to today >> but when I switch back to Beta it goes back to the normal broken one with >> photos from today that were shot yesterday. >> >> On Fri 25 Jul 2025 at 02:57, Alex ***@***.***> wrote: >> >>> *alextran1502* left a comment (immich-app/immich#20148) >>> <https://github.com/immich-app/immich/issues/20148#issuecomment-3114531289> >>> >>> is this in the new timeline or the old one? >>> >>> — >>> Reply to this email directly, view it on GitHub >>> <https://github.com/immich-app/immich/issues/20148#issuecomment-3114531289>, >>> or unsubscribe >>> <https://github.com/notifications/unsubscribe-auth/AAI55THTGCACA6Z7CEEGV4D3KET75AVCNFSM6AAAAACCJTRQLSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCMJUGUZTCMRYHE> >>> . >>> You are receiving this because you authored the thread.Message ID: >>> ***@***.***> >>> >>
OVERLORD commented 2026-02-05 12:20:28 +03:00
Author
Owner
Copy Link

@JayCroghan commented on GitHub (Aug 1, 2025):

This seems to be fixed for images which are synced since the new update, but the older images still show proper date time on Immich Web but show +8 hours in Immich iOS, both are updated to 1.137.1/1.137.0 this morning. I didn't think the problem could be with the upload as the web showed ok. I wonder is there a way to retrospectively fix the ones it's showing the wrong date for in Immich web or will I need to restart my entire Immich library :(

Edit: The issue is not present for images I uploaded using Immich-Go with XMP sidecar to start my library originally, only ones synced since and before this update. I used that method rather than sync due to the known iOS initial sync issue with file dates.

@JayCroghan commented on GitHub (Aug 1, 2025): This seems to be fixed for images which are synced since the new update, but the older images still show proper date time on Immich Web but show +8 hours in Immich iOS, both are updated to 1.137.1/1.137.0 this morning. I didn't think the problem could be with the upload as the web showed ok. I wonder is there a way to retrospectively fix the ones it's showing the wrong date for in Immich web or will I need to restart my entire Immich library :( Edit: The issue is not present for images I uploaded using Immich-Go with XMP sidecar to start my library originally, only ones synced since and before this update. I used that method rather than sync due to the known iOS initial sync issue with file dates.
OVERLORD commented 2026-02-05 12:20:29 +03:00
Author
Owner
Copy Link

@JayCroghan commented on GitHub (Aug 7, 2025):

I thought the latest version was fixed but it's not - the problem seems limited to screenshots though and only in Immich iOS where the screenshots were taken.

@JayCroghan commented on GitHub (Aug 7, 2025): I thought the latest version was fixed but it's not - the problem seems limited to screenshots though and only in Immich iOS where the screenshots were taken.
OVERLORD commented 2026-02-05 12:20:29 +03:00
Author
Owner
Copy Link

@chemicalsam commented on GitHub (Aug 27, 2025):

Also have this issue. Happens with new and old timeline.

Only happens with screenshots for me.

Screenshots always get assigned the wrong time but not photos I take.

But while they have the correct time on the web interface- they show in the wrong order on the timeline.

@chemicalsam commented on GitHub (Aug 27, 2025): Also have this issue. Happens with new and old timeline. Only happens with screenshots for me. Screenshots always get assigned the wrong time but not photos I take. But while they have the correct time on the web interface- they show in the wrong order on the timeline.
OVERLORD commented 2026-02-05 12:20:30 +03:00
Author
Owner
Copy Link

@chemicalsam commented on GitHub (Sep 8, 2025):

Image

Also while the time is right on the web interface, on both photos, they appear in the wrong timeline order.
The screenshot was taken after the photo.

However it's more prevalent on iOS where the screenshot just shows the wrong time/timezone altogether.

@chemicalsam commented on GitHub (Sep 8, 2025): <img width="315" height="290" alt="Image" src="https://github.com/user-attachments/assets/e59a2fb7-6f77-4bba-b81f-a5a4d6c482bf" /> Also while the time is right on the web interface, on both photos, they appear in the wrong timeline order. The screenshot was taken after the photo. However it's more prevalent on iOS where the screenshot just shows the wrong time/timezone altogether.
OVERLORD commented 2026-02-05 12:20:30 +03:00
Author
Owner
Copy Link

@MadWalnut commented on GitHub (Oct 23, 2025):

Same issue here. Wrong time in the app (shows correct timezone though) and wrong position (based on the wrong time). On web it works. I also noticed that this seemingly only happens after uploading the photo. I currently have a screenshot taken on mobile data (and therefore not synced yet) which shows the correct time and position.

@MadWalnut commented on GitHub (Oct 23, 2025): Same issue here. Wrong time in the app (shows correct timezone though) and wrong position (based on the wrong time). On web it works. I also noticed that this seemingly only happens after uploading the photo. I currently have a screenshot taken on mobile data (and therefore not synced yet) which shows the correct time and position.
OVERLORD commented 2026-02-05 12:20:31 +03:00
Author
Owner
Copy Link

@Xiaopande73 commented on GitHub (Nov 24, 2025):

Same issue. It's worth noting that images with location information display correctly on both the web and the iOS app, while images without location information (such as mobile phone screenshots) show properly on the web but appear eight hours behind on the iOS app.

@Xiaopande73 commented on GitHub (Nov 24, 2025): Same issue. It's worth noting that images with location information display correctly on both the web and the iOS app, while images without location information (such as mobile phone screenshots) show properly on the web but appear **eight hours behind** on the iOS app.
OVERLORD commented 2026-02-05 12:20:31 +03:00
Author
Owner
Copy Link

@aaronntw commented on GitHub (Dec 20, 2025):

Just noticed this issue here on Immich v2.3.1. Android app version 2.3.0 build.3027. Only applies to Screenshots on New Timeline.

  • On web-browser, the screensnot is shown under Today's group

  • Date taken 20-dec, 2025, 5:19:38PM, UTC+00:00 (correct date/time, wrong timezone)
    Image

  • On Android app, the image is shown under 21-Dec-2025 group (tomorrow)

  • Date taken 21-Dec-2025, 1:19AM UTC+08:00 (wrong date/time, correct timezone)
    Image

To add, after taking a screenshot on phone while waiting for it to get uploaded, the image is shown in the correct date group, ie 20-Dec-2025 but once it gets uploaded, the image gets moved to the 21-Dec-2025 group.

@aaronntw commented on GitHub (Dec 20, 2025): Just noticed this issue here on Immich v2.3.1. Android app version 2.3.0 build.3027. Only applies to Screenshots on New Timeline. - On web-browser, the screensnot is shown under Today's group - Date taken 20-dec, 2025, 5:19:38PM, UTC+00:00 (correct date/time, wrong timezone) <img width="1316" height="843" alt="Image" src="https://github.com/user-attachments/assets/e5d61fd7-6e30-4fc2-b5b3-4b9a4b4287df" /> - On Android app, the image is shown under 21-Dec-2025 group (tomorrow) - Date taken 21-Dec-2025, 1:19AM UTC+08:00 (wrong date/time, correct timezone) <img width="569" height="1269" alt="Image" src="https://github.com/user-attachments/assets/f3828676-61b4-484b-8b02-65087317a7bf" /> To add, after taking a screenshot on phone while waiting for it to get uploaded, the image is shown in the correct date group, ie 20-Dec-2025 but once it gets uploaded, the image gets moved to the 21-Dec-2025 group.
OVERLORD commented 2026-02-05 12:20:31 +03:00
Author
Owner
Copy Link

@JayCroghan commented on GitHub (Dec 20, 2025):

I’m a little concerned this issue is so prevalent yet the devs have ignored
it and consider it “stable”. This is quite the issue especially if it
requires re-uploading everything and is the major reason I haven’t cut the
cable in my existing image cloud.

On Sat 20 Dec 2025 at 19:38, aaronntw @.***> wrote:

aaronntw left a comment (immich-app/immich#20148)
https://github.com/immich-app/immich/issues/20148#issuecomment-3677790361

Just noticed this issue here on Immich v2.3.1. Android app version 2.3.0
build.3027. Only applies to Screenshots. The same screenshot

  • On web-browser, the screensnot is shown under Today's group
  • Date taken 20-dec, 2025, 5:19:38PM, UTC+00:00 (correct date/time,
    wrong timezone)

image.png (view on web)
https://github.com/user-attachments/assets/e5d61fd7-6e30-4fc2-b5b3-4b9a4b4287df

  • On Android app, the image is shown under 21-Dec-2025 group
  • Date taken 21-Dec-2025, 1:19AM UTC+08:00 (wrong date/time, correct
    timezone)

image.png (view on web)
https://github.com/user-attachments/assets/f3828676-61b4-484b-8b02-65087317a7bf

—
Reply to this email directly, view it on GitHub
https://github.com/immich-app/immich/issues/20148#issuecomment-3677790361,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAI55TBC6HEPVBYZFWHALVT4CU7LXAVCNFSM6AAAAACCJTRQLSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMNZXG44TAMZWGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

@JayCroghan commented on GitHub (Dec 20, 2025): I’m a little concerned this issue is so prevalent yet the devs have ignored it and consider it “stable”. This is quite the issue especially if it requires re-uploading everything and is the major reason I haven’t cut the cable in my existing image cloud. On Sat 20 Dec 2025 at 19:38, aaronntw ***@***.***> wrote: > *aaronntw* left a comment (immich-app/immich#20148) > <https://github.com/immich-app/immich/issues/20148#issuecomment-3677790361> > > Just noticed this issue here on Immich v2.3.1. Android app version 2.3.0 > build.3027. Only applies to Screenshots. The same screenshot > > - On web-browser, the screensnot is shown under Today's group > - Date taken 20-dec, 2025, 5:19:38PM, UTC+00:00 (correct date/time, > wrong timezone) > > image.png (view on web) > <https://github.com/user-attachments/assets/e5d61fd7-6e30-4fc2-b5b3-4b9a4b4287df> > > - On Android app, the image is shown under 21-Dec-2025 group > - Date taken 21-Dec-2025, 1:19AM UTC+08:00 (wrong date/time, correct > timezone) > > image.png (view on web) > <https://github.com/user-attachments/assets/f3828676-61b4-484b-8b02-65087317a7bf> > > — > Reply to this email directly, view it on GitHub > <https://github.com/immich-app/immich/issues/20148#issuecomment-3677790361>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAI55TBC6HEPVBYZFWHALVT4CU7LXAVCNFSM6AAAAACCJTRQLSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMNZXG44TAMZWGE> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >
OVERLORD commented 2026-02-05 12:20:32 +03:00
Author
Owner
Copy Link

@matt-andersen commented on GitHub (Dec 22, 2025):

Just chiming in to say that I have noticed this behaviour on IOS as well, just for screenshots. I am running v2.4.1 of the server and v2.4.1 build.239 for the app.

The screenshot gets saved as the correct date/time but as UTC+00:00. Then once the screenshot gets uploaded to Immich, it then seems to "recalibrate" to AEST (UTC+10:00) which then shoots the image forward ten hours. Meaning, that if I take a screenshot now at 7:30 PM (on Monday), it will show up as tomorrow (Tuesday) after the upload.

Date appears normal across the host and the container:

username@debian:~$ date
Mon 22 Dec 2025 19:24:46 AEST

node@33971d560c41:/usr/src/app$ date
Mon Dec 22 19:33:47 AEST 2025
@matt-andersen commented on GitHub (Dec 22, 2025): Just chiming in to say that I have noticed this behaviour on IOS as well, just for screenshots. I am running `v2.4.1` of the server and `v2.4.1 build.239` for the app. The screenshot gets saved as the correct date/time but as UTC+00:00. Then once the screenshot gets uploaded to Immich, it then seems to "recalibrate" to AEST (UTC+10:00) which then shoots the image forward ten hours. Meaning, that if I take a screenshot now at 7:30 PM (on Monday), it will show up as tomorrow (Tuesday) after the upload. Date appears normal across the host and the container: ``` username@debian:~$ date Mon 22 Dec 2025 19:24:46 AEST ``` ``` node@33971d560c41:/usr/src/app$ date Mon Dec 22 19:33:47 AEST 2025 ```
OVERLORD commented 2026-02-05 12:20:32 +03:00
Author
Owner
Copy Link

@Telesphoreo commented on GitHub (Jan 10, 2026):

Just chiming in to say that I have noticed this behaviour on IOS as well, just for screenshots. I am running v2.4.1 of the server and v2.4.1 build.239 for the app.

The screenshot gets saved as the correct date/time but as UTC+00:00. Then once the screenshot gets uploaded to Immich, it then seems to "recalibrate" to AEST (UTC+10:00) which then shoots the image forward ten hours. Meaning, that if I take a screenshot now at 7:30 PM (on Monday), it will show up as tomorrow (Tuesday) after the upload.

Date appears normal across the host and the container:

username@debian:~$ date
Mon 22 Dec 2025 19:24:46 AEST

node@33971d560c41:/usr/src/app$ date
Mon Dec 22 19:33:47 AEST 2025

I notice the same issue of screenshots being saved as GMT +00:00. It has the correct date and time, just the wrong timezone. However, they never "recalibrate" to my timezone. They seem to stay at GMT +00:00 for me. How long does it take for you to see the image recalibrate? Because it stays at GMT +00:00 for me when after they're uploaded to Immich.

@Telesphoreo commented on GitHub (Jan 10, 2026): > Just chiming in to say that I have noticed this behaviour on IOS as well, just for screenshots. I am running `v2.4.1` of the server and `v2.4.1 build.239` for the app. > > The screenshot gets saved as the correct date/time but as UTC+00:00. Then once the screenshot gets uploaded to Immich, it then seems to "recalibrate" to AEST (UTC+10:00) which then shoots the image forward ten hours. Meaning, that if I take a screenshot now at 7:30 PM (on Monday), it will show up as tomorrow (Tuesday) after the upload. > > Date appears normal across the host and the container: > > ``` > username@debian:~$ date > Mon 22 Dec 2025 19:24:46 AEST > ``` > > ``` > node@33971d560c41:/usr/src/app$ date > Mon Dec 22 19:33:47 AEST 2025 > ``` I notice the same issue of screenshots being saved as GMT +00:00. It has the correct date and time, just the wrong timezone. However, they never "recalibrate" to my timezone. They seem to stay at GMT +00:00 for me. How long does it take for you to see the image recalibrate? Because it stays at GMT +00:00 for me when after they're uploaded to Immich.
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
dependencies
documentation
external-library
format
good first issue
mobile-beta
mobile-beta
mobile-beta
needs-answer
nice to have
pull-request
Mirrored from GitHub Pull Request
 sharing
tech-debt
📱mobile
🖥️web
🗄️server
🧠machine-learning
No Label 📱mobile
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#6512
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?