You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Events with attendees that have an invalid (nil) email address cause Meetingbar to crash
To Reproduce
Create a meeting with one or more attendees.
At least one attendee should have a nil email address. In my case, it is a Microsoft Exchange calendar that has multiple attendees with x500 email addresses. e.g. /o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPXXX)/cn=Recipients/cn=5e17910fea164345b55313d0f6f4fXXX-John Smit. This email address shows as nil
Launch Meetingbar (immediate exit)
Launch Meetingbar via cli, returns:
2022-05-22 10:42:12.375491-0400 MeetingBar[3301:16960432] Category EVENT was registered
2022-05-22 10:42:12.375527-0400 MeetingBar[3301:16960432] Category SNOOZE_EVENT was registered
MeetingBar/EKEventStore.swift:105: Fatal error: Unexpectedly found nil while implicitly unwrapping an Optional value
2022-05-22 10:42:12.464587-0400 MeetingBar[3301:16959618] MeetingBar/EKEventStore.swift:105: Fatal error: Unexpectedly found nil while implicitly unwrapping an Optional value
Expected behavior
Expected launch w/o issue
Screenshots
Desktop (please complete the following information):
macOS version: 12.3.1
The text was updated successfully, but these errors were encountered:
App version
Installation source
Describe the bug
To Reproduce
Create a meeting with one or more attendees.
At least one attendee should have a
nil
email address. In my case, it is a Microsoft Exchange calendar that has multiple attendees with x500 email addresses. e.g./o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPXXX)/cn=Recipients/cn=5e17910fea164345b55313d0f6f4fXXX-John Smit
. This email address shows as nilLaunch Meetingbar (immediate exit)
Launch Meetingbar via cli, returns:
Expected behavior
Screenshots
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: