CI runs: prepare each leased device (language, reduce motion, permissions, keychain reset)

Abierto
#1,634 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
typescript

Línea de trabajo

Start by reading the linked request #1294 and the spec discussion on #327, then compare the existing lease request and named baseline behavior. The issue leaves the central design choices open: whether to add settings to lease requests and whether keychain reset belongs here. Done means the team resolves those choices and defines how CI leases get devices into the required state.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

feature:spec

Request: #1294

Problem

A CI run that leases many devices has to prepare each one by hand. budgie's e2e suite (budgie-at/budgie#1867) runs simctl through POST /v1/leases/<id>/exec on every lease: keyboard and language (AppleKeyboards, AppleLanguages -array en-US), reduce motion, privacy grant contacts|microphone <bundle id>, and a keychain reset before each test, so a PIN one test set can't lock out the next. The lease request has no field for any of this; the Maestro setup it replaces had simulator-reduce-motion and simulator-device inputs.

A named baseline prepared with these settings covers most of it today, but that means one baseline per settings combination, set up by an operator, and the per-test keychain reset is not covered.

Split from #1633 (release every lease of a run) in the spec session of 2026-11-17: the two halves of #1294 share no decision.

Who it is for

A CI job that leases 5–10 simulators per run on a shared farm and needs each one in a known state before its tests.

Open questions

  • Is a named baseline the answer (then document how to make one for a CI suite), or should the lease request also take common settings (language/locale, reduce motion, permission grants for a bundle id)? A spec session on #327 (2026-11-02) kept the rule that Simlock copies devices and runs no setup of its own; settings in the request would change it.
  • Does a keychain reset belong here, or does it need its own call?

Written by an agent.

Lenguaje dominante
TypeScript
Estrellas
705
Forks
40
Merge medio
12 h 9 min
PR fusionados (30 d)
376

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de callstackincubator/simlock

Todos los issues de callstackincubator/simlock

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.