extensions: [Apple Reminders] Getting SwiftError (Could not get any data) when opening My Reminders command
Extension
https://raycast.com/raycast/apple-reminders
Description
Error:
SwiftError
at ChildProcess.<anonymous> (/Users/<user>/.config/raycast/extensions/112ad714-bf10-4ccc-a70f-4232bb2241a5/my-reminders.js:50:13280)
at ChildProcess.emit (node:events:517:28)
at ChildProcess.emit (node:domain:489:12)
at maybeClose (node:internal/child_process:1098:16)
at Socket.<anonymous> (node:internal/child_process:450:11)
at Socket.emit (node:events:517:28)
at Socket.emit (node:domain:489:12)
at Pipe.<anonymous> (node:net:350:12)
Steps To Reproduce
Open My Reminders
(privacy permissions granted).
Current Behaviour
Nothing loads, error.
Expected Behaviour
To load.
Extra info
Creating reminders works (although lists do not load in that view).
About this issue
- Original URL
- State: closed
- Created 8 months ago
- Comments: 33 (11 by maintainers)
Awesome, can confirm it now works, thank you!
I took a deeper look at that and if you run it locally, you get a much more helpful error:
Instead of just:
So there’s two issues here. The first one is the Apple Reminders one that I’ll fix in the following hours thanks to you. The second one has to do with how we’re sending the errors in production. We’ll follow up on that so that if we have other errors in the future, it’ll be way easier to identify the cause.
Anyway, thanks again for your help. I’ll ship the PR soon 🙌
The source is indeed accessible here: https://github.com/raycast/extensions/tree/main/extensions/apple-reminders/swift/AppleReminders
So it means that it’s not something related to the swift/js bridge, but something related to the swift code itself. I’ll see what we can do - but that was already a big help, we made some progress, thanks!
It returns
zsh: trace trap ./AppleReminders getReminders
I ran this from
iTerm
(latest) where it also has access to Reminders. Tried again from Apple’s ownTerminal
same thing.@thomaslombart Seeing how the “legacy” extension worked just fine and this issue isn’t getting any love, would it at least be possible to get the legacy extension back?
Hey @rolandleth, sorry for the late reply. We’ll investigate this bug. Thanks for reporting the issue and for your patience! 😊