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

オープン
#1,797 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
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分
マージ済み PR(30日)
376

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

callstackincubator/simlock のほかの issue

callstackincubator/simlock の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。