Skip to content

Commit 097bead

Browse files
thymikeeclaude
andcommitted
docs(ios): state why a second launch-confirmation press cannot answer a later alert
Co-Authored-By: Claude Opus 5.5 <[email protected]>
1 parent 12aa6fe commit 097bead

1 file changed

Lines changed: 3 additions & 1 deletion

File tree

‎packages/platform-apple/src/launch-confirmation.ts‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -123,7 +123,9 @@ export async function answerLaunchConfirmation(
123123
/**
124124
* Presses `Open` and verifies a failed press. Only a press the runner's watchdog abandoned, with the
125125
* same confirmation still up, is pressed again, while the budget holds another whole press. Any
126-
* other failure, and a confirmation that is gone, ends the answer at once.
126+
* other failure, and a confirmation that is gone, ends the answer at once. The runner refuses new
127+
* work as `RUNNER_BUSY` until abandoned work drains, so a read that sees the confirmation proves the
128+
* abandoned press finished without answering it, and the next press cannot answer a later alert.
127129
*/
128130
async function acceptConfirmation(
129131
port: LaunchConfirmationPort,

0 commit comments

Comments
 (0)