[NameSpaces] Says "something went wrong"
Extension
https://www.raycast.com/GastroGeek/namespaces
Raycast Version
1.88.4
macOS Version
14.6.1
Description
Error:
Error: Command failed with exit code 1: osascript
74:106: execution error: Not authorized to send Apple events to System Events. (-1743)
X9:run-applescript.js:38:21
---
35: timedOut,
36: command: "osascript",
37: options,
38: parentError: new Error(),
39: })
### Steps To Reproduce
configured a space with modifier Command, keycode 18 (the 1 key). when I do those, it ways "something went wrong"
### Current Behaviour
"something went wrong"
### Expected Behaviour
Idk actually, I assume it changes my desktop?
Thank you for opening this issue!
🔔 @GastroGeek @xmok you might want to have a look.
💡 Author and Contributors commands
The author and contributors of GastroGeek/namespaces can trigger bot actions by commenting:
-
@raycastbot close this issueCloses the issue. -
@raycastbot close as not plannedCloses the issue as not planned. -
@raycastbot rename this issue to "Awesome new title"Renames the issue. -
@raycastbot reopen this issueReopens the issue. -
@raycastbot assign meAssigns yourself to the issue. -
@raycastbot good first issueAdds the "Good first issue" label to the issue. -
@raycastbot keep this issue openMake sure the issue won't go stale and will be kept open by the bot.
This reads more like a permissions issue. Please check in your System Settings and ensure that Raycast has required permissions especially "Accessibility". If all permissions are there, then will troubleshoot further.
Thanks for your response, I do have "Accessibility" enabled. Are there other permissions that are necessary as well?
Could be these 2 permissions:
In macOS Ventura (please check your System Settings for your OS version):
- Privacy & Security > Automation > Raycast > Shortcuts Events
- Privacy & Security > Automation > Raycast > System Events
This issue has been automatically marked as stale because it did not have any recent activity.
It will be closed if no further activity occurs in the next 10 days to keep our backlog clean 😊
This issue has been automatically closed due to inactivity.
Feel free to comment in the thread when you're ready to continue working on it 🙂
You can also catch us in Slack if you want to discuss this.