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

Offen
#1,797 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
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
45/100
Issue-Typ
Feature
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
android, ios, typescript
Bereich
cli, mobile-dev

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
TypeScript
Sterne
705
Forks
40
Ø Merge
12 Std. 9 Min.
Gemergte PRs (30 T.)
376

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

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 callstackincubator/simlock

Alle Issues in callstackincubator/simlock

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

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