Limrun iOS appstate succeeds with a cached app after instance termination
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- ios, typescript
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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
- Create a labeled Limrun iOS instance through
@limrun/api. - Attach a fresh daemon with
LIM_IOS_INSTANCE_URLandLIM_IOS_INSTANCE_TOKEN. Do not give the daemon an organization API key. - Run
connect limrun --platform ios --session reproandopen com.apple.Preferences --platform ios --session repro. - Delete the instance through the Limrun control plane.
- Run
appstate --json --platform ios --session repro, thensnapshot -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.
- 主要语言
- TypeScript
- 星标
- 5.1k
- 派生
- 339
- 平均合并
- 12 小时 57 分钟
- 30 天内合并 PR
- 653
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
callstack/agent-device 的其他 Issue
-
Limrun iOS fill reports success but drops non-ASCII text可能已有人在做 @mvanhorn 于 4 天前认领。 未关闭bug ready-for-agent
难度 2/5 1-3 小时 新手友好度 87/100
callstack/agent-device#3819 · 2 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
callstack/agent-device#1869 ·
维护者通常 1 天内回复
-
bug
难度 4/5 3-5 天 新手友好度 48/100
callstack/agent-device#3931 ·
维护者通常 1 天内回复
-
bug needs-info
难度 4/5 3-5 天 新手友好度 55/100
callstack/agent-device#3929 · 1 条评论 ·
维护者通常 1 天内回复
-
enhancement
难度 4/5 3-5 天 新手友好度 45/100
callstack/agent-device#3922 · 1 条评论 ·
维护者通常 1 天内回复
查看 callstack/agent-device 的全部 Issue
相似的 Issue
-
[Bug]: Device screenshot fails with 500 on iPhone Duo (Xcode 27.2): serve-sim calls simctl without --display可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 66/100
pingdotgg/t3code#24900 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
inu-appcenter/UNIDorm-web#411 ·
维护者通常 1 天内回复
-
🐛 bug
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
ranxianglei/billion-context#4720 ·
维护者通常 1 天内回复
-
area:arcade game p3-medium ready-for-agent type:bug
难度 2/5 1-3 小时 新手友好度 82/100
fderuiter/deruiter.dev#2840 ·
维护者通常 1 天内回复