drivers.ios.deviceSet switch is blocked by iOS seeds; the only supported purge (nuke --delete-devices) also wipes Android seeds

未关闭
#1,797 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
45/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
android, ios, typescript
领域
cli, mobile-dev

调研方向

Start by reading core/nuke-service.js, the drivers.ios.deviceSet configuration path, and the existing simlock nuke and seed management commands. Trace how device and seed deletion is scoped across drivers, then compare the two requested approaches. Done means there is a supported way to retire iOS devices and seeds while preserving Android seeds, with coverage for the chosen command or migration path.

由索引模型根据 Issue 内容生成。

描述

request:new

Summary

On a worker that has already provisioned simulators, switching drivers.ios.deviceSet from simlock to default is blocked by the iOS seeds in Simlock's private sources set. The only supported way to empty that set, simlock nuke --delete-devices, also deletes every other platform's seeds and resets every device. That includes the Android emulator seeds, which are large and slow to recreate. There is no per-platform or seed-only purge, and no migration path for the device set.

Version

simlock 0.8.0 (npm), macOS worker, Xcode 27.2 runtime.

Steps

  1. Worker running with the default drivers.ios.deviceSet: "simlock". It has served iOS and Android leases, so both platforms have seeds (simlock doctor lists sources: iPhone 17, iPhone 17 Pro, Pixel 9, Pixel 9 Pro).
  2. At 0 leases: simlock config set drivers.ios.deviceSet default, simlock daemon stop, simlock daemon start.
  3. simlock lease --platform ios ...

Actual

The lease fails with NO_DRIVER:

Refusing the ios device set: Simlock's own set at ~/.simlock/devices/ios still holds 2 simulator(s) (…). Set drivers.ios.deviceSet back to simlock, run simlock nuke --delete-devices and simlock doctor --purge-orphans, then switch again. Delete any that remain with xcrun simctl --set … delete <udid>, or, for a seed in the sources set, xcrun simctl --set …/sources delete <udid>.

The two "simulators" are the iOS seeds under ~/.simlock/devices/ios/sources. simlock doctor reports no findings, and simlock cleanup --dry-run is empty.

nuke --delete-devices (core/nuke-service.js) destroys all devices and deletes all drivers' seeds, Android included. So the documented path costs the Android seeds just to change an iOS-only setting. The only iOS-scoped alternative is raw xcrun simctl --set …/sources delete, which the agent instructions otherwise forbid.

Request

One of:

  • a per-platform purge, e.g. simlock nuke --platform ios --delete-devices, or a simlock seeds remove --platform ios command; or
  • a supported migration for drivers.ios.deviceSet that retires the private set's seeds and devices itself, leaving other platforms alone.

Why it matters

The default set is needed for tools that only see Xcode's set (Maestro, Detox, xcodebuild -destination id=, as simlock instructions notes). Teams adopting them shouldn't have to wipe Android emulator seeds to do so.

主要语言
TypeScript
星标
705
派生
40
平均合并
12 小时 9 分钟
30 天内合并 PR
376

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

callstackincubator/simlock 的其他 Issue

查看 callstackincubator/simlock 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。