Deleted exchange calendars get synced

REPRODUCIBILITY (% or how often): 100%
BUILD ID = OS VERSION (Settings > About product): 4.0.1.48 (Koli)
HARDWARE (XA2, Xperia 10…): Sony Xperia X
UI LANGUAGE: English
REGRESSION: (compared to previous public release: Yes, No, ?): No

DESCRIPTION:

Previously deleted calendars on outlook.com are synced to the Sailfish calendar app via MS Exchange account.

PRECONDITIONS:

Microsoft Exchange Account with previously deleted calendars.

STEPS TO REPRODUCE:

  1. Create and delete a calendar on your MS Exchange account (in my case Outlook.com)
  2. Add MS Exchange account to accounts on Sailfish OS device
  3. Sync MS exchange account including calendars

EXPECTED RESULT:

Only visible calendars on MS exchange account also show up in Sailfish calendar app under ‘manage calenders’.

ACTUAL RESULT:

All calendars ever created (even if deleted afterwards) on MS Exchange account get synced and ahow up in Sailfish calendar app under ‘manage calendars’.

ADDITIONAL INFORMATION:

(Please ALWAYS attach relevant data such as logs, screenshots, etc…)

1 Like

Same here. Issue still not solved.

Hello - any news to this problem? I delete some calendars on outlook365.com and then I delete the exchange account from the phone. After this I wait an the calendars was unvisible. After creating a new exchange account the deleted calendars are be back :(…

Not resolved on 4.3. I still have this problem.

I’m wondering if this bug is related to this one: Calendar settings lost after each reboot

As you say @pherjung, the two bugs could be related, but it’s a little hard to tell. I’ve recorded them both internally and tagged them as “tracked” separately just in case.

Any updates for this issue?
It is still an annoying problem on version 4.4.0.72, on Xperia X 10 II

I made a comment in the other thread somewhat touching this: with my vague memories I think I had this issue with my Android phone in around 2018. And some seem to have similar issues with trying to sync Google calendar with Exchange server. That is, for me it seems to be an issue with Exchange or perhaps with specific Exchange servers.