Skip to content

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

Open

Description

@arekkubaczkowski

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.

Activity

  1. arekkubaczkowski commented on Nov 20, 2026

    @arekkubaczkowski
    ContributorAuthor

    Follow-up from the same worker, after deleting only the two iOS seeds with the xcrun simctl --set …/sources delete <udid> command that the refusal message suggests (daemon stopped, 0 leases): the switch to deviceSet: default then registered the iOS driver, but every iOS lease failed with PROVISION_FAILED: simctl clone <deleted seed udid> … Provided set path does not exist: ~/.simlock/devices/ios-sources. After switching back to simlock, it failed with Invalid device: <deleted seed udid>. state.db still had both seeds as ready rows in ios_source_data / ios_source_files, and simlock doctor reported no findings.

    So the documented xcrun simctl … delete remedy leaves Simlock unable to provision iOS on either set until those rows are removed. Removing exactly those rows (daemon stopped, DB backed up) fixed it, and a new seed was made in ios-sources. Suggestions: have doctor flag a ready seed whose simulator no longer exists, and have provisioning treat a missing seed as stale and re-seed instead of failing.

  2. added
    request:newInbox. Never picked up, body never edited.
    on Nov 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    request:newInbox. Never picked up, body never edited.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions