-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Detect deleted / moved files properly #15692
Comments
Does signing out and in again help? |
|
My bad, I thought you were talking about the server |
Actually a duplicate of #15079 |
Fortunately, I have backups on my Immich server ;) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The bug
I usually store my photos and videos on my SD card, but unfortunately I had to get a new one, because the old SD card got corrupted.
Due to the corrupted state of the SD card, I was unable to move the files from the old SD card to the new SD card.
Immich thinks a lot of files are locally stored on my SD card, so it'll try and view the images and videos from the SD card. However, it doesn't realize that all the media is gone, because I have a new SD card.
When playing a video, Immich doesn't crash; instead, it stays spinning and doesn't play the video either; I have attached the ADB logs below.
Furthermore, when trying to view an image (stored on the old SD card, with external pictures disabled), it simply doesn't work and the blurhash is displayed instead. Additionally, the ADB log simply spams
Failed to create image decoder with message 'unimplemented'
for each image it tries (and fails) to display.To fix this issue, I propose that Immich always checks if the item exists and if it doesn't exist, it will fallback to the online version of the item stored on the server and try to play that instead.
The OS that Immich Server is running on
Synology DSM 7.2
Version of Immich Server
v1.125.1
Version of Immich Mobile App
v1.125.1 build.2177
Platform with the issue
Your docker-compose.yml content
Your .env content
Reproduction steps
Relevant log output
Additional information
No response
The text was updated successfully, but these errors were encountered: