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

iOS Simulator open: simctl openurl has no timeout and can hold the open until the daemon request times out

Cerrado
  • ¿Algo no está bien?
#3,101 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
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
78/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
ios, typescript
Área
mobile, testing

Línea de trabajo

Start in packages/platform-apple/src/core/app-launch.ts at openIosSimulatorUrl and compare its simctl bounds with the other launch calls. Add the unit test described for a provider whose openurl never returns, then verify the open fails within the bound with the typed reason and that cancellation kills the child. Update the open help where the other launch bounds are documented.

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

Descripción

What happens

openIosSimulatorUrl (packages/platform-apple/src/core/app-launch.ts) runs xcrun simctl openurl <udid> <url> with no timeoutMs. When CoreSimulator is wedged (seen twice on 2026-10-01 under host load 215–691 while working #3096, and once on CI run 36843756495 step 87 where openurl answered NSPOSIXErrorDomain 60 only after its own long internal wait), the open holds until the daemon request timeout (450–630 s in those runs), and the simctl openurl child outlives the daemon's kill of the request.

Every other simctl call the open makes is bounded (listapps, plutil, the terminate calls at 2 s). openurl is the one that can take minutes.

Required behavior

  • simctl openurl runs under a bound of its own, shorter than the open's request budget, and takes the request signal so a cancel kills the child.
  • A timed-out openurl fails the open with a typed reason (dispatched: unknown: the URL may have been delivered) rather than letting the daemon request time out around it.

Completion conditions

  • A unit test with a provider whose openurl never returns: the open fails within the bound with the typed reason, and the child receives the kill.
  • The bound and its reason are documented in the open help where the other launch bounds are.
Lenguaje dominante
TypeScript
Estrellas
5k
Forks
334
Merge medio
11 h 48 min
PR fusionados (30 d)
605

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.