immich-app/immich
1
0
Fork 0
mirror of https://github.com/immich-app/immich.git synced 2026-02-05 00:30:57 +03:00
Code Issues 18 Packages Projects Releases 10 Wiki Activity

[BUG] Images in incorrect order #297

New Issue
Closed
opened 2026-02-04 19:25:10 +03:00 by OVERLORD · 14 comments
OVERLORD commented 2026-02-04 19:25:10 +03:00
Owner
Copy Link

Originally created by @gabriel-gfs on GitHub (Sep 11, 2022).

Describe the bug
These two pictures have a certain timestamp they appear in the wrong order in immich.
20220819-IMG_9066

20220819_121927

Task List

  • I have read thoroughly the README setup and installation instructions.
  • I have included my docker-compose file.
  • I have included information on my machine, and environment.
version: "3.8"

services:
  immich-server:
    image: altran1502/immich-server:latest
    entrypoint: ["/bin/sh", "./start-server.sh"]
    volumes:
      - ${UPLOAD_LOCATION}:/usr/src/app/upload
    env_file:
      - .env
    environment:
      - NODE_ENV=production
    depends_on:
      - redis
      - database
    restart: always

  immich-microservices:
    image: altran1502/immich-server:release
    entrypoint: ["/bin/sh", "./start-microservices.sh"]
    volumes:
      - ${UPLOAD_LOCATION}:/usr/src/app/upload
    env_file:
      - .env
    environment:
      - NODE_ENV=production
    depends_on:
      - redis
      - database
    restart: always

  immich-machine-learning:
    image: altran1502/immich-machine-learning:release
    entrypoint: ["/bin/sh", "./entrypoint.sh"]
    volumes:
      - ${UPLOAD_LOCATION}:/usr/src/app/upload
    env_file:
      - .env
    environment:
      - NODE_ENV=production
    depends_on:
      - database
    restart: always

  immich-web:
    image: altran1502/immich-web:release
    entrypoint: ["/bin/sh", "./entrypoint.sh"]
    env_file:
      - .env
    restart: always

  redis:
    container_name: immich_redis
    image: redis:6.2
    restart: always

  database:
    container_name: immich_postgres
    image: postgres:14
    env_file:
      - .env
    environment:
      POSTGRES_PASSWORD: ${DB_PASSWORD}
      POSTGRES_USER: ${DB_USERNAME}
      POSTGRES_DB: ${DB_DATABASE_NAME}
      PG_DATA: /var/lib/postgresql/data
    volumes:
      - pgdata:/var/lib/postgresql/data
    restart: always

  immich-proxy:
    container_name: immich_proxy
    image: altran1502/immich-proxy:release
    ports:
      - 2283:80
    logging:
      driver: none
    depends_on:
      - immich-server
    restart: always

volumes:
  pgdata:

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
The images appear in correct order.

System

  • Phone OS: Android 12/12L
  • Server Version: v1.28.2
Originally created by @gabriel-gfs on GitHub (Sep 11, 2022). **Describe the bug** These two pictures have a certain timestamp they appear in the wrong order in immich. ![20220819-IMG_9066](https://user-images.githubusercontent.com/36446511/189529145-79cfae4b-a4b5-46ad-b181-e49010b86a6f.jpg) ![20220819_121927](https://user-images.githubusercontent.com/36446511/189529147-41c69366-1028-44a1-994b-fe06b9f80526.jpg) **Task List** - [x] I have read thoroughly the README setup and installation instructions. - [x] I have included my `docker-compose` file. - [x] I have included information on my machine, and environment. ``` version: "3.8" services: immich-server: image: altran1502/immich-server:latest entrypoint: ["/bin/sh", "./start-server.sh"] volumes: - ${UPLOAD_LOCATION}:/usr/src/app/upload env_file: - .env environment: - NODE_ENV=production depends_on: - redis - database restart: always immich-microservices: image: altran1502/immich-server:release entrypoint: ["/bin/sh", "./start-microservices.sh"] volumes: - ${UPLOAD_LOCATION}:/usr/src/app/upload env_file: - .env environment: - NODE_ENV=production depends_on: - redis - database restart: always immich-machine-learning: image: altran1502/immich-machine-learning:release entrypoint: ["/bin/sh", "./entrypoint.sh"] volumes: - ${UPLOAD_LOCATION}:/usr/src/app/upload env_file: - .env environment: - NODE_ENV=production depends_on: - database restart: always immich-web: image: altran1502/immich-web:release entrypoint: ["/bin/sh", "./entrypoint.sh"] env_file: - .env restart: always redis: container_name: immich_redis image: redis:6.2 restart: always database: container_name: immich_postgres image: postgres:14 env_file: - .env environment: POSTGRES_PASSWORD: ${DB_PASSWORD} POSTGRES_USER: ${DB_USERNAME} POSTGRES_DB: ${DB_DATABASE_NAME} PG_DATA: /var/lib/postgresql/data volumes: - pgdata:/var/lib/postgresql/data restart: always immich-proxy: container_name: immich_proxy image: altran1502/immich-proxy:release ports: - 2283:80 logging: driver: none depends_on: - immich-server restart: always volumes: pgdata: ``` **To Reproduce** Steps to reproduce the behavior: 1. Go to '...' 2. Click on '....' 3. Scroll down to '....' 4. See error **Expected behavior** The images appear in correct order. **System** - Phone OS: Android 12/12L - Server Version: v1.28.2
OVERLORD commented 2026-02-04 19:25:22 +03:00
Author
Owner
Copy Link

@panoti commented on GitHub (Sep 12, 2022):

Hi @gabriel-gfs, the file 20220819-IMG_9066 is not found. Can you re-upload again?

@panoti commented on GitHub (Sep 12, 2022): Hi @gabriel-gfs, the file `20220819-IMG_9066` is not found. Can you re-upload again?
OVERLORD commented 2026-02-04 19:25:35 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Sep 13, 2022):

Hi @gabriel-gfs Here are the two timestamp I have after uploading by the web app

Image 1

Screen Shot 2022-09-12 at 23 41 39

EXIF

Screen Shot 2022-09-12 at 23 46 57

TIFF

Screen Shot 2022-09-12 at 23 45 55

Image 2

Screen Shot 2022-09-12 at 23 41 47

EXIF

Screen Shot 2022-09-12 at 23 46 30

TIFF

Screen Shot 2022-09-12 at 23 46 19

Which one do you expect to be the correct one?

@panoti I think this is the problem, you faced, correct?

@alextran1502 commented on GitHub (Sep 13, 2022): Hi @gabriel-gfs Here are the two timestamp I have after uploading by the web app # Image 1 <img width="661" alt="Screen Shot 2022-09-12 at 23 41 39" src="https://user-images.githubusercontent.com/27055614/189810613-d842e197-1146-4205-965e-9f66bacaf6e2.png"> ## EXIF <img width="352" alt="Screen Shot 2022-09-12 at 23 46 57" src="https://user-images.githubusercontent.com/27055614/189811136-21942e3b-33b4-404b-8908-8d639ca1309b.png"> ## TIFF <img width="343" alt="Screen Shot 2022-09-12 at 23 45 55" src="https://user-images.githubusercontent.com/27055614/189810995-bf1ecb81-6511-4db3-bff1-3bbaf44b9353.png"> # Image 2 <img width="1311" alt="Screen Shot 2022-09-12 at 23 41 47" src="https://user-images.githubusercontent.com/27055614/189810617-bf94a6a1-0b05-41c9-a7a9-802a42fd65d4.png"> ## EXIF <img width="308" alt="Screen Shot 2022-09-12 at 23 46 30" src="https://user-images.githubusercontent.com/27055614/189811079-55d44105-e4d0-44c5-8878-2ddcef4eeebd.png"> ## TIFF <img width="249" alt="Screen Shot 2022-09-12 at 23 46 19" src="https://user-images.githubusercontent.com/27055614/189811047-e2cc0a5b-b2fb-43d4-8fb4-a80d0f7ee989.png"> Which one do you expect to be the correct one? @panoti I think this is the problem, you faced, correct?
OVERLORD commented 2026-02-04 19:25:44 +03:00
Author
Owner
Copy Link

@panoti commented on GitHub (Sep 13, 2022):

@alextran1502 same as me. It comes from time zone problem. But idk whether @gabriel-gfs is talking about that or not.

@panoti commented on GitHub (Sep 13, 2022): @alextran1502 same as me. It comes from time zone problem. But idk whether @gabriel-gfs is talking about that or not.
OVERLORD commented 2026-02-04 19:26:02 +03:00
Author
Owner
Copy Link

@gabriel-gfs commented on GitHub (Sep 13, 2022):

Hi @gabriel-gfs Here are the two timestamp I have after uploading by the web app

Image 1

Screen Shot 2022-09-12 at 23 41 39

EXIF

Screen Shot 2022-09-12 at 23 46 57

TIFF

Screen Shot 2022-09-12 at 23 45 55

Image 2

Screen Shot 2022-09-12 at 23 41 47

EXIF

Screen Shot 2022-09-12 at 23 46 30

TIFF

Screen Shot 2022-09-12 at 23 46 19

Which one do you expect to be the correct one?

@panoti I think this is the problem, you faced, correct?

image
This is the order that is displayed in the timeline of immich, ergo the picture with the later timestamp is displyed earlier than the picture wiht the earlier timestamp.

@gabriel-gfs commented on GitHub (Sep 13, 2022): > Hi @gabriel-gfs Here are the two timestamp I have after uploading by the web app > > # Image 1 > <img alt="Screen Shot 2022-09-12 at 23 41 39" width="661" src="https://user-images.githubusercontent.com/27055614/189810613-d842e197-1146-4205-965e-9f66bacaf6e2.png"> > > ## EXIF > <img alt="Screen Shot 2022-09-12 at 23 46 57" width="352" src="https://user-images.githubusercontent.com/27055614/189811136-21942e3b-33b4-404b-8908-8d639ca1309b.png"> > > ## TIFF > <img alt="Screen Shot 2022-09-12 at 23 45 55" width="343" src="https://user-images.githubusercontent.com/27055614/189810995-bf1ecb81-6511-4db3-bff1-3bbaf44b9353.png"> > > # Image 2 > <img alt="Screen Shot 2022-09-12 at 23 41 47" width="1311" src="https://user-images.githubusercontent.com/27055614/189810617-bf94a6a1-0b05-41c9-a7a9-802a42fd65d4.png"> > > ## EXIF > <img alt="Screen Shot 2022-09-12 at 23 46 30" width="308" src="https://user-images.githubusercontent.com/27055614/189811079-55d44105-e4d0-44c5-8878-2ddcef4eeebd.png"> > > ## TIFF > <img alt="Screen Shot 2022-09-12 at 23 46 19" width="249" src="https://user-images.githubusercontent.com/27055614/189811047-e2cc0a5b-b2fb-43d4-8fb4-a80d0f7ee989.png"> > > Which one do you expect to be the correct one? > > @panoti I think this is the problem, you faced, correct? ![image](https://user-images.githubusercontent.com/36446511/189857908-3f504963-564e-4f49-b958-e5bdee73cfa9.png) This is the order that is displayed in the timeline of immich, ergo the picture with the later timestamp is displyed earlier than the picture wiht the earlier timestamp.
OVERLORD commented 2026-02-04 19:26:15 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Oct 1, 2022):

@gabriel-gfs I think the order is correct, since each image grid starting to display the latest in the day and progress to display the later one. Just like you see the latest images on first, follow by the older images

@alextran1502 commented on GitHub (Oct 1, 2022): @gabriel-gfs I think the order is correct, since each image grid starting to display the latest in the day and progress to display the later one. Just like you see the latest images on first, follow by the older images
OVERLORD commented 2026-02-04 19:26:20 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Oct 12, 2022):

Close with the reason mentioned above

@alextran1502 commented on GitHub (Oct 12, 2022): Close with the reason mentioned above
OVERLORD commented 2026-02-04 19:26:24 +03:00
Author
Owner
Copy Link

@gabriel-gfs commented on GitHub (Oct 12, 2022):

Sry i didnt respond earlier. The issue does not appear to be fixed. The images are not in the correct order as this is not in the timeline but rather in a album where the timeline is the other way around so the later image should appear later and not earlier.

@gabriel-gfs commented on GitHub (Oct 12, 2022): Sry i didnt respond earlier. The issue does not appear to be fixed. The images are not in the correct order as this is not in the timeline but rather in a album where the timeline is the other way around so the later image should appear later and not earlier.
OVERLORD commented 2026-02-04 19:26:34 +03:00
Author
Owner
Copy Link

@gabriel-gfs commented on GitHub (Oct 12, 2022):

Screenshot 2022-10-12 122217
As is probably visible in this there should be no sorting in which this is the correct order as the timestamps are all over the place

@gabriel-gfs commented on GitHub (Oct 12, 2022): ![Screenshot 2022-10-12 122217](https://user-images.githubusercontent.com/36446511/195319636-3614a065-e258-4367-b35b-2c010299552e.png) As is probably visible in this there should be no sorting in which this is the correct order as the timestamps are all over the place
OVERLORD commented 2026-02-04 19:26:39 +03:00
Author
Owner
Copy Link

@zackpollard commented on GitHub (Oct 12, 2022):

Would you be able to provide that full set of photos so we have more of a dataset to test against?

@zackpollard commented on GitHub (Oct 12, 2022): Would you be able to provide that full set of photos so we have more of a dataset to test against?
OVERLORD commented 2026-02-04 19:26:51 +03:00
Author
Owner
Copy Link

@gabriel-gfs commented on GitHub (Oct 12, 2022):

Sent it via Discord

@gabriel-gfs commented on GitHub (Oct 12, 2022): Sent it via Discord
OVERLORD commented 2026-02-04 19:27:00 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Jan 17, 2023):

Fixed in #1326

@alextran1502 commented on GitHub (Jan 17, 2023): Fixed in #1326
OVERLORD commented 2026-02-04 19:27:15 +03:00
Author
Owner
Copy Link

@gabriel-gfs commented on GitHub (Jan 19, 2023):

Screenshot 2022-10-12 122217 As is probably visible in this there should be no sorting in which this is the correct order as the timestamps are all over the place

These pictures remain in incorrect order as you can see in this
image

@gabriel-gfs commented on GitHub (Jan 19, 2023): > ![Screenshot 2022-10-12 122217](https://user-images.githubusercontent.com/36446511/195319636-3614a065-e258-4367-b35b-2c010299552e.png) As is probably visible in this there should be no sorting in which this is the correct order as the timestamps are all over the place These pictures remain in incorrect order as you can see in this ![image](https://user-images.githubusercontent.com/36446511/213400281-18c27641-85c6-448d-af91-52d15e10add6.png)
OVERLORD commented 2026-02-04 19:27:19 +03:00
Author
Owner
Copy Link

@alextran1502 commented on GitHub (Jan 19, 2023):

@gabriel-gfs

Is this the new upload or from the original upload? The fix doesn't applied automatically to the older photos, only to the new upload. We are planning to add a new job to rescan all exif data

@alextran1502 commented on GitHub (Jan 19, 2023): @gabriel-gfs Is this the new upload or from the original upload? The fix doesn't applied automatically to the older photos, only to the new upload. We are planning to add a new job to rescan all exif data
OVERLORD commented 2026-02-04 19:27:34 +03:00
Author
Owner
Copy Link

@gabriel-gfs commented on GitHub (Jan 19, 2023):

No these are old pictures. Thanks for the information. I'll be looking forward to that job. 🤗

@gabriel-gfs commented on GitHub (Jan 19, 2023): No these are old pictures. Thanks for the information. I'll be looking forward to that job. 🤗
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
accessibility
changelog:enhancement
changelog:security
changelog:translation
cli
date-time
documentation
external-library
format
good first issue
needs-answer
nice to have
sharing
tech-debt
📱mobile
🖥️web
🗄️server
🧠machine-learning
No Label
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#297
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?