Installed apps greyed out in Default Apps Terminal drop down

Support
1

What issue or error are you experiencing?

I recently changed from WARP to Terminal because was having issue with Site Shell… warp won’t run the defualt .sh script.. but a different issue..

changed my default app to default mac terminal, but now I can’t go back to Warp as it is greyed out. The app is installed in my ~/Applications folder. I’ve tried quit local and restarted it, but still always greyed out now.

not sure if this is a Local issue or Warp issue or OS??

What steps can be taken to replicate the issue? Feel free to include screenshots, videos, etc

System Details

  • **Local Version:**Version 10.0.0+6907

  • Operating System (OS) and OS version: Mac Tahoe 26.4.1 (25E253)

Local Logs

Attach your Local Logs here (Help Doc - Retrieving Local’s Log)

local-lightning.log (338.3 KB)

Security Reminder
Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed.

2

Thanks for your report, @balbert. I can’t reproduce this so far — I can switch to Terminal, restart Local, and then switch to Warp as long as Warp is installed at /Applications/Warp.app.

Local checks for Warp by looking for an application named “Warp.app” (macOS Finder just shows this as “Warp”, though) at either /Applications (shared applications folder) or ~/Applications (user applications folder).

Might your Warp app be named differently or be in a different place? For example, if you were running it from the disk image or Desktop/Downloads folders, Local would not find it.

3

Thanks. Yes warp is at ~/Applications/Warp.app

It was all working fine and was able to change to the default terminal but can’t go back.

The other odd thing, which might be part of the issue, is before I changed to terminal, when i clicked “site shell”, instead of opening a window in Warp and running the start sh script, it would just show me the script path… almost like it wanted me to approve running the script.

There was a split window… my shell on the left and on the right was another window with just the /Users/bob.albert/Library/Application\ Support/Local/ssh-entry/Lvotf17_b.sh in it… i wasn’t sure how to accept and run or what. maybe there is a setting in Warp i need to fix?

This is why i changed the default app.

Not sure if this is a new Warp setting or if warp in general is the issue.

Bob

4

As a test, i installed iTerm2 and all the other apps are still greyed out. It doesn’t seem to see the iTerm either now.

it too is in the applications folder in my user folder…
/Users/bob.albert/Applications/iTerm.app

As a test, i copied another version of iTerm to my /Applications folder and now it sees it. Did the same with Warp and it works now.

This is a company managed Mac, so maybe Local can’t read my user ~/Applications folder. I guess this might be the issue.

Also looks like the split screen auto shell script issue is a known issue with the latest version of Warp… ugg.. so i guess it is all me and not Local :wink: lol

Thanks,

Bob

5

Thanks for the update, @balbert.

This is a company managed Mac, so maybe Local can’t read my user ~/Applications folder. I guess this might be the issue.

Ah, yes — that could be it. If Local can’t read ~/Applications it won’t be able to find apps there. Also, Local runs the find command behind the scenes, so if your company security policy blocks apps from running shell commands it could stop Local from finding apps.

Interesting to hear the Warp split pane problem is a known issue, thanks for sharing.