feat: run multiple devices per workspace with named slots - #773
Merged
Merged
Conversation
janicduplessis
added this pull request to stack #768
September 12, 2026 16:37
janicduplessis
force-pushed
the
feat/device-slot-cli
branch
from
September 12, 2026 16:55
c2b4d06 to
84a9f47
Compare
This was referenced Sep 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Each platform currently has one device assignment per workspace. Testing on an iPhone, an iPad, and hardware needs independent targets that subsequent commands can reuse.
Solution
Add
--slot <name>to local iOS/Android runs, including physical devices and multiple simulators of the same model. Existing assignments remain in the default slot. Slots share Metro and build caches; native CLI runs serialize workspace mutations to protect shared build output.Logs and status identify slots.
stop --slotpreserves Metro and sibling devices; workspace cleanup handles every slot.Limits to review:
unverified.Depends on #769, above #767 and #764.
Test plan
Regression coverage includes allocation, reuse, scoped cleanup, leases, log markers, launch attribution, default-state compatibility, and EAS-downloaded builds in default and named slots.
The combined slot stack and QA fixes passed the full loop and cache suites for bare React Native and Expo on both platforms. iOS ran locally on the 16 GB Mac; all four Android jobs passed in the hosted matrix. Both iOS pool suites also passed hosted QA.
Both iOS loops exercised three distinct simulators (two iPhones and an iPad), reuse, cache hits, attributed logs, scoped stop/resume, and complete cleanup. Each iOS cache suite passed all seven applicable checks, including one build shared by two racing workspaces. The initial failures led to readiness fixes in #779, Android cleanup fixes in #780, and selecting an iPad supported by an available runtime in this PR.
Physical-device installs were not exercised on hardware. Lease and command behavior have regression coverage. The earlier full hosted run contains iOS failures; the passing sign-off combines its Android jobs with the final local iOS loops/caches and hosted pool run.
Fixes #770.