fix: handle devicectl launch arguments#93
Merged
V3RON merged 3 commits intocallstackincubator:mainfrom Apr 2, 2026
Merged
Conversation
|
@hannojg is attempting to deploy a commit to the Callstack Team on Vercel. A member of the Team first needs to authorize it. |
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
2 participants
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.
Harness uses
devicectl device process launchfor physical iOS devices.When app launch arguments are present,
devicectlexpects them after a--separator.Without that separator, launch arguments are parsed incorrectly and physical-device startup can fail.
Harness also appends
--json-outputto everydevicectlcommand.That flag must stay before the
--separator sodevicectlstill treats it as its own option and writes the result JSON file correctly.