cgeo: Geokrety logging doesn't work when logging from timezone ahead of CET
To Reproduce: Steps to reproduce the behavior:
- Open some cache (I’m in SU caches)
- Save the log with 'write note type"
- Use Geokrety to set all as visited
- Send the log
Cgeo will show “logging GK”, but this will be really really quick and no log will be added to GK.
I first though it doesn’t work just for “write note” logs, but today it didn’t for for “found” logs as well…
Version of c:geo used: You will find the c:geo version in c:geo Menu -> About c:geo
Is the problem reproducible: Yes / often
Screenshots: You may attach screenshots if applicable and helpful to explain your problem
System information:
Attach system information here if available (see c:geo Menu -> About c:geo -> Swipe right to System)
Keep the apostrophe at beginning and end to have it properly formatted
Additional context: e.g. Reference to other issues, projects, sources, etc.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 18 (18 by maintainers)
Commits related to this issue
- gk: always use CET timezone Fixes #9496 — committed to okainov/cgeo by okainov 4 years ago
- gk: always use CET timezone Fixes #9496 — committed to okainov/cgeo by okainov 4 years ago
- gk: always use CET timezone Fixes #9496 — committed to okainov/cgeo by okainov 4 years ago
- gk: always use CET timezone Fixes #9496 — committed to okainov/cgeo by okainov 4 years ago
- gk: always use CET timezone Fixes #9496 — committed to cgeo/cgeo by okainov 4 years ago
I so also think, that we can use the workaround in our code for now and change it as soon as a new API provides such time zone handling.
@kumy Timezone handling is cause of many bugs. The best solution is to have all involved parties use UTC and require all connectors to deliver UTC in timestamps. All other approaches (also delivering time zone information with the timestamp) shows somehow to be more error prone based on my experience. So using UTC for the GKAPI in future is IMHO the best way.
Actually I have seen this since forever in website UI, but in the UI there was a simple workaround to change the hour, so I didn’t really bother 😃