-
Notifications
You must be signed in to change notification settings - Fork 33
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
No writable calendars are configured for invitations, please check the calendar properties #563
Comments
I have the same issue on TB 102.6.0 (64-bit), Debian 10. |
Initially I created the boolean "calendar.google.enableEmailInvitations" (true), as found in some older Google searches, with no success. I then updated the properties for the Google calendar by specifying the associated email address and was able to accept the invitation. That is when the weirdness started.
|
I'm also having the same issue with TB 102.8.0 on MacOS 11.7.4 and add-on version 102.0.3. My Google calendar and tasks are visible in TB, but when I receive an email calendar invite, it shows the message "No writable calendars are configured for invitations, please check the calendar properties." The Read-only checkbox in the calendar properties is not checked. |
Same issue here (TB 102.11.0 64-bit on Windows). I can only accept invites in a local calendar, but I need them in a Google calendar. |
The settings you mention are available in the add-on preferences, can you make sure the checkboxes related to attendees and scheduling are checked? Afterwards, please unsubscribe and re-subscribe to your calendars. |
The checkboxes are there on the add-on settings page, and I checked them as desired. However, on the calendar settings page, some controls seem to be missing. For example, there is no control for selecting an email address, like there is for local calendars. I am sure it was there and then disappeared, but since then the calendar does not accept invitations. |
You should only be able to schedule in the primary calendar, i.e. the one with your name on it. The email should be set automatically, hence the controls are missing. I'd suggest rather enabling the option in Google Calendar to show invitations in the calendar, than to accept invitation emails into the calendar. We have quite a few reporters here with potentially different issues, this makes it a bit hard to track. I'm going to need some debug logging as described in the readme, and more details on which calendar, what the invitation looks like, etc. |
Then in my case this is probably the issue, since I was using a sub-calendar (one that I created as a new calendar in the Google calendar app). When working with a primary Google calendar it works. I hope that sub-calendars will be supported in the future. Thanks for your help Philipp! |
I have the same problem on Thunderbird 115.3.1 (64-bit) (Ubuntu) with the most recent add-on version. I'm trying to add event invitations from elsewhere (ical files are not from Google) and cannot add them with the "No writable calendar..." message. |
Hi folks. Quite a few reporters in this issue, I'm going to close this out. If you are having this issue please make sure you are scheduling in your primary calendar. If there are other issues please open individual issues and make sure to provide debug logs. |
Describe the problem and steps to reproduce it:
Connect to Google Workspace account calendar through the addon.
Receive an event invitation at Google Workspace email for the same account.
What happened?
A message is shown "No writable calendars are configured for invitations, please check the calendar properties"
What did you expect to happen?
I should be able to accept/reject the invite.
Anything else we should know?
TB 102.6.0
Provider for Google Calendar 102.0.3
Debian 11
Under the calendar properties "Read Only" is unchecked, Location is correct.
The calendar synchronizes and shows events.
I searched through old issues where a solution was to change a config editor setting that no longer exists and saw that this was fixed in 91. This doesn't work in 102 for me.
The text was updated successfully, but these errors were encountered: