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

Ouverte
#1,797 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
45/100
Type d'issue
Fonctionnalité
Clarté
Clairement spécifiée
Activité
Active
Stack technique
android, ios, typescript
Domaine
cli, mobile-dev

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
TypeScript
Étoiles
705
Forks
40
Merge moyen
12 h 9 min
PR mergées (30 j)
376

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de callstackincubator/simlock

Toutes les issues de callstackincubator/simlock

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.