`yarn test-ios` exits before building RNTester: `objc-test.sh` launches the WebSocket server script #59433 deleted

Open Beginner friendly
#59,939 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

@lazerg is already working on this.

Since Nov 12, 2026.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
bash, javascript, node.js, react-native

Research direction

Start with scripts/objc-test.sh around lines 54–70 and 132–135, then inspect the RNTester integration tests and the linked deletion in PR #59433. Confirm whether any remaining test needs the WebSocket server on port 5555; update the test script to match the current tests. Done means yarn test-ios gets past server startup and proceeds to the packager and RNTester build.

Written by the indexing model from the issue text.

Description

Description

yarn test-ios (scripts/objc-test.sh test) starts the WebSocket test server with sh "./IntegrationTests/launchWebSocketServer.sh" & from packages/rn-tester, then waits for localhost:5555 to answer (L132-L135). https://github.com/react/react-native/pull/59433 deleted packages/rn-tester/IntegrationTests/, that script and websocket_integration_test_server.js among it, so waitForWebSocketServer polls sixty times and exits 1: on main the command stops before it builds RNTester or runs a test. No test left on main connects to port 5555.

No GitHub job runs yarn test-ios (#59596), and #59666, which turns it on in test_ios_rntester, counts on the script starting that server.

Steps to reproduce
  1. On macOS, in a checkout of main (0e4af152b8), run yarn test-ios; or run bash repro.sh from the reproducer below, which runs scripts/objc-test.sh test in a sparse clone of main with lsof stubbed, so the script's cleanup kills nothing listening on 8081 or 5555.

Expected: the script gets past the WebSocket server step to the packager and builds RNTester for testing.
Actual: it prints sh: ./IntegrationTests/launchWebSocketServer.sh: No such file or directory, retries localhost:5555 for a minute and exits 1 with WebSocket Server did not respond in time. No more attempts left.

React Native Version

main (0e4af152b8)

Affected Platforms

Build - MacOS

Output of npx @react-native-community/cli info

Not applicable: this is React Native's own test script. The reproducer's run: react-native 0e4af15 (2026-11-11), Darwin 27.2.0, bash 3.2.57(1)-release

Stacktrace or Logs
react-native 0e4af15 (2026-11-11), Darwin 27.2.0, bash 3.2.57(1)-release
packages/rn-tester/IntegrationTests/launchWebSocketServer.sh: missing
scripts/objc-test.sh:134:    sh "./IntegrationTests/launchWebSocketServer.sh" &
scripts/objc-test.sh:135:    waitForWebSocketServer
  Launch WebSocket Server
  sh: ./IntegrationTests/launchWebSocketServer.sh: No such file or directory
  WebSocket Server did not respond in time. No more attempts left.
scripts/objc-test.sh test exited 1 after 62s, retrying localhost:5555 59 times
SUMMARY: yarn test-ios stops before building RNTester: it launches packages/rn-tester/IntegrationTests/launchWebSocketServer.sh, which is missing, and exits 1 when nothing answers on localhost:5555
MANDATORY Reproducer

https://gist.github.com/YevheniiKotyrlo/6235683cdbbb2507855f997fa6023f79 — bash repro.sh exits 1 while yarn test-ios stops at the WebSocket server and 0 once it gets past it to the packager.

Screenshots and Videos

No response

Dominant language
C++
Stars
127k
Forks
25.5k
Avg merge
3d 22h
Merged PRs (30d)
235

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from react/react-native

All issues in react/react-native

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.