Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#3,076 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
68/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
ios, typescript
Área
cli, documentation, mobile, testing

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
4.8k
Forks
315
Merge medio
11 h 27 min
PR fusionados (30 d)
556

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de callstack/agent-device

Todos los issues de callstack/agent-device

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.