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
I took a photo at 8:20 this morning and uploaded it to my Piwigo instance through the iOS app (3.0.1). The photo shows in the app with a timestamp of 1:20 AM. I'm in Pacific time, and my server is in the same time zone. My servers docker image was composed with:
environment:
- TZ=America/Los_Angeles
My latest nginx access.log for the piwigo site shows a proper timestamp in the correct timezone:
[06/Jul/2023:10:46:50 -0700]
If I save the image from the app onto my phone, it has the proper timestamp. If I save the image to my PC, it has the proper timestamp. As far as I can tell this is just a display bug in the iOS app, that it's showing -7 hours from the correct timestamp. It's as if the app assumes the image timestamp on the photo is GMT and it's adjusting to display in Pacific time. I think this is a regression from the latest app version, as I never noticed this bug before.
Device: iPhone 14 Pro
OS: iOS 16.5.1
App version 3.0.1
The text was updated successfully, but these errors were encountered:
I took a photo at 8:20 this morning and uploaded it to my Piwigo instance through the iOS app (3.0.1). The photo shows in the app with a timestamp of 1:20 AM. I'm in Pacific time, and my server is in the same time zone. My servers docker image was composed with:
My latest nginx access.log for the piwigo site shows a proper timestamp in the correct timezone:
If I save the image from the app onto my phone, it has the proper timestamp. If I save the image to my PC, it has the proper timestamp. As far as I can tell this is just a display bug in the iOS app, that it's showing -7 hours from the correct timestamp. It's as if the app assumes the image timestamp on the photo is GMT and it's adjusting to display in Pacific time. I think this is a regression from the latest app version, as I never noticed this bug before.
The text was updated successfully, but these errors were encountered: