App Flow offers no simulator selection when multiple iOS devices match

未關閉
#106 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
3/5
預估耗時
1-2 天
新手友好度
35/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
cpp, ios
領域
mobile-dev

研究方向

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.

由索引模型根據 Issue 內容生成。

描述

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.

主要語言
C++
星號
243
分支
21
平均合併
15 小時 6 分鐘
30 天內合併 PR
57

環境準備

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

callstackincubator/codex-mobile-dev-plugin 的其他 Issue

查看 callstackincubator/codex-mobile-dev-plugin 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。