REPRODUCIBILITY (% or how often): 100
BUILD ID: 3.4
HARDWARE (Jolla1, Tablet, XA2,…): X10 and X10plus
UI LANGUAGE: german
REGRESSION: (compared to previous public release: Yes, No, ?):
disabled (sub)calendars with exchange and caldav always reappear again randomly or after sync. I need to disable them often, even without restart
I can confirm that this applies to disabled Google calendars on XA2 as well, so most likely it’s platform independent and applies to any remote calendar.
The calendars become enabled again every time the account is synced.
I can confirm this for personal Outlook account in XA2
May I ask more specifically what do you mean by disabled ? Is this:
I would like to investigate this because with @flypig we have change part of this code to solve the issue of alarm ringing for disabled accounts.
Additionally, may I ask what you mean by “reappear again” ? When you uncheck a calendar in the account setting page, the calendar is not synced anymore, but it is still visible. If you want to hide it from the calendar app, go to this app, and choose “manage calendars” in the pulley menu. Uncheck the calendar there to toggle its visibility.
Ok, thank, got it. One more question if you don’t mind ? They are Exchange calendars, right ? Does it happen also for CalDAV ?
I’ll look at it and give you feedback.
Yes, one is a office 365 exchange account. Another one is a mailbox.org business account. I can use mailbox.org with exchange, showing the same issue. Mailbox can also be accessed by caldav. I just set it up with calDav, and did some testing. seems like there is no issue. So I guess the issue is exchange exclusive. Thanks for looking into it.
I quickly grepped in the code for setIsVisible() which is the KCalCore method to change the visibility of a calendar, in the CalDAV sync plugin and Google sync plugin, without finding it. That’s why I was asking, indeed. The exchange code is closed source sadly, as far as I know. So I cannot check myself. I’ll ask @flypig or Chris Adams, if they could give a look when they have time.
I can confirm this for Google Calendar as well and it’s not a regression. This was also the problem on the previous release. Seems the sync breaks at some point and sets all calendars active again (and the duplicates, other issue, start to reappear).
Well, I think I found the reason for this, or at least a reason introduced in 3.4.0. To avoid alarms ringing for disabled calendars (in the sense of accounts) as it happened previously, we linked the alarm to the visibility of the calendar only. And we setup a binding between account status and visibility. This binding is supposed to be triggered on every status change of the account, but it’s actually not the case. It is firing every time a setting is changed in the account… I need to discuss with @flypig of this, maybe tomorrow if he has time on IRC #SailfishOS channel.
That sounds good; I’ll follow along with your discussions with Chris until the topic comes up.
Cleared calendar db and contacts and removed the account just to see if it helps. Still having this issue. Calendars re-selected to visible after just setting them to not be visible. As in the screencap from apozaf.
@apozaf has raised this as a topic for the Community meeting on Thursday, so hopefully there’ll be an answer for then (or at least, some discussion on the topic).
Same here. Nothing changed that stange behaviour on 4
Darn. We need to investigate this more.
Checked this as I updated to 4.2. Yeah its still an issue that google calendars reappear as visible even though selected as not visible from manage calendars pulley item. I have a lot of organization calendars that are shared to me and I would want to disable them on my phone to see my events.
I cannot reproduce. Is it happening at every sync ?
I think it’s when loosing connection or switching to airplane mode. But not always. hmmm.
Definately after every restart.
I’m sorry, it’s not clear for me how to reproduce.
Looking at the code, one action that definitely triggers the visibility issue:
I still cannot see in the sync code how it can happen during a scheduled sync though : /
If @miqu or @apozaf can provide some steps on how to reproduce, it would be of great help to find a solution. Any other information are good to take also.
