-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dublicating events when accepting #801
Comments
This is exactly why I have a preference for disabling attendees and notifications, when something is considered an accepted invite and when it is just an event being added is just too flaky :( I'm sorry this is happening to you as well! I don't really have great debugging steps, aside from making sure that the correct email is associated with your calendar in the calendar properties. If you are comfortable using a debugger there is a way to step through the code and determine if the organizer/attendee check is working as intended. |
Hello, I have the same problem for the whole team. |
Hello, I have the same problem as well. It looks like that duplicate event is sent where I am organizer. |
Same issue here.
|
I am using the "Provider für Google Kalender" add-on to sync calendar invites that I receive via email to my Google Calendar. However, recently I’ve noticed that when accepting a calendar invite through the add-on, a duplicate of the event is created, and all the previous attendees receive the same invite again, but with me listed as the organizer.
Steps to reproduce:
Receive a calendar invite via email.
Accept the invite using the "Provider for Google" add-on.
A duplicate event appears in the calendar.
The original attendees receive the invite again, but now I am shown as the organizer.
Obviously I expected the event to be added to my calendar without creating duplicates or changing the organizer.
Unfortunately, there are no error messages which i can provide. Please let me know what else I should do to troubleshoot this issue.
The text was updated successfully, but these errors were encountered: