Incorrect file timestamps resulting in server errors
I have imported some documents from Google photos, some of them were just photos forwarded by others on Whatsapp etc and so werent originally my content. But what happened was the metadata (probably EXIF timestamps?) are WAYYYY in the future. See screenshot example, 143746 years in the future for example (screenshot from Docker's console logs). And these have resulted in Server Errors on the front-end.
The files obviously exist, but because of their timestamp, puts them at the top of our photos libraries which cannot be viewed. What's the best way of dealing with them? Is there a way to find which ones are the affected data and clean them up using either their file system time stamp or put any future dated photos into a review album that don't show up in the main photos page?
Thanks heaps!
10 Replies
Which version of the server are you on?
I'm on v1.82.1 using the docker ghcr.io/immich-app build
Can you update to 1.83? this issue is "fixed" in 1.83
There is no more error on the page. But the root cause is still there:
The image isn't displayed on the web page
But visible on the mobile app
Correct, thus the "fix" you can now remove/download that image and fix the metadata
Except the image isn't visible on the web page. You have to go on the mobile
ok cool thanks heaps. I'll try to get the latest image and see if that works
@Alex could the server not realistically default to the file's creation date or something if the datetime offset is clearly in the future? or potentially stick them all in a system album or something and let the owner decide what to do with the pic (just show it in the album without timelines, but sorted in file creation date order?)
That is the plan, to build some sort of troubled view to manually resolve those files