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
I’m encountering permission errors when trying to create or save files on macOS (version 15.2). Here’s what happens:
Initially, I see this error:
1.“Failed to save ‘file.tsx’: Insufficient permissions. Select ‘Retry as Sudo’ to retry as superuser.”*
When I click “Retry as Sudo,” I get a different error:
2.“Failed to save ‘file.tsx’: ENOENT: no such file or directory, open ‘/Applications/Cursor.app/Contents/Resources/Cursor.icns’”*
I noticed that in the /Resources path, there’s a file named icon.icns, not Cursor.icns. I tried renaming it to Cursor.icns, but the issue persists.
The Cursor app has full disk access, and all the directories involved have read-write privileges, so I’m unsure what’s causing this.
From what I understand, Cursor is a fork or wrapper around VS Code, so it seems like the permissions are being handled weird. Has anyone experienced this or found a fix?
The text was updated successfully, but these errors were encountered:
I’m encountering permission errors when trying to create or save files on macOS (version 15.2). Here’s what happens:
Initially, I see this error:
1.“Failed to save ‘file.tsx’: Insufficient permissions. Select ‘Retry as Sudo’ to retry as superuser.”*
When I click “Retry as Sudo,” I get a different error:
2.“Failed to save ‘file.tsx’: ENOENT: no such file or directory, open ‘/Applications/Cursor.app/Contents/Resources/Cursor.icns’”*
I noticed that in the /Resources path, there’s a file named icon.icns, not Cursor.icns. I tried renaming it to Cursor.icns, but the issue persists.
The Cursor app has full disk access, and all the directories involved have read-write privileges, so I’m unsure what’s causing this.
From what I understand, Cursor is a fork or wrapper around VS Code, so it seems like the permissions are being handled weird. Has anyone experienced this or found a fix?
The text was updated successfully, but these errors were encountered: