iOS: make the device set configurable so Xcode tools can target a leased simulator
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- ios, typescript
调研方向
Start with ADR 0001 and the iOS device set configuration and lifecycle code; the issue does not name specific files for the change. First map how the worker selects and manages its CoreSimulator device set, then define the default, runtime-change behavior, and simlock simctl behavior alongside the recovery risks. Done means the spec resolves those open questions and documents the effects of targeting the default set.
由索引模型根据 Issue 内容生成。
描述
Problem
Simlock's iOS simulators live in their own CoreSimulator device set (ADR 0001). No Xcode tool can target a simulator there from the command line: xcodebuild -destination "platform=iOS Simulator,id=<udid>", react-native run-ios --udid, Expo, Detox, Maestro and agent-device's XCTest runner all read the default set. The only switch is the per-user DVTSimulatorSetLocation default, which leaks into every xcodebuild run of that user and hides the default-set simulators while set. Every per-process route was tested and does not work. The docs never mention the limit, and the only workaround is to build for generic/platform=iOS Simulator and install with simlock simctl install.
Android does not have this problem: adb, Gradle and the RN CLI honour ANDROID_ADB_SERVER_PORT, so the separate adb server is compatible with the tooling. The question is about iOS only.
Proposal: make the iOS device set configurable, ios.deviceSet: "simlock" | "default", and decide which is the default.
What the isolation buys and costs
Buys: an accident boundary. xcrun simctl shutdown all, erase all, delete unavailable, Xcode's "Delete All Simulators" and an RN CLI that picks booted cannot touch a leased device. src/drivers/AGENTS.md calls the root "an accident boundary, not a security boundary".
Costs: the primary use-cases cannot build onto a leased device without the generic-build detour, and UI test runners cannot target it at all.
What dropping it does not break: cleanup, nuke and the warm pool act only on devices the registry owns, so a developer's own simulators stay safe. Devices are already named simlock-<uuid>. A leased device that is shut down from outside is already rebooted under its lease; a deleted one already ends its lease as device-lost.
What dropping it costs: a developer whose Mac is a worker sees every simlock-… device in Xcode's destination picker. A stray erase all wipes an agent's in-progress state, and recovery reboots but does not reinstall. The refusal list in simlock simctl protects nothing once agents run xcrun simctl directly.
Context
Found in the 2026-10-23 product review. The maintainer rejected the per-user default on 2026-09-14 and on 2026-10-23 chose to keep the isolation and document the generic build for now, then asked for this to be made configurable.
Open questions for the spec session: the default value (the review leaned to default once recovery after an external shutdown or erase is tested and the docs state what a careless simctl … all does); whether the key can change on a running worker or needs nuke --delete-devices; what simlock simctl does under default (plain passthrough, or still refuse the lifecycle commands); the ADR that supersedes 0001 for iOS.
Written by an agent.
- 主要语言
- TypeScript
- 星标
- 22
- 派生
- 2
- 平均合并
- 9 小时 14 分钟
- 30 天内合并 PR
- 425
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
callstackincubator/simlock 的其他 Issue
-
bug:new
难度 2/5 1-3 小时 新手友好度 82/100
callstackincubator/simlock#1035 ·
维护者通常 1 天内回复
-
bug:ready
难度 2/5 1-3 小时 新手友好度 70/100
callstackincubator/simlock#639 · 3 条评论 ·
维护者通常 1 天内回复
-
feature:spec
难度 5/5 一周以上 新手友好度 12/100
callstackincubator/simlock#1024 ·
维护者通常 1 天内回复
-
iOS simulator input through the HID injector可能已有人在做 @V3RON 今天认领。 未关闭task:blocked
难度 5/5 一周以上 新手友好度 20/100
callstackincubator/simlock#1019 · 1 条评论 ·
维护者通常 1 天内回复
-
Android input through scrcpy's control channel可能已有人在做 @V3RON 今天认领。 未关闭task:blocked
难度 4/5 3-5 天 新手友好度 42/100
callstackincubator/simlock#1018 · 1 条评论 ·
维护者通常 1 天内回复
查看 callstackincubator/simlock 的全部 Issue
相似的 Issue
-
category::task code priority::normal
难度 2/5 1-3 小时 新手友好度 78/100
e0ipso/strikethroo#145 ·
维护者通常 1 天内回复
-
难度 1/5 1-3 小时 新手友好度 85/100
cocos/cocos-docs#3333 ·
-
bug
难度 2/5 1-3 小时 新手友好度 75/100
RevenueCat/react-native-purchases#2079 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 78/100
RevenueCat/purchases-hybrid-common#2039 ·
维护者通常 1 天内回复
-
agent-reported area/react bug
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复