Open romica228 opened 3 months ago
Hi @romica228 sorry to hear about this. Make sure your Mac hardware that supports Metal. That's the API we use to render Warp on Mac.
If it does support Metal, make sure that Warp is in the application folder. If the issue persist, please provide the logs so that we can investigate the issue further. https://docs.warp.dev/help/sending-us-feedback#gathering-warp-logs
Hello, @dannyneira
Thank you for your response, my Mac supports Metal but I can't provide you with the logs because there are no files created related to warp in the logs folder. After today's update the app wont prompt even the message reported earlier.
Heard, Sorry about this. I'll let the team know and see if there is a possible workaround.
Hey @romica228 - can you try deleting Warp.app and reinstalling it (in case something got screwy when you updated your OS)?
Hello @vorporeal,
Done that and still no response from the app at all. Tried both .dmg and brew.
Ive been having a really similar issue for the last couple of weeks. Trying to start Warp and the icon flashes and goes away. I also have no warp files in the logs. I have tried uninstalling and removing anything warp related then reinstalling via the DMG or brew. Really hard to troubleshoot with no logs. Works fine on my other identical mac. (M1 Pro)
Hey, sorry you're all experiencing this. I've done some research and can't find any good information as to why this occurs or what to do about it.
@mysticfalconvt The reason there are no Warp logs is that macOS is preventing you from even running Warp - the application never even starts.
Can you check in Console.app to see if launchd.log
has any relevant information?
Can you check in Console.app to see if
launchd.log
has any relevant information?results related to Warp in `launchd.log`
2024-04-29 11:01:36.339908 (gui/501/application.dev.warp.Warp-Stable.118903577.118903687) <Notice>: internal event: WILL_SPAWN, code = 0
2024-04-29 11:01:36.339910 (gui/501/application.dev.warp.Warp-Stable.118903577.118903687) <Notice>: service state: spawn scheduled
2024-04-29 11:01:36.339910 (gui/501/application.dev.warp.Warp-Stable.118903577.118903687) <Notice>: service state: spawning
2024-04-29 11:01:36.340209 <Notice>: Coalition Cache Hit: app<application.dev.warp.Warp-Stable.118903577.118903687(501)> [255819]
2024-04-29 11:01:36.340223 (gui/501/application.dev.warp.Warp-Stable.118903577.118903687) <Notice>: launching: launch job demand
2024-04-29 11:01:36.344477 (gui/501/application.dev.warp.Warp-Stable.118903577.118903687 [61506]) <Notice>: xpcproxy spawned with pid 61506
2024-04-29 11:01:36.344522 (gui/501/application.dev.warp.Warp-Stable.118903577.118903687 [61506]) <Notice>: internal event: SPAWNED, code = 0
2024-04-29 11:01:36.344525 (gui/501/application.dev.warp.Warp-Stable.118903577.118903687 [61506]) <Notice>: service state: xpcproxy
2024-04-29 11:01:36.344595 (gui/501/application.dev.warp.Warp-Stable.118903577.118903687 [61506]) <Notice>: internal event: SOURCE_ATTACH, code = 0
2024-04-29 11:01:36.362196 (gui/501/application.dev.warp.Warp-Stable.118903577.118903687 [61506]) <Notice>: service state: running
2024-04-29 11:01:36.362241 (gui/501/application.dev.warp.Warp-Stable.118903577.118903687 [61506]) <Notice>: internal event: INIT, code = 0
2024-04-29 11:01:36.362244 (gui/501/application.dev.warp.Warp-Stable.118903577.118903687 [61506]) <Notice>: job state = running
2024-04-29 11:01:36.362274 (gui/501/application.dev.warp.Warp-Stable.118903577.118903687 [61506]) <Notice>: Successfully spawned stable[61506] because launch job demand
2024-04-29 11:01:36.439889 (pid/61506 [stable]) <Notice>: uncorking exec source upfront
2024-04-29 11:01:36.439907 (pid/61506 [stable]) <Notice>: created
2024-04-29 11:01:36.457354 (pid/61506 [stable]) <Notice>: shutting down
2024-04-29 11:01:36.457392 (pid/61506 [stable]) <Notice>: cleaning up
2024-04-29 11:01:36.457497 (gui/501/application.dev.warp.Warp-Stable.118903577.118903687 [61506]) <Notice>: exited due to exit(1)
2024-04-29 11:01:36.457503 (gui/501/application.dev.warp.Warp-Stable.118903577.118903687 [61506]) <Notice>: service state: exited
2024-04-29 11:01:36.457536 (gui/501/application.dev.warp.Warp-Stable.118903577.118903687 [61506]) <Notice>: internal event: EXITED, code = 0
2024-04-29 11:01:36.457541 (gui/501/application.dev.warp.Warp-Stable.118903577.118903687 [61506]) <Notice>: job state = exited
2024-04-29 11:01:36.457795 (gui/501 [100011]) <Notice>: service inactive: application.dev.warp.Warp-Stable.118903577.118903687
2024-04-29 11:01:36.457800 (gui/501/application.dev.warp.Warp-Stable.118903577.118903687 [61506]) <Notice>: service state: not running
2024-04-29 11:01:36.457807 (system) <Notice>: removing child: pid/61506
2024-04-29 11:01:36.459177 (gui/501/application.dev.warp.Warp-Stable.118903577.118903687) <Notice>: removing job: caller = runningboardd
2024-04-29 11:01:36.459180 (gui/501 [100011]) <Notice>: removing service: application.dev.warp.Warp-Stable.118903577.118903687
2024-04-29 11:01:36.459212 (gui/501/application.dev.warp.Warp-Stable.118903577.118903687) <Notice>: internal event: PETRIFIED, code = 0
2024-04-29 11:01:36.459215 (gui/501/application.dev.warp.Warp-Stable.118903577.118903687) <Notice>: job state = removed
Hm. If you run the app from Terminal.app or iTerm using /Applications/Warp.app/Contents/MacOS/stable
(assuming you've installed Warp by copying it into the Applications folder), do you get any log output there?
That actually works. Opens right up. Still doesn't open when trying outside of that command in the terminal.
Ok, I wonder if perhaps the app is quarantined or something like that.
What's the output of ls -l@ /Applications/Warp*
?
% ls -l@ /Applications/Warp*
total 0
drwxr-xr-x 7 robertboskind admin 224 Apr 25 10:40 Contents
No dice. Maybe the output of open /Applications/Warp.app
might have something useful? (context on that guess is this Apple forum thread: https://developer.apple.com/forums/thread/740689)
Nada, nothing shows up there. Although if I have it started already with /Applications/Warp.app/Contents/MacOS/stable then it does focus it.
Thanks for trying. Crazy wild goose chase. I may just decide to wipe the laptop and try again.
Discord username (optional)
No response
Describe the bug
Warp app wont open after being installed on the mac for the first time. Tryied reinstalling it and no luck, still same error.
To reproduce
Just install the app via dmg or brew and try to open it. The Apple prompt telling that this is an app from the Internet and so on appears and then nothing happens.
Expected behavior
The app to launch.
Screenshots
Operating system
MacOS
Operating system and version
macOS Big Sur 11.7.10
Shell Version
zsh 5.8
Current Warp version
Not open it to give the version, but its the most recent one.
Regression
Yes, this bug started recently or with an X Warp version
Recent working Warp date
27 March
Additional context
I updated the macOS version from 11.5 to 11.7.10 and maybe it has something to do with it. Was working well on 11.5
Does this block you from using Warp daily?
Yes, this issue prevents me from using Warp daily.
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:b9d78064-c89e-4973-b153-5178a31ee54e
None