Timezones are being ignored on iOS #807
Replies: 3 comments
-
|
Hello, If that's not an option, we will modify our desktop/web app bulk change time API to handle this particular case. |
Beta Was this translation helpful? Give feedback.
-
|
I'd like to second the request that the app show the local time of the photos. I've just had a similar issue with the desktop app: when uploading photos with no EXIF time offset it appears to assume the system timezone of the app. It's a fine default but
Given that EXIF doesn't appear to record the time zone, only the offset, it would seem even more important to allow editing the time zone and perhaps prompt the user to do so when the EXIF offset is inconsistent with the assumed time zone. |
Beta Was this translation helpful? Give feedback.
-
|
I'm having the same issue on Android and in the desktop app: I took some photos in locations with timezone UTC-5. Some of the photos I uploaded while still there, the rest of the photos I uploaded back home (UTC+1). Both Android and desktop app, however, seem to interpret the photos' local times as times in my current timezone (UTC+1). As a result, in the photo overview those photos I took in the evening are shown as having been taken the next day in the morning etc. Nevertheless, the Ente app's info button for any given individual photo does show the correct local time, including the timezone offset (@gkoz), e.g. @rachel-carvalho's screenshot showed similar EXIF data. So could it be that, whether or not the offset is stored in the EXIF data, depends on the camera app in question? In my case, I use a Google Pixel w/ Google Camera. Even if the offset weren't present in the EXIF data, since my photos' filenames PS: @rachel-carvalho Would you mind renaming this thread and removing the "on iOS" part since the issues doesn't seem platform-specific? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the bug
When a photo taken on one timezone (ie UTC -3) is uploaded on another timezone (ie UTC -5), its timestamp is the original one but uses the current device's timezone.
So if a photo is taken at 13:00 UTC -3 (16:00 UTC), it's being displayed as 13:00 UTC -5 when viewing on this time zone, instead of 11:00 which is the correct timestamp.
I'm not sure if this is an issue on iOS only or not.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The timestamp should remain correct regardless of timezones. Ideally we'd see the original time in the original timezone.
Screenshots
I'm adding screenshots below.
Smartphone (please complete the following information):
Additional context
I noticed this because another user who I share an album with has photos (taken and uploaded on Android) that should be within minutes of mine but are apart by 2 hours, the difference between my current timezone and the one from the photos. Their photos seem to have the correct timestamp.
✅ Here are screenshots with the details + EXIF of the photo with correct timestamps, taken and uploaded on Android:
❌ Details + EXIF of the iOS photo with incorrect timestamp:
Beta Was this translation helpful? Give feedback.
All reactions