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

Stacked assets (including locked) displayed independently in memories #6152

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

Originally created by @dekzter on GitHub (May 28, 2025).

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

  • Yes

The bug

When memories for a day are generated, it includes assets that are stacked together. This also includes assets that have been locked. I believe that if assets are stacked and then locked, it may only be locking the primary asset, hiding all from the timeline view. But when memories are generated, it is not differentiating between stacked assets. This causes assets that are stacked to show all assets in the memory as well as stacked assets that belong to a primary asset that was locked.

Related to the comment in this closed issue: https://github.com/immich-app/immich/issues/18529#issuecomment-2916006376

The OS that Immich Server is running on

Docker - Proxmox 8.3.5

Version of Immich Server

1.134.0

Version of Immich Mobile App

1.134.0

Platform with the issue

  • Server
  • Web
  • Mobile

Your docker-compose.yml content

N/A

Your .env content

N/A

Reproduction steps

  1. Stack assets together

  2. Generate memories

  3. See all stacked assets are visible

  4. Stack assets together

  5. Lock stack of assets

  6. See that the stacked assets are in memories, but the primary (locked) asset is not

Relevant log output

Additional information

No response

Originally created by @dekzter on GitHub (May 28, 2025). ### I have searched the existing issues, both open and closed, to make sure this is not a duplicate report. - [x] Yes ### The bug When memories for a day are generated, it includes assets that are stacked together. This also includes assets that have been locked. I believe that if assets are stacked and then locked, it may only be locking the primary asset, hiding all from the timeline view. But when memories are generated, it is not differentiating between stacked assets. This causes assets that are stacked to show all assets in the memory as well as stacked assets that belong to a primary asset that was locked. Related to the comment in this closed issue: https://github.com/immich-app/immich/issues/18529#issuecomment-2916006376 ### The OS that Immich Server is running on Docker - Proxmox 8.3.5 ### Version of Immich Server 1.134.0 ### Version of Immich Mobile App 1.134.0 ### Platform with the issue - [x] Server - [ ] Web - [ ] Mobile ### Your docker-compose.yml content ```YAML N/A ``` ### Your .env content ```Shell N/A ``` ### Reproduction steps 1. Stack assets together 2. Generate memories 3. See all stacked assets are visible 1. Stack assets together 2. Lock stack of assets 3. See that the stacked assets are in memories, but the primary (locked) asset is not ### Relevant log output ```shell ``` ### Additional information _No response_
OVERLORD added the 🗄️server label 2026-02-05 12:03:40 +03:00
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 🗄️server
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#6152
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?