Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Limrun iOS appstate succeeds with a cached app after instance termination

Offen
  • Stimmt etwas nicht?
#3,924 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
35/100
Issue-Typ
Bug
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
ios, typescript
Bereich
backend-api-design, mobile

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
TypeScript
Sterne
5.1k
Forks
339
Ø Merge
12 Std. 57 Min.
Gemergte PRs (30 T.)
653

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus callstack/agent-device

Alle Issues in callstack/agent-device

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.