-
Notifications
You must be signed in to change notification settings - Fork 374
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unexpected loss of permission #3009
Comments
Thanks for letting us know @markmbaum Please see our guides on the permissions and updating warp issues that could be affecting your permissions. Let us know if those helped, if not, we will need a bit more information from you to reproduce this issue, most likely some Logs. |
Ok thanks for the pointer. I haven't noticed any issues updating Warp, so I'll look into the other troubleshooting. |
Same issue here. SOLUTION: After a MacOS update, my standard terminal also didn't have access anymore for Full Disk Access in Privacy & Security. So make sure to check this. |
I've also been getting this behavior. Over the past 2 - 3 weeks. |
Hey Folks, We're noticing reports of this issue returning recently. We suspect it may be related to auto-updates to Warp. We're going to reopen, investigate further, and post any updates on this thread. As a possible workaround/stopgap measure, please apply and pending Updates to Warp. This should grant Warp the permissions again and resume normal functions. 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. |
Just happened to me. Shortly after "Update Warp" showed up in the toolbar. |
Confirming I have been experiencing this and granting permissions to 'old' seems to have been the fix for me. |
how if in my devices there's no "old"? |
Adding to this thread as #5417 was closed. I didn't think it was a duplicate as this issue was closed as completed in March 2023. There is no "old" in my settings. |
@mark-jordanovic-lewis when you see the issue, is there usually a pending update in Warp? If you do, the best workaround would be to apply the Update, and the new Warp binary should have the right permissions. We've noticed this only on MacOS and when there is a pending update, so just want to confirm. |
I can't really comment on that, there was an update today and it happened. I encountered it quite a few times before I posted previous issue but I'm not sure it corresponded with an update or not. |
@robbiehobby Yup, this appears to happen after a pending Update in Warp and only on directories that require permissions (i.e. Documents, Downloads, Desktop, etc), even if you've granted Warp "Full Disk Access". If you manage to run commands on those directories while Warp is still Updating in the background, then the issue may not happen. |
@mark-jordanovic-lewis Keep an eye out for this, We suspect it is related to updates with high certainty, but your issue may indeed be different. There will be a fix coming soon (which may cause the issue again ), but updating to the new version will hopefully ensure it doesn't return for future releases. If that's not the case, please reopen #5417 and let us know. |
Same issue for me while saving local files on mac after updating to OS 15. |
In case it helps finding the root cause: I only started to face this issue after upgrading my MacOS version to Sequoia |
Same issue for me. Only happens after updating to macOS Sequoia. |
@dannyneira As requested (but cannot re-open issue #5434). On Thursday and Friday there was no loss of permissions in warp. Yesterday morning, Monday 11th Nov 2024, permissions to read directories in already open warp sessions have been lost. No changes in OS settings related to Full Disk access of the application.
Removed warp, rebooted machine, reinstalled warp, warp will still not open. Checked permissions, Warp.App is read/write for me. Delving into the Warp.app package and running the stable binary gives me:
I removed the yaml that was not formatted as a theme file and the git files from the themes directory and those errors went away.
I completely purged my system of warp assets inc. DBs, config and themes and re-installed it. Warp works now. |
@mark-jordanovic-lewis Thanks for sharing the details. As far as I'm aware, the fix for this issue went out last weeks release. We're fairly confident it won't return in future releases, but please keep an eye out for this issue and let us know. |
@dannyneira good to know. I can't pin down what it was that was causing the problem, and I was annoyed at having to set up my config again - however the UI is intuitive and it was easy to get back up and running once I could sort of work out what was going on. Thanks for staying on this and replying. I will post if this happens again and the solution above does not fix things. |
Discord username (optional)
No response
Describe the bug
I was in the process of fairly routine git activity and the Warp shell suddenly lost permission to access files and directories. A screenshot of the error message and failure to even run
ls
is below.If I quit and restart, it works fine.
Sometimes sudden permission loss happens in the middle of running a program (in this case Python scripts driving an executable), which makes it crash.
To Reproduce
The last thing I did before the screenshot above was
git push --force
but sometimes the sudden permission loss happens in the middle of runnig a Python script.Expected behavior
The shell should keep running with normal permissions.
Screenshots
No response
Operating System
MacOS
Operating System and Version
macOS 13.3.1
Shell Version
zsh 5.9 (x86_64-apple-darwin22.0)
Warp Version
v0.2023.04.25.08.05.stable_00
Additional context
No response
Does this block you from using Warp daily?
No
Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)
Yes, this I confirmed this only happens in Warp, not other terminals.
Warp Internal (ignore): linear-label:b8107fdf-ba31-488d-b103-d271c89cac3e
None
The text was updated successfully, but these errors were encountered: