Upon invitations, calendar "personal" is created although there is a valid calender

[nursoda]

Calendar 1.5.3 on NC12.0 (release)

Steps to reproduce

1. create a second calendar, name it (say "MyCalendar"), and delete the default calendar "personal"
2. let someone else invite you to a meeting

Expected behaviour The invitation should be processed in MyCalendar

Actual behaviour If calendar "personal" doesn't exist, it's silently created on-the-fly and the invitation is processed there.

Problem is, that if you - like me - only use e.g. Thunderbird Calendar and more or less only use the web interface to maintain the NC server and apps, you don't notice that you have a new calendar, and appointments therein.

I reported this as https://github.com/nextcloud/calendar/issues/466 first but Georg wrote that "If you have another calendar in place, no new calendar should be created."

[ethanopp]

+1

...Even creates another calendar "Personal" if your first calendar is named "Personal"... Resulting in 2 "Personal" calendars...

[MorrisJobke]

cc @georgehrke

[palegrand]

+1
is there any known work-around?

[georgehrke]

Please don't comment with +1, 👍 etc. when you can't add anything new. It's only spamming contributors' mail inboxes for no reason. Use Github Reactions instead.

If there was a known workaround, it would have been posted here.

Thx! :)

[amadeus-torwell]

Sorry to ask one year later, but is there anything that can be done? We would love to fix it ourselves, just getting some advice where to start searching for this bug would be helpful.

Thanks! :)

[nursoda]

Took me a while, too, to reproduce NOW ;-) Bug is still there in NC 13 with current Calendar app. To reproduce, you can do everything within Nextcloud web interface. I was missing that when I tried first.

1a) create a dummy user 1b) create a second calender 1c) delete the default calendar 2a) log in as an existing user on the SAME cloud instance 2b) Create a new meeting, invite the dummy USER (selecting it!) 1d) For dummy, the default calendar is re-created and the meeting was created within that.

Oddly enough, I am shown TWO identical dummy users in step 2b.

[mokkin]

I have realized the issue since NC 14 and reproduced it like @nursoda just yet with NC 15.0.5

To avoid problems in our team I moved my custom named calendar to the auto created "pesonal" one as a workaround.

[biva]

Any update? Still the same problem with NC15 :(

[palegrand]

Still the same problem on NC16 :-(

[georgehrke]

This is done on purpose right now: https://github.com/nextcloud/server/pull/2274

We should introduce an option to define a default calendar (like most other calendar applications outside) and store it in there. If there is no default calendar, take the first writable one (based on calendar order). If there is none, create one.

https://tools.ietf.org/html/rfc6638#section-9.2

[tcitworld]

Note: We now have the setting in server since https://github.com/nextcloud/server/pull/19852 so even though it's not selectable right now (see https://github.com/nextcloud/calendar/pull/2331) we can still use it straight away.

[tcitworld]

Closed by https://github.com/nextcloud/server/pull/32361