App Flow offers no simulator selection when multiple iOS devices match

Abierto
#106 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
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
cpp, ios
Área
mobile-dev

Línea de trabajo

Start with the App Flow Screen UI capture path and the Regenerate and Launch App handlers, then find where the generic iOS target is resolved against installed simulators. Look for where the "devices match this request equally" error is raised and whether the selected simulator ID is carried into the capture input. Done means a selected simulator survives Regenerate and Launch App, or the capture UI offers a way to pick one when several match. Related context is in #101.

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

Descripción

bug

What happened

After stopping the previously selected iOS simulator, the presenter retried App Flow Screen UI → Regenerate. App Flow reported 11 devices match this request equally. Select one explicitly. The Mobile Dev picker still showed the selected simulator, and App Flow's capture options did not provide a target choice. The presenter asked where to select one and could not proceed.

Expected behavior

App Flow should use a clearly selected compatible simulator or offer a way to resolve ambiguity from the capture UI. Carry the selected target through Regenerate and Launch App. The current capture input has no device ID, and the generic iOS target can match several installed simulators. The earlier active-session ownership error is tracked in #101.

Lenguaje dominante
C++
Estrellas
243
Forks
21
Merge medio
15 h 6 min
PR fusionados (30 d)
57

Preparar el entorno

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/codex-mobile-dev-plugin

Todos los issues de callstackincubator/codex-mobile-dev-plugin

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.