warpdotdev
Not authorized to send Apple events to Google Chrome. (-1743)
Dupe Check
- [X] I have searched Warp bugs and there are no duplicates
Describe the bug
I'm using expo and when I try to launch chrome to debug my app, I get the error above. I might me mistaken, but seems to be new problem after upgrade to OSX Sequoia.
The bug appears to be triggered only when new version is available and I need to restart to upgrade. After restart the bug is gone.
To reproduce
osascript -e 'POSIX path of (path to application "google chrome")'
15:50: execution error: Not authorized to send Apple events to Google Chrome. (-1743)
Expected behavior
No response
Screenshots
Operating system
MacOS
Operating system and version
15.0.1
Shell Version
No response
Current Warp version
v0.2024.10.08.08.02.stable_01
Regression
Yes, this bug started recently or with an X Warp version
Recent working Warp date
No response
Additional context
No response
Does this block you from using Warp daily?
Yes, this issue prevents me from using Warp daily.
Is this an issue only in Warp?
Yes, I confirmed that this only happens in Warp, not other terminals.
Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e
None
Hi @gdanov sorry to hear about this. It could be due to the latest version of OSX, which we haven't fully tested Warp on yet. But given the error message, I suspect it may be something with the permissions. Got to you Mac System Settings > Privacy & Security > Full Disk Access, and grant Warp permission so that the osascripts can run (even though you noted that it has Automation permission already, this might be worth to just debug the issue).
I suspect this may be resolved in later versions of either OSX Sequoia or Warp as we test further on that update so thanks for letting us know. I'll try and reproduce this issue and we'll post any updates on this thread.
To anyone else facing this issue, please add a 👍 to the original post at the top or comment with your details, and subscribe if you'd like to be notified.
thanks. I've enabled it. Just to reiterate — the bug happens only when warp shows the button "restart to update". after restart everything is fine.
I'm experiencing the same thing on my machine -- MacOS 15.4 on an M4 Mac.
My Warp had an update&relaunch pending, and when I tried to run a simple automation it failed.
Specifically, this command:
osascript -e 'tell application "System Events" to get name of every process'
Fails with this error:
40:44: execution error: Not authorized to send Apple events to System Events. (-1743)
After letting Warp update&relaunch, running the command caused macOS to pop up the permission dialog, and I was able to execute the script after that.
