warpdotdev
Updates on Mac
Discord username (optional)
No response
Describe the solution you'd like?
In order to update Warp (which happens quite frequently, which is NOT a complaint!) in macOs, I need to drop to a terminal and run Warp as an admin using sudo. Just make it so the "update" button asks for the correct permissions, and it'd be SO MUCH better!
Is your feature request related to a problem? Please describe.
Updates.
Additional context
No response
How important is this feature to you?
1 (Not too important)
Warp Internal (ignore) - linear-label:39cc6478-1249-4ee7-950b-c428edfeecd1
None
Thanks for this feature request!
To anyone else interested in this feature, please add a 👍 to the original post at the top to signal that you want this feature, and subscribe if you'd like to be notified.
I have a similar problem.
I clicked update button many times but it couldn't be completed unless I manually forced Kill.
I have experienced the same problem reported by @yanquer. This is particularly annoying as, when you force kill Warp, there is a possibility you lose all your opened tabs and I'm (apparently) not able to recover them 😢
Hi Folks, Sorry about this issue. Thanks for letting us know. Please note that the logged in user requires admin permissions in order to fully update Warp without the force kill. https://docs.warp.dev/help/updating-warp#auto-update-issues
ThAts why I brought it up... I consider closing it, opening terminal, and sudoing the app a temporary workaround... But Windows and macOS can (as far as I'm aware) elevate (request) permissions (take a look at Microsoft Office Update as an example)
Sent from my T-Mobile 5G Device Get Outlook for Androidhttps://aka.ms/AAb9ysg
From: Danny Neira @.> Sent: Wednesday, May 29, 2024 5:15:22 PM To: warpdotdev/Warp @.> Cc: Todd Charlton @.>; Author @.> Subject: Re: [warpdotdev/Warp] Updates on Mac (Issue #4825)
Hi Folks, Sorry about this issue. Thanks for letting us know. Please note that the logged in user requires sudo/admin permissions in order to fully update Warp without the force kill. https://docs.warp.dev/help/updating-warp#auto-update-issues
— Reply to this email directly, view it on GitHubhttps://github.com/warpdotdev/Warp/issues/4825#issuecomment-2138276305, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AYZT7W64H5GXZJRVLSBICJLZEZAOVAVCNFSM6AAAAABGZKRMXOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZYGI3TMMZQGU. You are receiving this because you authored the thread.Message ID: @.***>
I am logged in as the admin user and I am not experiencing what is shown in https://docs.warp.dev/help/updating-warp#auto-update-issues.
In my case, I did not do anything special in this regard. I first installed Warp last year (when it was available only for MacOS with Apple Silicon) and every time I would have clicked on the "update" button, it would have done the following things (automatically):
- close warp
- update warp
- open a new instance of warp with current tabs
Lately, I don't remember exactly when (it may be few months) this doesn't happen anymore (again without me doing anything different than what I used to do). Now when I click on the button, it doesn't flash any errors, but it won't close warp, which looks really like as if it was updated correctly. But, if I do not force kill it, any command that I launch from that moment would potentially freeze Warp (even simple commands) and/or it would show graphic glitches. So I need to force quit it, potentially losing any running command if I try to update it while something is running (if I am clumsy enough obviously).
The very annoying thing it is not the force kill per se, but the fact, that time to time, the tabs/sections you have set up in Warp are not recovered when you re-open it, forcing you to recreate them one by one, which is very unfortunate. I have not found a steady way to avoid this, but it eventually happens time to time (which is a thing that is making me reconsider using Warp as it is always a pain reopening all the tabs).
Marco: As the post states, you’re not seeing the issue because you are logged in with an admin account. Best practices in security is to not allow local admin privileges. It’s like going to buy a pack of gum and bringing your life savings with you.
In a case where someone occasionally needs admin privileges, you can create an administrator account on the machine and give that user the password for it. They use their own account, and if something requires admin privs, they are typically presented with a prompt to enter admin privileges. THAT is what doesn’t happen with Warp’s updates currently.
It sounds like your issue is entirely different and most likely unrelated.
From: Marco Cavalli @.> Date: Monday, June 3, 2024 at 4:21 AM To: warpdotdev/Warp @.> Cc: Todd Charlton @.>, Author @.> Subject: Re: [warpdotdev/Warp] Updates on Mac (Issue #4825)
I am logged in as the admin user and I am not experiencing what is shown in https://docs.warp.dev/help/updating-warp#auto-update-issues.
In my case, I did not do anything special in this regard. I first installed Warp last year (when it was available only for MacOS with Apple Silicon) and every time I would have clicked on the "update" button, it would have done the following things (automatically):
- close warp
- update warp
- open a new instance of warp with current tabs
Lately, I don't remember exactly when (it may be few months) this doesn't happen anymore (again without me doing anything different than what I used to do). Now when I click on the button, it doesn't flash any errors, but it won't close warp, which looks really like as if it was updated correctly. But, if I do not force kill it, any command that I launch from that moment would potentially freeze Warp (even simple commands) and/or it would show graphic glitches. So I need to force quit it, potentially losing any running command if I try to update it while something is running (if I am clumsy enough obviously).
The very annoying thing it is not the force kill per se, but the fact, that time to time, the tabs/sections you have set up in Warp are not recovered when you re-open it, forcing you to recreate them one by one, which is very unfortunate. I have not found a steady way to avoid this, but it eventually happens time to time (which is a thing that is making me reconsider using Warp as it is always a pain reopening all the tabs).
— Reply to this email directly, view it on GitHubhttps://github.com/warpdotdev/Warp/issues/4825#issuecomment-2144579198, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AYZT7W6QDKDJKC5FDQ5TRSLZFQRSDAVCNFSM6AAAAABGZKRMXOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBUGU3TSMJZHA. You are receiving this because you authored the thread.Message ID: @.***>
+1
I am having the same issue as the topic starter, and would love to see an update implementation that is more in line with other Mac applications. I believe many similar apps are using the Sparkle Update framework.
Just adding my voice to this frustrating bug.
[!NOTE] I'm sad to see it doesn't have more 👍 on it. I bet if you put a link to this issue in the red popup that shows up on Mac asking you to auto-update, you'd get a ton more interaction on it.
Warp is amazing, but the friction every week from having to stop what I'm doing, quit the app entirely (or else the update will fail), download Warp from the internet, open the dmg, drag the icon into the Applications folder, tell Mac OS "yes I want to replace it", reopen Warp, and tell MacOS "yes I'm sure I want to open this "mysterious" app that I downloaded from the internet"... it is Chinese water torture.
My Mac setup is I have an admin account that I created when I first started up this machine and then I immediately created a user account which is what I actually use for my day to day work. Normally, when any app needs admin privileges, I just enter in the admin account and password. Works like a charm.
Warp is the only software I'm using that fails to work well with to this good-security-practice approach. I'm not sure why, but I would imagine that since your primary user audience is sophisticated, terminal-using devs, that a higher percent of them than most people would be set up with this same admin / user split approach.
Examples of dev software that works absolutely fine when updates are required:
- Slack
- Discord
- Telegram
- Signal
- IntelliJ IDEA
- All the browsers
- iTerm
As an aside, I find the instructions at https://docs.warp.dev/help/updating-warp#auto-update-issues a bit unclear.
If you have admin access on the computer, opening the app with the admin user should fix the auto-update issues.
What does that mean? I should log out of my user account, log into the admin account, and open it? Is there some way to run the app from the UI or the terminal in a special way?
A google search shows that this advice is not as straightforward as it may seem: https://www.google.com/search?q=mac+open+app+as+admin
I'm also experiencing issues with the update process. On my work computer a have a standard user account. The company uses BeyondTrust to elevate privileges when necessary. The update process works for many different apps and I get a prompt from BeyondTrust to elevate to admin privileges during the update process. This, however, does not work with Warp. I opened a IS ticket and they pointed me to this issue. So I am here to add my voice to this request. :)
@dannyneira Is this on the roadmap at all? Would love for updates to be fixed.
Hey folks, sorry about this but it's not on the roadmap right now.
We're tracking this issue over at https://github.com/warpdotdev/Warp/issues/3947 and would appreciate it if you could 👍 and comment there if you're also experiencing the same bug. This helps us gauge the impact of the issue.
We'll be closing this as a duplicate.