You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When uploading files via Immich iOS the filesystem-level create-date and modified-date remain messy. In the screenshot below, the storage template extracts the correct Exif dates, while the filesystem dates do not match.
There have been no edits whatsoever to the images on iOS. So it is completely unclear where the "14. December" is coming from, Immich was not even installed yet on that day.
This behaviour was reported in previous issues (#2581, #3900) and has been allegedly fixed with PR #7010. However, this issue persists.
Expected behaviour: the filesystem dates match the exif dates.
The OS that Immich Server is running on
Synology
Version of Immich Server
v1.125.7
Version of Immich Mobile App
v1.125.3 (iOS)
Platform with the issue
Server
Web
Mobile
Your docker-compose.yml content
will provide upon request
Your .env content
will provide upon request
Reproduction steps
Upload past Images via iOS Backup
Check Filesystem Dates
Relevant log output
Additional information
No response
The text was updated successfully, but these errors were encountered:
The bug
When uploading files via Immich iOS the filesystem-level create-date and modified-date remain messy. In the screenshot below, the storage template extracts the correct Exif dates, while the filesystem dates do not match.
There have been no edits whatsoever to the images on iOS. So it is completely unclear where the "14. December" is coming from, Immich was not even installed yet on that day.
This behaviour was reported in previous issues (#2581, #3900) and has been allegedly fixed with PR #7010. However, this issue persists.
Expected behaviour: the filesystem dates match the exif dates.
The OS that Immich Server is running on
Synology
Version of Immich Server
v1.125.7
Version of Immich Mobile App
v1.125.3 (iOS)
Platform with the issue
Your docker-compose.yml content
will provide upon request
Your .env content
Reproduction steps
Relevant log output
Additional information
No response
The text was updated successfully, but these errors were encountered: