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
If an event has attendees, and one of them doesn't have a name field, then the event details popup won't appear after clicking on the event cell.
Environment:
Operating System: macOS Sonoma
App Version: 0.15.1 (2262)
Xcode Version: 15 (15A240d)
Steps to reproduce:
Add an event with a list of attendees and ensure that one of them doesn't have a name field (mine is from Microsoft Teams calendar, and the attendee has only an email).
Click on the event cell to show the details popup.
Expected behaviour:
The event details popup appears.
Actual behavior:
Nothing happens, but an assertion failure occurs in AgendaViewController.m:1184.
It turns out that the name property in EKParticipant is nullable. Therefore, I believe it would be better to check if it's nil and, if so, use an alternative (for example, an email).
The text was updated successfully, but these errors were encountered:
Thanks for the report.
I'm kind of flying blind when it comes to attendees since I don't work with any kind of collaboration software and can't really generate good test cases.
Indeed, the code was simply using EKParticipant name. I've changed it to check for nil and fall back to EKParticipant URL.resourceSpecifier (email) or just a dummy string if that too is nil.
Description:
If an event has attendees, and one of them doesn't have a name field, then the event details popup won't appear after clicking on the event cell.
Environment:
Steps to reproduce:
Expected behaviour:
The event details popup appears.
Actual behavior:
Nothing happens, but an assertion failure occurs in
AgendaViewController.m:1184
.Possible solution:
It turns out that the
name
property inEKParticipant
is nullable. Therefore, I believe it would be better to check if it's nil and, if so, use an alternative (for example, an email).The text was updated successfully, but these errors were encountered: