Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

iOS: make the device set configurable so Xcode tools can target a leased simulator

Chiusa
  • Qualcosa non va?
#946 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
ios, typescript
Ambito
developer-experience, infrastructure

Direzione di ricerca

Start with ADR 0001 and the iOS device set configuration and lifecycle code; the issue does not name specific files for the change. First map how the worker selects and manages its CoreSimulator device set, then define the default, runtime-change behavior, and simlock simctl behavior alongside the recovery risks. Done means the spec resolves those open questions and documents the effects of targeting the default set.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

request:new

Problem

Simlock's iOS simulators live in their own CoreSimulator device set (ADR 0001). No Xcode tool can target a simulator there from the command line: xcodebuild -destination "platform=iOS Simulator,id=<udid>", react-native run-ios --udid, Expo, Detox, Maestro and agent-device's XCTest runner all read the default set. The only switch is the per-user DVTSimulatorSetLocation default, which leaks into every xcodebuild run of that user and hides the default-set simulators while set. Every per-process route was tested and does not work. The docs never mention the limit, and the only workaround is to build for generic/platform=iOS Simulator and install with simlock simctl install.

Android does not have this problem: adb, Gradle and the RN CLI honour ANDROID_ADB_SERVER_PORT, so the separate adb server is compatible with the tooling. The question is about iOS only.

Proposal: make the iOS device set configurable, ios.deviceSet: "simlock" | "default", and decide which is the default.

What the isolation buys and costs

Buys: an accident boundary. xcrun simctl shutdown all, erase all, delete unavailable, Xcode's "Delete All Simulators" and an RN CLI that picks booted cannot touch a leased device. src/drivers/AGENTS.md calls the root "an accident boundary, not a security boundary".

Costs: the primary use-cases cannot build onto a leased device without the generic-build detour, and UI test runners cannot target it at all.

What dropping it does not break: cleanup, nuke and the warm pool act only on devices the registry owns, so a developer's own simulators stay safe. Devices are already named simlock-<uuid>. A leased device that is shut down from outside is already rebooted under its lease; a deleted one already ends its lease as device-lost.

What dropping it costs: a developer whose Mac is a worker sees every simlock-… device in Xcode's destination picker. A stray erase all wipes an agent's in-progress state, and recovery reboots but does not reinstall. The refusal list in simlock simctl protects nothing once agents run xcrun simctl directly.

Context

Found in the 2026-10-23 product review. The maintainer rejected the per-user default on 2026-09-14 and on 2026-10-23 chose to keep the isolation and document the generic build for now, then asked for this to be made configurable.

Open questions for the spec session: the default value (the review leaned to default once recovery after an external shutdown or erase is tested and the docs state what a careless simctl … all does); whether the key can change on a running worker or needs nuke --delete-devices; what simlock simctl does under default (plain passthrough, or still refuse the lifecycle commands); the ADR that supersedes 0001 for iOS.

Written by an agent.

Lingua principale
TypeScript
Stelle
22
Fork
2
Merge medio
9h 14m
PR unite (30g)
425

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di callstackincubator/simlock

Tutte le issue di callstackincubator/simlock

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.