-
Notifications
You must be signed in to change notification settings - Fork 376
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
Warp became broken after update. #5492
Comments
Hi @RockBacon9922 sorry to hear about this. I'll let the team know asap. Please see troubleshooting steps from our team below. |
Hi @RockBacon9922 - before taking any steps to fix the issue (e.g.: uninstalling and reinstalling Warp), can you run the following commands from another terminal and share the output here?
|
@vorporeal I have the same issue as @RockBacon9922 , here is the output from the three commands: |
Fascinating. What's the output of |
@vorporeal here is the output: |
I have the same issue and same outputs as above |
@svenjr @diegocuehdz that's interesting - would you mind running |
there are no files in the
|
PS: I made this update through the update notification in the Warp app menu. |
Thanks @muescha, that's helpful! Was your computer low on disk space recently? It looks like copying the new, downloaded version of Warp failed, so we're trying to understand why (in addition to ensuring that we don't switch to a broken version). |
No low disk space: |
Dupe Check
Describe the bug
Warp destroyed itself after its self update. When trying to launch the app Mac said the app was broken
To reproduce
No clue. All I did was press the close and update button and it caused the app to become broken.
Expected behavior
No response
Screenshots
No response
Operating system
MacOS
Operating system and version
14.6.1
Shell Version
No response
Current Warp version
No response
Regression
Yes, this bug started recently or with an X Warp version
Recent working Warp date
20/11/24
Additional context
No response
Does this block you from using Warp daily?
No
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
The text was updated successfully, but these errors were encountered: