nextcloud / nextcloud/calendar
Invitation email with iCal file from NC32 not fully recognized in NC33
Open
Nobody has claimed this yet.
0. to triage
bug
needs info
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 332
- Avg merge
- 16h 13m
- Merged PRs (30d)
- 137
Description
Steps to reproduce
- Open Calendar in NC 32, create an event and invite an attendee email that has their email and calendar set up in NC 33.
- In NC Mail in NC 33, see that the invitation email is recognized and the buttons "accept, decline ..." are displayed.
- However, in the Calendar in NC 33 the event is not displayed as pending and there is no notification about the invitation. Also, in a connected calDAV client like Apple Calendar the invitation is not presented.
Calendar Versions:
NC 32: 6.4.1
NC 33: 6.4.1
Expected behavior
The invitation should be presented in NC Calendar, the notifications and calDAV clients.
Actual behavior
The invitation is only presented in Nextcloud Mail.
Calendar app version
6.4.1
CalDAV-clients used
No response
Browser
No response
Client operating system
No response
Server operating system
No response
Web server
None
Database engine version
None
PHP engine version
None
Nextcloud version
No response
Updated from an older installed version or fresh install
None
List of activated apps
Nextcloud configuration
Web server error log
Log file
Browser log
Additional info
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the NC32-to-NC33 invitation flow in NC Mail and Calendar, then inspect how the invitation reaches the CalDAV client. Done means the invitation appears as pending in NC Calendar, generates its notification, and is presented by a connected CalDAV client.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100