leits / MeetingBar

🇺🇦 Your meetings at your fingertips in the macOS menu bar
https://meetingbar.app
Apache License 2.0
4.43k stars 191 forks source link

Bug: Delegated calendars not appearing in MeetingBar #506

Closed scottsb closed 1 year ago

scottsb commented 1 year ago

App version 4.0.6

Installation source App Store

Describe the bug When integrating using native macOS calendar integration, my "delegated" calendars are not appearing as options in MeetingBar, whether read-only or read/write. These are calendars owned by other Google accounts that are shared with me. The main use case is my personal Google calendar which is shared (read/write) with my work Google Workspace account.

To Reproduce Steps to reproduce the behavior:

  1. Share a calendar from one Google account to another. (Receiving account might specifically need to be a Google Workspace account, but I've not confirmed.)
  2. Set up the Google account receiving the share in macOS Calendar.
  3. Enable the shared Google account as a displayed "delegated" calendar in macOS Calendar.
  4. Configure MeetingBar to use the native macOS Calendar integration.
  5. View the list of calendars in MeetingBar. Note that the shared calendar does not appear.

Expected behavior All calendars that appear in macOS calendar are available in Meeting Bar.

Screenshots List of calendars in macOS Calendar app: SCR-20220913-j5t

List of calendars in MeetingBar: SCR-20220913-j77

Desktop (please complete the following information):

scottsb commented 1 year ago

This seems similar to #212 but that was supposed to have been fixed already.

leits commented 1 year ago

Hi @scottsb,

Thanks for the report! I found out why it can't get delegated sources right after the first access granting, but after the app restart, it must be there. Can you check?

scottsb commented 1 year ago

@leits Yes, you're right: it is there after restarting. I had never gone back into the settings screen after first installing and submitting this issue. Would be great to get that zero-state bug fixed, but thanks for pointing out the effective workaround: it solves the issue for my own personal purposes.

leits commented 1 year ago

@scottsb, great! Added the bug fix to the next release scope (4.2.0)