Auto Timezone leads to errors in calendar app

prog-amateur

Re: Odd issues with native UT Alarm clock. [Solved]

Hello, I open a new thread as the above is marked as solved, but I consider the solution as a short-term workaround. Also, my device is a Nexus 5, but I think my issue can be cross devices :

When I sync calendars with Nextcloud account, I can see that events in the Ubuntu Touch calendar app are in the wrong time zone (I am on UTC+2 and calendar adds + 2 hours).
One important thing to consider : the calendar from the notification bar displays the correct time zone, while the hour in the application is delayed.
If I use this workaround (to select a UTC+0 city like Rabat and correct time manually, meaning I have to change time in summer and winter by myself), then the calendar app displays events in the correct time.
Also, there is neither popup nor sound despite the fact that the option has been enabled (is is due to this offset ?)

Please, could you confirm and check this issue ?

Thank you very much for your help.

Keneda

I have timezone like yours, UTC+2 and clock setting on auto, and everything works fine, alarm and calendar app + corresponding notifications.
But i can't test Nextcloud as i don't have any account.

prog-amateur

@keneda Hello and thank you,

I have tested an event from the smartphone : I can have notifications, but if the event has been imported from Nextcloud, then there is +2 hours and no notification (despite the fact that notifications are enabled in the settings).

Mou du GNU

I have the same timezone and the same problem with +2hrs. If I use the workaround, the app displays the correct time for my events. The problem is I can't create an event from the phone at the right time because it will be +2hrs on Nextcloud.
So far I haven't found a way to make it work properly both ways

arubislander

@mou-du-gnu I don't understand the search for work arounds while this is obviously a bug in the synchronisation routine with nextcloud. Has there already been an issue raised for this? It needs to be fixed in the sync software, since as you have seen no work-around will work for all the different usecases of the calendar.