Skip to content

Add Device Hub Support - #155

Open
PaitoAnderson wants to merge 3 commits into
okwasniewski:mainfrom
PaitoAnderson:main
Open

PaitoAnderson wants to merge 3 commits into
okwasniewski:mainfrom
PaitoAnderson:main

Conversation

@PaitoAnderson

@PaitoAnderson PaitoAnderson commented Sep 14, 2026 •

Copy link
Copy Markdown

Note

This PR was written with Claude.

Summary:

Fixes launching iOS simulators on Xcode 27.

Changelog:

Fixed simulator launching on Xcode 27, which replaced Simulator.app with Device Hub.

Test Plan:

Screenshot 2026-09-15 at 8 22 58 PM

Update: I see a better method using expo/expo#46809 and the devices url scheme, change pushed.

@JustJoostNL

Copy link
Copy Markdown

@okwasniewski any chance of this getting merged & released soon? I've always used MiniSim and it would be sad when it wouldn't work with the new Device Hub.

@jaimebg

jaimebg commented Sep 17, 2026

Copy link
Copy Markdown

+1 to this, iOS sims not working in last xcode version

@Alarak-Alex

Copy link
Copy Markdown

@PaitoAnderson Thanks for this — I hit the same Xcode 27 breakage and can confirm the whole approach works on real hardware (Xcode 27.0, macOS 26, iOS 27.0 runtime):

  • Contents/Developer/Applications is fully removed and no Simulator.app exists anywhere in the Xcode bundle or the simulator runtime cryptex; Device Hub ships at Contents/Applications/DeviceHub.app with bundle ID com.apple.dt.Devices and the devices URL scheme registered in its Info.plist.
  • open "devices://device/open?id=<udid>" launches Device Hub, boots a shutdown device, and focuses its window — verified end-to-end, so the deep-link targeting is solid.

I opened #156 on top of this PR with one hardening: falling back to open -a DeviceHub.app when the devices:// scheme isn't in the LaunchServices database yet (fresh installs), so users get Device Hub opened instead of an error dialog. Happy to close it if you'd rather fold the change in here.

@PaitoAnderson

Copy link
Copy Markdown
Author

Thanks @Alarak-Alex! Maybe best to just leave both PRs open and maintainer can decide how to best merge? I'm good with anything :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants