Closed farahnur42 closed 6 months ago
can you provide details of your filesystem time for that file ?
This throws off the date/time for recently added content on e.g. the Tachiyomi Komga extension <=1.4.55 (1.4.55 switches from fileLastModified to lastModified which is even more incorrect as any metadata change, reordering etc to the book will throw it off - I've asked for this behaviour to be reverted once the timestamps are fixed Komga-side).
Update on this for anyone stumbling upon this issue: 1.4.56 switches over to book.created instead of book.LastModified, and it can be switched back over to fileLastModified in the future.
🎉 This issue has been resolved in 1.10.4
(Release Notes)
Steps to reproduce
Add a newly grabbed/created/modified book to any series
Check fileLastModified for that book from the API response (with e.g. /api/v1/books/{bookId})
Notice that the time is localized, not in UTC.![image](https://github.com/gotson/komga/assets/37258115/01efb081-fcdc-4155-bbd9-92eab5618058)
Expected behavior
The time should be converted to UTC from whatever the configured timezone is, as the API reports it as UTC.
Actual behavior
The time is localized so it can be either in the future or the past depending on your native timezone (in my case perpetually 6h in the future).
Logs
No response
Komga version
1.10.3-master
Operating system
Docker
Installation method
Docker
Other details
This throws off the date/time for recently added content on e.g. the Tachiyomi Komga extension <=1.4.55 (1.4.55 switches from fileLastModified to lastModified which is even more incorrect as any metadata change, reordering etc to the book will throw it off - I've asked for this behaviour to be reverted once the timestamps are fixed Komga-side).
Acknowledgements