You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 3a88e1f
Browse filesBrowse the repository at this point in the historyBrowse files
test(apple): keep one source of truth for the confirmation shape
The review found three P3s on the same split:
- The openurl-timeout test compared `hint` against itself, so nothing pinned the
operator-facing text. Export `IOS_SIMULATOR_OPENURL_TIMEOUT_HINT` and assert it.
- `CONFIRMATION` and `alertNotFound()` existed twice, one copy per test file, so
prompt-text changes could diverge. Both now come from
`launch-confirmation.fixtures.ts`, which `lifecycle.fixtures.ts` no longer
duplicates.
- The docs claimed every later command would have failed; `open` and `activate`
can relaunch a stopped app, so the claim is limited to commands that require a
running app.
* A killed child answers nothing, so the bound cannot report whether the hand-off landed; the hint is
48
+
* the operator's only notice that a retry can duplicate the deep link.
49
+
*/
50
+
exportconstIOS_SIMULATOR_OPENURL_TIMEOUT_HINT=
51
+
'The Simulator may still have received the URL; CoreSimulator is slow to answer. Retry the open, or answer any "Open in" prompt with alert accept.';
52
+
46
53
// fallow-ignore-next-line complexity
47
54
exportasyncfunctionopenIosApp(
48
55
device: DeviceInfo,
@@ -178,7 +185,7 @@ async function openIosSimulatorUrl(
178
185
reason: IOS_SIMULATOR_OPENURL_TIMEOUT_REASON,
179
186
timeoutMs: IOS_SIMULATOR_OPENURL_TIMEOUT_MS,
180
187
deviceId: device.id,
181
-
hint: 'The Simulator may still have received the URL; CoreSimulator is slow to answer. Retry the open, or answer any "Open in" prompt with alert accept.',
Copy file name to clipboardExpand all lines: website/docs/docs/commands.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -82,7 +82,7 @@ agent-device fold open
82
82
- On an iOS Simulator, iOS can ask `Open in "<App>"?` before your app receives the URL from `open <app> --launch-url <url>`. If the URL's scheme belongs to your session app, `open` taps **Open** for you and its JSON data includes `launchConfirmation: "accepted"`. If no prompt appears, the response has no `launchConfirmation` field.
83
83
-`open` recognizes the prompt by its English title. On a Simulator set to another language, it leaves the prompt on screen and returns as if no prompt appeared; answer it with `alert accept` or `alert dismiss`. Run with `--debug` to see the title `open` did not recognize.
84
84
-`open` reads the prompt whenever it cannot see your app after the launch, including on a slow host where the app's target discovery fails on its own deadline. A prompt that appears after `open` has already seen your app stays on screen; answer it with `alert accept` or `alert dismiss`.
85
-
- When `open` taps **Open** and your app still provably never starts, it hands the same URL to the Simulator once more and reads the prompt again. If the app is still not running after that, `open` fails with `details.reason: launch_confirmation_unanswered` instead of reporting success for a launch that never happened; every later command in that session would have failed with `app is not running`.
85
+
- When `open` taps **Open** and your app still provably never starts, it hands the same URL to the Simulator once more and reads the prompt again. If the app is still not running after that, `open` fails with `details.reason: launch_confirmation_unanswered` instead of reporting success for a launch that never happened; later commands that require a running app would have failed with `app is not running`.
86
86
- If the URL's scheme belongs to a different installed app, `open` does not answer the prompt. The command fails with `details.reason: launch_confirmation_foreign_app`; `details.foreignAppBundleId` names that app. The prompt stays on screen: close it with `alert dismiss`, then pass a launch URL whose scheme your app handles.
87
87
- If `open` cannot identify a single installed app that owns the scheme, it does not know which app would receive the URL, so it leaves the prompt on screen and returns as if no prompt appeared; answer it with `alert accept` or `alert dismiss`. This happens when no installed app declares the scheme, when more than one does (for example a debug and a release build), and when the app list or an app's `Info.plist` could not be read.
88
88
-`open <app> --launch-console <path>` captures launch-time stdout/stderr for direct iOS simulator app launches. It is not valid for URL opens or
0 commit comments