Repository navigation
Support Windows hosts #247
Description
Harness runs on macOS and Linux today. This issue tracks the work to make Harness run on Windows hosts: the CLI, the Jest runner, the device lock, and the Android, Vega, and Web platforms.
Each linked issue reports a Windows-specific failure, or one that was observed on a Windows host. Closed items are already fixed and are listed for reference.
Open
- Windows Android SDK path not found #183: Windows Android SDK path not found
- Android platform fails on Windows hosts #191: Android platform fails on Windows hosts (the umbrella for Android; Windows Android SDK path not found #183 and Android runner can't start on a Windows host: SDK binaries are looked up without .exe or .bat #201 are its first two failures)
- On Windows, Jest cannot find the react-native-harness preset #222: On Windows, Jest cannot find the react-native-harness preset
- On a Windows host, a test's file name reaches the device with backslashes #216: On a Windows host, a test's file name reaches the device with backslashes
- On Windows, the device lock fails while another run deletes a lock file #218: On Windows, the device lock fails while another run deletes a lock file
- platform-vega's Metro enhancer test fails on Windows #219: platform-vega's Metro enhancer test fails on Windows
- The pre-push hook builds the same packages twice at once #225: The pre-push hook builds the same packages twice at once (two
tsc --buildruns collide on Windows) - Timeout diagnostics lose the promise a hung test awaits once it is garbage-collected #217: Timeout diagnostics lose the promise a hung test awaits once it is garbage-collected (flaked on Windows CI)
- On Windows, sdkmanager.bat and avdmanager.bat fail on any argument #259: On Windows, sdkmanager.bat and avdmanager.bat fail on any argument
- A user's ANDROID_AVD_HOME is overwritten with ~/.android/avd #260: A user's ANDROID_AVD_HOME is overwritten with ~/.android/avd
- platform-ios's crash diagnostics test fails on Windows because it expects forward slashes #261: platform-ios's crash diagnostics test fails on Windows because it expects forward slashes
Closed
- Android runner can't start on a Windows host: SDK binaries are looked up without .exe or .bat #201: Android runner can't start on a Windows host: SDK binaries are looked up without .exe or .bat
- The iOS package's tests never run:
platform-applehas notesttarget #232: The iOS package's tests never run (Windows also failed to load two files that resolvepackage.jsonthroughimport.meta.url)
Done when
- The Android, Vega, and Web platforms run end to end on a Windows 11 host.
- The Jest preset resolves on Windows with the Jest version the CLI pins.
- Path, lock, and process handling behave the same on Windows and POSIX.
- The unit test suite passes on a Windows CI job.
Activity
platform-applehas notesttarget #232TheSeydiCharyyev commentedon Oct 22, 2026
I ran
mainat 81ed195 on a Windows 11 host (10.0.26200, Node 24.17.0, pnpm 10.6.1 through corepack).pnpm build:all,pnpm test:all,pnpm lint:all,pnpm typecheck:all: all pass.--config jest.harness.crash.config.mjs --testPathPatterns src/__tests__/crash/android) withharness_crash_modeset topre_rnand todelayed_pre_ready: Harness exits with code 1, both test files report the crash, and.harness/crash-reportsgetslogcat.txtanddropbox-crash.txtfor each file.pass/withHARNESS_TEST_TIMEOUT=40000: 3 of 3 pass.fail/hangandfail/middle-chunk-failurefail with the errors their comments describe, and the code frame points atassertion-helper.tsline 5.Not covered:
sdkmanager/avdmanager, On Windows, sdkmanager.bat and avdmanager.bat fail on any argument #259).fail/connection-lost: it needskill -STOPon the app process, and this emulator image has no root.