You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(rn): separate emulator launch from readiness verification
Split emulator/simulator processes into launch and verify steps to fix
deployment when devices are already running.
Problem: When an emulator/simulator was already running, deploy tasks
failed because they depended on launch process health, but the launch
process would exit immediately if device was already up.
Solution:
- launch-emulator/launch-simulator: Checks if device is running, starts
if needed, then exits (may skip if already running)
- verify-emulator-ready/verify-simulator-ready: Always runs, waits for
device to be ready regardless of how it started
- Deploy tasks now depend on verify-*-ready instead of launch health
This enables iteration in dev mode where devices persist between test runs.
Changes:
- test-suite-android-e2e.yaml: Split android-emulator into launch + verify
- test-suite-ios-e2e.yaml: Split ios-simulator into launch + verify
- test-suite-all-e2e.yaml: Split both platforms into launch + verify
- Updated device lock files from test runs
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
0 commit comments