We have moved to a new Sailfish OS Forum. Please start new discussions there.
1 | initial version | posted 2014-04-14 04:44:39 +0200 |
All of my google calendar events are offset by -12 hours. I am using 1.0.5.16, but I was experiencing the same issue on 1.0.4.20.
My timezone is set to automatic on my Jolla: GMT -7:00 (-6:00) Edmonton, Canada. I experience the same issue if I manually set it. This is also the current timezone on my google calendar settings.
If I add a new event on the calendar app, it is saved to google calendar with the correct time, but the event on the calendar app then switches to -12 hours.
Here is the database entry of a newly created event scheduled to start April 13 at 20:00. The DateStart and DateStartLocal look correct.
2294|012ba221-1e6d-488e-8981-004e5f39fc83|Event|Tester2||1397440800|1397419200|America/Edmonton|0|1397444400|1397422800|America/Edmonton|0|0|||0|255.0|255.0|0||1397439027|1397439027|1397439027|1||||0|0|0|||urn:x-ical:bef40561-d69f-4e7b-953a-a72c4ce28e82|bef40561-d69f-4e7b-953a-a72c4ce28e82|0|0|0|0|0||0|||0
Here is the same database entry a couple of seconds later. The DateStart and DateStartLocal have both shifted by -12 hours.
2294|012ba221-1e6d-488e-8981-004e5f39fc83|Event|Tester2||1397397600|1397376000|America/Edmonton|0|1397401200|1397379600|America/Edmonton|0|0|||0|255.0|255.0|0||1397439027|1397439029|1397439029|2||||0|0|0|||urn:x-ical:bef40561-d69f-4e7b-953a-a72c4ce28e82|bef40561-d69f-4e7b-953a-a72c4ce28e82|0|0||0|0|0|0|||0
Any workarounds or suggestions for further troubleshooting?
2 | No.2 Revision |
All of my google calendar events are offset by -12 hours. I am using 1.0.5.16, but I was experiencing the same issue on 1.0.4.20.
My timezone is set to automatic on my Jolla: GMT -7:00 (-6:00) Edmonton, Canada. I experience the same issue if I manually set it. This is also the current timezone on my google calendar settings.
If I add a new event on the calendar app, it is saved to google calendar with the correct time, but the event on the calendar app then switches to -12 hours.
Here is the database entry of a newly created event scheduled to start April 13 at 20:00. The DateStart and DateStartLocal look correct.
2294|012ba221-1e6d-488e-8981-004e5f39fc83|Event|Tester2||1397440800|1397419200|America/Edmonton|0|1397444400|1397422800|America/Edmonton|0|0|||0|255.0|255.0|0||1397439027|1397439027|1397439027|1||||0|0|0|||urn:x-ical:bef40561-d69f-4e7b-953a-a72c4ce28e82|bef40561-d69f-4e7b-953a-a72c4ce28e82|0|0|0|0|0||0|||02294|012ba221-1e6d-488e-8981-004e5f39fc83|Event|Tester2||1397440800|1397419200|America/Edmonton|0|
1397444400|1397422800|America/Edmonton|0|0|||0|255.0|255.0|0||1397439027|1397439027|1397439027|1||||0|0|0|||
urn:x-ical:bef40561-d69f-4e7b-953a-a72c4ce28e82|bef40561-d69f-4e7b-953a-a72c4ce28e82|0|0|0|0|0||0|||0
Here is the same database entry a couple of seconds later. The DateStart and DateStartLocal have both shifted by -12 hours.
2294|012ba221-1e6d-488e-8981-004e5f39fc83|Event|Tester2||1397397600|1397376000|America/Edmonton|0|1397401200|1397379600|America/Edmonton|0|0|||0|255.0|255.0|0||1397439027|1397439029|1397439029|2||||0|0|0|||urn:x-ical:bef40561-d69f-4e7b-953a-a72c4ce28e82|bef40561-d69f-4e7b-953a-a72c4ce28e82|0|0||0|0|0|0|||02294|012ba221-1e6d-488e-8981-004e5f39fc83|Event|Tester2||1397397600|1397376000|America/Edmonton|0|
1397401200|1397379600|America/Edmonton|0|0|||0|255.0|255.0|0||1397439027|1397439029|1397439029|2||||0|0|0|||
urn:x-ical:bef40561-d69f-4e7b-953a-a72c4ce28e82|bef40561-d69f-4e7b-953a-a72c4ce28e82|0|0||0|0|0|0|||0
Any workarounds or suggestions for further troubleshooting?