`open --launch-url` should answer the iOS "Open in <app>?" confirmation
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 68/100
- Issue 类型
- 功能
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- ios, typescript
- 领域
- cli, documentation, mobile, testing
调研方向
Start with the Apple runner and the open command family, then inspect the smoke lane's answerDeepLinkConfirmation helper and the live fixture E2E. Use the fixture replay for agent-device-test-app:///automation to verify the confirmation behavior, and update commands.md for both outcomes. Done means the helper is deleted, the fixture runs unattended, and foreign-app confirmations remain errors.
由索引模型根据 Issue 内容生成。
描述
Part of #3069.
Purpose
On an iOS Simulator, open <bundle> --launch-url <scheme-url> can raise the system confirmation Open in "<App>"?. The command returns success while the app is still waiting behind that sheet, and the next command fails with APP_NOT_RUNNING or wait_capture_stalled. The iOS smoke lane answers the sheet from its own harness (#3044, #3063), and a local fixture replay hits the same sheet on every test run. Production users get no help.
Required behavior
- When
open --launch-urltargets the session app and iOS raises the confirmation naming that app,openaccepts it as part of the launch and reports it:data.launchConfirmation: "accepted". - A confirmation naming a different app is never accepted.
openfails withreason: launch_confirmation_foreign_appand the app name indetails. - No confirmation, no change: the response is as today.
- The wait for the sheet is bounded by the existing launch budget; a sheet that never appears costs no extra time beyond one capture.
Completion conditions
- The smoke lane's
answerDeepLinkConfirmationhelper is deleted, and the live fixture E2E passes without it. - A fixture replay that opens
agent-device-test-app:///automationruns unattended. commands.mddocuments the two outcomes.
Dependencies
None. Apple runner and the open command family only.
- 主要语言
- TypeScript
- 星标
- 4.9k
- 派生
- 328
- 平均合并
- 12 小时 18 分钟
- 30 天内合并 PR
- 561
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
callstack/agent-device 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 74/100
callstack/agent-device#3407 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 88/100
callstack/agent-device#3353 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
callstack/agent-device#1869 ·
维护者通常 1 天内回复
-
needs-triage
难度 3/5 1-2 天 新手友好度 76/100
callstack/agent-device#3453 ·
维护者通常 1 天内回复
-
CRAP: newly scored platform-apple simulator boot retry and macOS helper file listing可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 4/5 3-5 天 新手友好度 52/100
callstack/agent-device#3451 ·
维护者通常 1 天内回复
查看 callstack/agent-device 的全部 Issue