-
Notifications
You must be signed in to change notification settings - Fork 46
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
Document date is wrong, probable timezone issue #45
Comments
Did you configure |
Yes it's set to Europe/Berlin on the paperless docker env |
If I do not set this variable and use the UTC default, it works. |
I can reproduce this issue here. The timestamp comes back from the server as 2021-02-28T23:00:00Z which would be correct for Europe/Berlin. The app currently displays the timestamp in UTC, not the local timezone. I will change the app behaviour to be consistent with the web interface. However, I'm not sure if this is really what the user expects. If I scan a document in March at home, then travel to London, I don't expect it to show up in February. |
Yeah, time zones are tough and are a headache. So it would take the time zone from the server? If the sever stays at home it might still show march. Frequent travelers just should run the sever in UTC ;-) ? |
No, the local time zone from the OS. Changing the server to UTC just fixed the issue because the app currently assumes the date should be displayed in UTC. |
Describe the bug
The date of the document is not matching the date displayed in the app.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The date is viewed as March 1, 2021
Screenshots
Paperless-ng server:
App:
Additional information
Paperless App Version: 0.0.10, f-droid
Do you use Paperless NG as a backend: Paperless-ng 1.4.1
Possible cause
It might be because the display timezone is different in the app and the server. Can the app query the server timezone? In the end of the time it's only dates, not date time, so I am not sure if any timezone logic has to take place.
The text was updated successfully, but these errors were encountered: