forked from expo/expo
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[ios] Build client with ENABLE_PACKAGER_CONNECTION=0 to fix websocket…
… spam RN has "packager connection" code that attempts to visit a (mostly) hardcoded URL with a hardcoded port and repeatedly tries to reconnect without backoff, leading to hundreds or thousands of bad requests. I looked into the packager connection code on both iOS and Android -> it receives commands from the packager such as taking a heap snapshot or reloading. Searching all of RN and Metro, these commands aren't sent and it looks like open-source doesn't actually use this feature. (Live reload uses a different mechanism.) For the iOS client, I built it with `ENABLE_PACKAGER_CONNECTION=0` which mitigates this request spam. There are still some `nw_socket` log messages but no longer dozens per second. XDL (Podfile generation) changes are here: expo/expo-cli#78 Test plan: build the iOS client from source and verify that it doesn't spam as many `nw_socket` errors. Test live reload with NCL.
- Loading branch information
Showing
11 changed files
with
849 additions
and
22,962 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters