Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

`open --launch-url` should answer the iOS "Open in <app>?" confirmation

Aperta
#3,076 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
68/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
ios, typescript

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

needs-triage

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-url targets the session app and iOS raises the confirmation naming that app, open accepts it as part of the launch and reports it: data.launchConfirmation: "accepted".
  • A confirmation naming a different app is never accepted. open fails with reason: launch_confirmation_foreign_app and the app name in details.
  • 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 answerDeepLinkConfirmation helper is deleted, and the live fixture E2E passes without it.
  • A fixture replay that opens agent-device-test-app:///automation runs unattended.
  • commands.md documents the two outcomes.

Dependencies

None. Apple runner and the open command family only.

Lingua principale
TypeScript
Stelle
4.8k
Fork
315
Merge medio
11h 27m
PR unite (30g)
556

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di callstack/agent-device

Tutte le issue di callstack/agent-device

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.