Skip to content

Conversation

@brandonkboswell
Copy link

  • Replaced CalendarAccessWorker, RemindersAccessWorker, and RemindersFetchWorker with thread-safe context structs
  • Use ThreadSafeFunction instead of AsyncWorker for cross-thread callbacks
  • Capture shared_ptr by value in lambdas to ensure promise lifetime
  • Fixes segmentation fault when macOS permission dialog callback fires

This fixes crash at memory address 0x260 when users grant calendar permissions.

 - Replaced CalendarAccessWorker, RemindersAccessWorker, and RemindersFetchWorker with thread-safe context
 structs
 - Use ThreadSafeFunction instead of AsyncWorker for cross-thread callbacks
 - Capture shared_ptr by value in lambdas to ensure promise lifetime
 - Fixes segmentation fault when macOS permission dialog callback fires

 This fixes crash at memory address 0x260 when users grant calendar permissions.
@brandonkboswell
Copy link
Author

@dacay let me start by saying I'm not an Objective-C coder or a Swift coder of any kind. I found that EventKit-node was crashing after accepting permissions when I went to use it. I had Claude code fix that issue, and the code that's in this fork seems to continue to maintain all the functionality that existed in your version, but doesn't crash after receiving proper permissions on macOS 26.2 Tahoe.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant