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

Limrun iOS appstate succeeds with a cached app after instance termination

Abierto
  • ¿Algo no está bien?
#3,924 1 comentario 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
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
ios, typescript
Área
backend-api-design, mobile

Línea de trabajo

Start with packages/provider-limrun/src/facts-runtime.ts and trace how the Apple session handler handles an unavailable iOS appState and runtime read errors. Reproduce with the listed connect, open, instance deletion, appstate --json, and snapshot commands. Done means instance loss cannot return a successful cached app identity; the issue notes that obtaining an authoritative foreground bundle ID remains unresolved.

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

Descripción

bug

Problem

On agent-device 0.21.31, appstate --json on a Limrun iOS session returns the last app recorded by open, even after the instance is terminated. A successful result can therefore describe an app on a device that no longer exists.

Reproduction

  1. Create a labeled Limrun iOS instance through @limrun/api.
  2. Attach a fresh daemon with LIM_IOS_INSTANCE_URL and LIM_IOS_INSTANCE_TOKEN. Do not give the daemon an organization API key.
  3. Run connect limrun --platform ios --session repro and open com.apple.Preferences --platform ios --session repro.
  4. Delete the instance through the Limrun control plane.
  5. Run appstate --json --platform ios --session repro, then snapshot -i --platform ios --session repro.

Measured result: appstate exits 0 and returns appBundleId: "com.apple.Preferences" with source: "session". snapshot exits 1. The label still has exactly one instance and it is terminated.

Expected result

appstate should report a live foreground identity or fail without an app identity when it cannot read the device. In particular, an instance loss must not turn into a successful cached answer.

Source trace

The Limrun owner marks iOS appState unavailable in packages/provider-limrun/src/facts-runtime.ts. The Apple session handler drops that refusal and falls back to session.appBundleId. It also drops non-cancellation errors from the runtime read.

A complete fix also needs an authoritative foreground bundle ID. The iOS client in @limrun/api exposes an accessibility tree with an application PID and label, but no bundle ID. A live attempt to run simctl spawn booted launchctl list was refused because the provider restricts spawn to defaults, notifyutil, and limproxy. Matching app display names would be ambiguous and would not establish app identity.

Our consumer uses the returned bundle ID to scope saved credentials. We are preparing a fork update and would like to carry the smallest fix that can later be removed.

Lenguaje dominante
TypeScript
Estrellas
5.1k
Forks
339
Merge medio
12 h 57 min
PR fusionados (30 d)
653

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.