[beta] Replacing a previously downloaded photo causes duplicates in the mobile timeline

[dagstuan]

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

• Yes

The bug

I'm not entirely sure if this is a duplicate or not, but I've come across an issue where I have downloaded a photo to my phone, and then replaced it in Immich by reuploading a new version from Lightroom. In this case, Immich can't match the hash of the downloaded photo that's on my phone, so I end up with two copies of the same image when Immich backs up the photo that's stored on the phone.

I'm not sure what should be the correct behavior in this case, but it would be nice to not end up with two copies of the same image if it is replaced after having downloaded it to the phone.

I also noticed similar behavior if I manually edit a photo using the native photos app on iOS, Immich then reuploads the edited photo, and I end up with duplicates in the timeline.

The OS that Immich Server is running on

Synology OS

Version of Immich Server

v1.137.3

Version of Immich Mobile App

v1.137.3

Platform with the issue

• Server
• Web
• Mobile

Your docker-compose.yml content

-

Your .env content

-

Reproduction steps

1. Upload a photo to Immich
2. Download the photo to the phone using the Immich app
3. Replace the photo in Immich with one that results in a different hash.
4. Observe duplicates in the Mobile app when the mobile app refreshes the content on the server.

Relevant log output

Additional information

No response

[jrasm91]

The replaceAsset implementation, which I assume you are using from Lightroom is basically mutating the asset and that's causing issues with syncing and tracking. For these reason's we've deprecated replaceAsset and it'd be better to upload a new asset, and then optionally delete the old one instead of "replacing" it

#21791