Bug Report: Transmit Extension "Show Servers" slow initialization on macOS Tahoe 26.2
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7.8k
- Forks
- 6.9k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 442
Description
Extension
https://www.raycast.com/kennonb/transmit
Raycast Version
1.104.1
OS Version
OS X 26.2 Tahoe
Description
Since updating to macOS Tahoe 26.2, the "Show Servers" command in the Transmit extension takes exactly 10 seconds to display any results. Once loaded, searching is fast, but closing and reopening the panel reintroduces the 10-second delay.
Transmit Version 5.11.3
Technical Findings (Logs): The macOS Console logs show a specific timeout during the _LSCopyMatchingApplications call when Raycast tries to locate the Transmit application bundle.
Log Snippet:
Raycast: (LaunchServices) [com.apple.launchservices:cas] _LSCopyMatchingApplications(sessionID=-2 matchInfo={ "CFBundleIdentifier"="com.panic.Transmit" }) Timeout: 9.0 Entry Point ID: transmit.index__1f1c304f-ce6d-4e61-80fc-dba736264844
Observations:
The system hits a 9.0s timeout every time the command is initiated.
The delay persists even after resetting LaunchServices (lsregister), TCC permissions (tccutil), and clearing Raycast caches.
It appears to be a Sandbox/Permission issue where Tahoe blocks the automated discovery or the AppleScript bridge to Transmit.
"Show Servers" was running blazing fast on Sequoia (and was a hudge timesaver).
Steps To Reproduce
- On Mac OS Tahoe start RayCast and type "Transmit" -> select "Show Servers" + return. Type in some characters. Recognize the delay until you can actually search the list.
- Press ESC and reopen the "Search Servers" Panel repeat the search – again we see the 10s delay.
Current Behaviour
Initializing the search panel content takes around 10s (for aprox. 70 server names). After loading the list, the filter/search is fast.
Expected Behaviour
Opening the "Search Server" panel and initializing the search should be fast as before (Sequoia) = around 1s.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Transmit extension's “Show Servers” command and reproduce the delay on macOS Tahoe 26.2, using the reported _LSCopyMatchingApplications timeout and entry point ID as the first investigation clues. Done means the command initializes in roughly 1 second, as it did on Sequoia, while preserving fast server-list searching.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- desktop, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100