mihon
mihon copied to clipboard
Wrong date in history
Steps to reproduce
- Read a couple of different manga.
- Open history list.
- It's gonna show the wrong date (today, yesterday...).
Expected behavior
Show the right date
Actual behavior
Showing the wrong date
Crash logs
No response
Mihon version
0.16.1
Android version
Android version: 10 (SDK 29)
Device
UMIDIGI A9 Pro
Other details
It started with the last version of tachi.
Acknowledgements
- [X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
- [X] I have written a short but informative title.
- [X] If this is an issue with an official extension, I should be opening an issue in the extensions repository.
- [X] I have gone through the FAQ and troubleshooting guide.
- [X] I have updated the app to version 0.16.1.
- [X] I have updated all installed extensions.
- [X] I will fill out all of the requested information in this form.
I have the same issue. It also appears on the Updates tab. I think it has to do with the GMT offset. My offset is -6 and interestingly, the error doesn't occur at night.
On Updates tab I didn't realize, and my timezone is -3, if it helps.
To be clear, the time shows correctly, it just incorrectly groups things as yesterday. It will also move things that are correctly labeled as "Today" to yesterday, but I'm not sure how to replicate that behavior.
joaoandre120's screenshot proves the "yesterday" and "today" lables are (incorrectly) based on GMT and the time is (correctly) based on local timezone. Their timezone is -3 and everything before 21:00 is yesterday and everything after 21:00 is today.
I'm seeing the same behavior in the Updates tab:
My timezone offset is -5.
I tried changing my timezone to UTC and looking at the Update Tab again. The date is correct:
So it must just not be implementing the timezone shift correctly.
EDIT: After changing back to my local timezone and restarting the app, the date issue persists.
Also seems like this was tagged before as an issue #58
Yeah, this looks to me like a duplicate of #58, closing as such.