Xcode 10 runtime warning on fresh install: nw_socket_handle_socket_event

[mog3n]

Description

While running the boilerplate react native app, I receive the runtime error:
2018-09-09 21:46:07.681496-0400 client[2035:560210] [] nw_socket_handle_socket_event [C6.2:1] Socket SO_ERROR [61: Connection refused] 2018-09-09 21:46:07.681861-0400 client[2035:560216] [] nw_connection_get_connected_socket [C6] Client called nw_connection_get_connected_socket on unconnected nw_connection 2018-09-09 21:46:07.681903-0400 client[2035:560216] TCP Conn 0x2821ac300 Failed : error 0:61 [61]
which loops over and over for the duration of debugging the app on a device. I'm not sure exactly what this error is associated with, however in my other app I receive the same error. This may or may not be related to remote push notifications (APNs).

Environment

React Native Environment Info: System: OS: macOS 10.14 CPU: x64 Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz Memory: 27.59 MB / 16.00 GB Shell: 3.2.57 - /bin/bash Binaries: Node: 9.8.0 - /usr/local/bin/node Yarn: 1.5.1 - /usr/local/bin/yarn npm: 5.6.0 - /usr/local/bin/npm Watchman: 4.9.0 - /usr/local/bin/watchman SDKs: iOS SDK: Platforms: iOS 11.4, macOS 10.13, tvOS 11.4, watchOS 4.3 IDEs: Xcode: 9.4.1/9F2000 - /usr/bin/xcodebuild npmPackages: react: 16.4.1 => 16.4.1 react-native: 0.56.0 => 0.56.0 npmGlobalPackages: create-react-native-app: 1.0.0 react-native-cli: 2.0.1

Reproducible Demo

1. react-native init
2. react-native run-ios
3. In Capabilities, enable both 'Notifications' and Background Modes -> Enable 'Remote notifications'
4. Open Xcode and select a connected iPhone
5. Launch/debug the app and open the Xcode console

A couple of notes:

• Device is iPhone X on iOS 12.0 beta (16A5366a)
• Building the app using Xcode 10.0 beta 2 (10L177m) beta, while react-native run-ios builds using Xcode 9.4.1
• macOS is running 10.14 Beta (18A377a)

[mog3n]

UPDATE This only happens when I run it on an iOS 12 device!!! (Doesn't matter what I build with) Reverting back to iOS 11 for now.

[yacut]

same issue with 0.57.0 version:

react-native info
  React Native Environment Info:
    System:
      OS: macOS High Sierra 10.13.6
      CPU: x64 Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
      Memory: 690.77 MB / 16.00 GB
      Shell: 5.3 - /bin/zsh
    Binaries:
      Node: 8.11.4 - /usr/local/bin/node
      Yarn: 1.9.4 - /usr/local/bin/yarn
      npm: 5.6.0 - /usr/local/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 12.0, macOS 10.14, tvOS 12.0, watchOS 5.0
    IDEs:
      Android Studio: 3.1 AI-173.4907809
      Xcode: 10.0/10A255 - /usr/bin/xcodebuild
    npmPackages:
      @types/react-native: ^0.56.21 => 0.56.21 
      react: 16.5.1 => 16.5.1 
      react-native: ^0.57.0 => 0.57.0 

[nebulashine]

Is this resolved? I'm also seeing messages like:
2018-09-18 15:25:36.721046-0700 AwesomeProject[18908:21074308] [] nw_socket_handle_socket_event [C4.1:1] Socket SO_ERROR [61: Connection refused]
2018-09-18 15:25:36.728264-0700 AwesomeProject[18908:21074308] [] nw_socket_handle_socket_event [C4.2:1] Socket SO_ERROR [61: Connection refused]
2018-09-18 15:25:36.734951-0700 AwesomeProject[18908:21074298] [] nw_connection_get_connected_socket [C4] Client called nw_connection_get_connected_socket on unconnected nw_connection

[BANG88]

Temporary fix:

Edit Scheme => Run => Environment Variables => Add OS_ACTIVITY_MODE:disable

[fulvio-m]

Temporary fix:

Edit Scheme => Run => Environment Variables => Add OS_ACTIVITY_MODE:disable

This works fine, but keep in mind that it also suppresses all NSLog output you may need for debugging.

[Jackyaung]

I also have the same problem, it keeps running and the memory is getting big and big, when it reached 15G, my computer crushed

[jnicholls]

Any info on this? I am too seeing a spew of these errors in debug output when running my app on a device. I haven't tracked memory consumption on the device yet but I will do that soon to see if this is a show-stopping issue that would prevent me from releasing my app.

EDIT: While I haven't seen me any absurd memory growth, it is chewing through an abnormal amount of CPU while in this cycle of establishing connections.

[divsbhalala]

I also having same issue with xcode 10 and IOS12

[yehia123]

I am receiving this error ReactProject[12849:185872] [] nw_connection_get_connected_socket [C62] Client called nw_connection_get_connected_socket on unconnected nw_connection and my computer becomes completely slow while running it.

[abegehr]

The same problem for me on Xcode 10 iOS 12 Simulator.

Temporary fix:

Edit Scheme => Run => Environment Variables => Add OS_ACTIVITY_MODE:disable

This fixes the issue on iOS 12 Simulator. Could someone explain what this does?

I will test later on iOS 11.

[ZachOrr]

Hey all - “Same” and “+1” are not particularly helpful for this discussion.

[harrisrobin]

Weird,

doing

rm -rf $TMPDIR/react-* && watchman watch-del-all && yarn cache clean

worked for me. Maybe it wouldn't hurt to add a --reset-cache after the start script, but I did not have to do that!

[cjadhav]

If someone is looking for temporary get rid of this issue then apply filter in XCode console with [info][tid:com.facebook.react.JavaScript]

So we can see our required debug log.. 😆

[mmmulani]

please stop commenting with +1/"me too". It's more frustrating than helpful.

about this issue, it's caused by Apple changing the error messages in their network stack making our fishhook logic no longer work. (Found here: https://github.com/facebook/react-native/blob/master/Libraries/WebSocket/RCTReconnectingWebSocket.m)

@maicki do you have any spare cycles to take a look at getting this working?

[dbreese]

No idea if this helps, but just an observation -- when I see this issue, I can watch the number of ports being reported for Xcode via Activity Monitor keeps climbing. On my Mac Pro trashcan, OSX will eventually become unusable and crash, usually when the ports climb to around 200,000.

Looks like the number of ports grows by about 20 every 2 seconds.

I don't see any odd data via netstat or lsof.

Hardly any CPU usage for me, just the ports slowly climbing and eventually OSX crashing and requiring a power cycle to recover.

[LuisRizo]

For me, @dembe1's solution didn't work since I'm using Electrode Native and we don't have that in our AppDelegate.m. However, we don't use sockets in our react-native app so I went to the source of the reconnections and prevented them from happening.

On RN 0.57.8 and electrode-native version 0.30, the culprit was RCTInspectorPackagerConnection.m at line 200.

- (void)webSocket:(RCTSRWebSocket *)webSocket didFailWithError:(NSError *)error
{
  if (_webSocket) {
    [self abort:@"Websocket exception"
      withCause:error];
  }
  if (!_closed) {
    [self closeAllConnections]; // <- Change to this. Before it was `[self reconnect];
  }
}

This removed all those annoying reconnect logs.

This change is a bit overkill, I'm sure commenting out the [self reconnect]; would have been enough, but since we don't use sockets, this is fine for us. It might have some side-effects, I'm no iOS expert, but it works for me, so maybe it will work for others.

UPDATE:

For my team members, that wasn't enough. I also had to remove the [self reconnect]; calls on RCTReconnectingWebSocket.m on lines 166 and 172.

After that, no more logs.

[IAmMarcellus]

I'm using react native 0.59.5 and I'm getting these errors. However this version of react native uses:
RCTRootView *rootView = [[RCTRootView alloc] initWithBridge:bridge
instead of RCTRootView *rootView = [[RCTRootView alloc] initWithBundleURL:jsCodeLocation
so I can't implement the:
[[RCTBundleURLProvider sharedSettings] setJsLocation:jsCodeLocation.host]; fix.
Is there any way to implement that fix using the bridge instead of initWithBundle?

[aibek-bird]

Having the same issue on iOS 12.1.4, react-native: 0.59.5, XCode 10.2.1.

Runs many times:

2019-05-15 16:21:41.751022+0900 AppName[525:278667] TCP Conn 0x2820d4480 Failed : error 0:61 [61]
2019-05-15 16:21:43.869817+0900 AppName[525:252581] [] nw_socket_handle_socket_event [C25.1:1] Socket SO_ERROR [61: Connection refused]

Any updates?

[kenjdavidson]

Was having the same issue on:

• IOS 12.2

• XCode 12.2.1

• RN 0.59.8

Looking at the comments on a number of posts I was able to resolve the issue by applying pretty much the same fix to AppDelegate.m. First of all, I'm terribly new to Objective-C so I'm sure this could be prettier, but its effective:

- (NSURL *)sourceURLForBridge:(RCTBridge *)bridge
{
#if DEBUG
  NSURL *jsUrl = [[RCTBundleURLProvider sharedSettings] jsBundleURLForBundleRoot:@"index" fallbackResource:nil];
  [[RCTBundleURLProvider sharedSettings] setJsLocation:jsUrl.host];
  return [[RCTBundleURLProvider sharedSettings] jsBundleURLForBundleRoot:@"index" fallbackResource:nil];
#else
  return [[NSBundle mainBundle] URLForResource:@"main" withExtension:@"jsbundle"];
#endif
}

[thingthing]

@kenjdavidson thanks, it works perfectly! Just you can optimize the code a little bit by reusing the jsUrl variable:

- (NSURL *)sourceURLForBridge:(RCTBridge *)bridge
{
#if DEBUG
  NSURL *jsUrl = [[RCTBundleURLProvider sharedSettings] jsBundleURLForBundleRoot:@"index" fallbackResource:nil];
  [[RCTBundleURLProvider sharedSettings] setJsLocation:jsUrl.host];
  return jsUrl;
#else
  return [[NSBundle mainBundle] URLForResource:@"main" withExtension:@"jsbundle"];
#endif
}

[GreenRidingHood]

#24023 (comment) @patrickkempff 's solution possibly help

[noahtallen]

I'm also on 0.59.8 and the latest iOS and Xcode. My workaround looks like this:

- (NSURL *)sourceURLForBridge:(RCTBridge *)bridge
{
#if DEBUG
  NSURL *jsUrl = [[RCTBundleURLProvider sharedSettings] jsBundleURLForBundleRoot:@"index" fallbackResource:nil];
  [[RCTBundleURLProvider sharedSettings] setJsLocation:jsUrl.host];
  return jsUrl;
#else
  return [[NSBundle mainBundle] URLForResource:@"main" withExtension:@"jsbundle"];
#endif
}

The errors are gone while I do have a JS debugger open, but

2019-05-26 13:10:24.616366-0400 zonder[73455:1923229] [] nw_socket_handle_socket_event [C224.1:1] Socket SO_ERROR [61: Connection refused]
2019-05-26 13:10:24.618005-0400 zonder[73455:1923229] [] nw_socket_handle_socket_event [C224.2:1] Socket SO_ERROR [61: Connection refused]
2019-05-26 13:10:24.618761-0400 zonder[73455:1923229] [] nw_connection_get_connected_socket [C224] Client called nw_connection_get_connected_socket on unconnected nw_connection

just repeats indefinitely while I'm not debugging JS. So I guess the solution isn't working for me :(

[dan-abc]

@noahtallen, @IAmMarcellus I’ve found moving the RCTBundleURLProvider call to applicationDidFinishLaunchingWithOptions seems to fix the nw_socket_handle_socket_event errors both in and not in JS debug mode.

[[RCTBundleURLProvider sharedSettings] setJsLocation:[self sourceURLForBridge:bridge].host];

I added the line directly after the [[RCTRootView alloc] initWithBridge:bridge... call.

[noahtallen]

@DShepherd Huh. I just tried that and the logs still show up for me

[jvandenaardweg]

Did all of the above, but did not really work. Then I noticed a CORS error in the Chrome debugger. Switched to React Native Debugger (https://github.com/jhen0409/react-native-debugger), rebuild the app, and it started working on my device.

The cors error prevented from connecting to the socket i guess

I hope this could be helpful to someone.

To summarize what I did:

1. Editted my AppDelegate.m to reflect the latest template version, as I was using a version that looked a bit different. Latest version: https://github.com/facebook/react-native/blob/master/template/ios/HelloWorld/AppDelegate.m
2. Then, editted my AppDelegate.m to use the change suggested above: Xcode 10 runtime warning on fresh install: nw_socket_handle_socket_event #21030 (comment)
3. Close any open Chrome debugger
4. Open the React Native Debugger
5. Clean build
6. Rebuild the App, target your own device
7. Wait for the Metro bundler to complete bundling (see your terminal), that could take a little. In the mean time you'll see websocket connection errors, as the bundler is not ready yet.
8. Wait for the app to open. Logs should now start flowing into React Native Debugger

While the app is running, you should not see any socket connection errors again in the logs

AppDelegate.m

/**
 * Copyright (c) Facebook, Inc. and its affiliates.
 *
 * This source code is licensed under the MIT license found in the
 * LICENSE file in the root directory of this source tree.
 */

#import "AppDelegate.h"
#import <AppCenterReactNativeCrashes/AppCenterReactNativeCrashes.h>
#import <AppCenterReactNativeAnalytics/AppCenterReactNativeAnalytics.h>
#import <AppCenterReactNative/AppCenterReactNative.h>

#import <React/RCTBundleURLProvider.h>
#import <React/RCTRootView.h>
#import "RNSplashScreen.h"

// iOS 9.x or newer
// https://facebook.github.io/react-native/docs/linking
#import <React/RCTLinkingManager.h>

@implementation AppDelegate

// https://facebook.github.io/react-native/docs/linking
- (BOOL)application:(UIApplication *)application
            openURL:(NSURL *)url
            options:(NSDictionary<UIApplicationOpenURLOptionsKey,id> *)options
{
  return [RCTLinkingManager application:application openURL:url options:options];
}

- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{

  // Custom added
  [AppCenterReactNativeCrashes registerWithAutomaticProcessing];
  [AppCenterReactNativeAnalytics registerWithInitiallyEnabled:false];
  [AppCenterReactNative register];

  RCTBridge *bridge = [[RCTBridge alloc] initWithDelegate:self launchOptions:launchOptions];
  RCTRootView *rootView = [[RCTRootView alloc] initWithBridge:bridge
                                                   moduleName:@"MyApp"
                                            initialProperties:nil];

  // Custom editted
  // Original:
  // rootView.backgroundColor = [[UIColor alloc] initWithRed:1.0f green:1.0f blue:1.0f alpha:1];
  rootView.backgroundColor = [UIColor blackColor];

  self.window = [[UIWindow alloc] initWithFrame:[UIScreen mainScreen].bounds];
  UIViewController *rootViewController = [UIViewController new];
  rootViewController.view = rootView;
  self.window.rootViewController = rootViewController;
  [self.window makeKeyAndVisible];

  // Custom added
  [RNSplashScreen show];

  return YES;
}

- (NSURL *)sourceURLForBridge:(RCTBridge *)bridge
{
#if DEBUG

  // Custom added:
  // This prevents the logs from constantly showing websocket connection errors
  // https://github.com/facebook/react-native/issues/21030#issuecomment-493392051
  // original:
  // return [[RCTBundleURLProvider sharedSettings] jsBundleURLForBundleRoot:@"index" fallbackResource:nil];
  NSURL *jsUrl = [[RCTBundleURLProvider sharedSettings] jsBundleURLForBundleRoot:@"index" fallbackResource:nil];
  [[RCTBundleURLProvider sharedSettings] setJsLocation:jsUrl.host];
  return jsUrl;
#else
  return [[NSBundle mainBundle] URLForResource:@"main" withExtension:@"jsbundle"];
#endif
}

@end

[noahtallen]

I'm also using react native debugger (which works great like you say!), but the logs show up for me when I turn off remote JS debugging

[jerodb]

@dembe1 solution from Mar 10 worked for me. He gives an excellent explanation of this issue btw!

[DataGreed]

The same problem is still present even on 0.59.9, I wonder how facebook engineers don't run in the same issue on daily basis 🤔

[DataGreed]

Okay on 0.59.9 cleaning up the build folder and rebuilding the app helps. If you need a debuger, https://github.com/jhen0409/react-native-debugger works as @jvandenaardweg suggested (chrome debugger shows CORB errors).

The annoying thing is that even with the app working and debugger working I see a neverending stream of errors in xcode console:

2019-08-12 12:37:12.707914+0100 MyApp[13292:3989531] [] nw_socket_handle_socket_event [C15913.1:1] Socket SO_ERROR [61: Connection refused]
2019-08-12 12:37:12.708742+0100 MyApp[13292:3989531] [] nw_socket_handle_socket_event [C15913.2:1] Socket SO_ERROR [61: Connection refused]
2019-08-12 12:37:12.708899+0100 MyApp[13292:3989451] [] nw_connection_get_connected_socket [C15913] Client called nw_connection_get_connected_socket on unconnected nw_connection
2019-08-12 12:37:12.708912+0100 MyApp[13292:3989451] TCP Conn 0x28085ad00 Failed : error 0:61 [61]

I mean, what exactly is it trying to connect to? The Metro bundler works properly and the debugger is connected, what's happening?

[msand]

I think fb uses quite a different debug setup internally, and it's supposed to connect to that.

[allnash]

Kinda ridiculous, that everyone is struggling with the tools rather than the actual appplication code.

[echokk11]

Xcode 11, IOS13, RN 0.57.8
stuck here.

2019-09-30 17:59:34.364815+0800 kardashian[8997:267918] [] nw_socket_handle_socket_event [C268.2:1] Socket SO_ERROR [61: Connection refused]
2019-09-30 17:59:34.365713+0800 kardashian[8997:267914] [] nw_connection_get_connected_socket [C268] Client called nw_connection_get_connected_socket on unconnected nw_connection
2019-09-30 17:59:36.379120+0800 kardashian[8997:267918] [] nw_socket_handle_socket_event [C269.1:1] Socket SO_ERROR [61: Connection refused]
2019-09-30 17:59:36.380715+0800 kardashian[8997:267918] [] nw_socket_handle_socket_event [C269.2:1] Socket SO_ERROR [61: Connection refused]
2019-09-30 17:59:36.381649+0800 kardashian[8997:267907] [] nw_connection_get_connected_socket [C269] Client called nw_connection_get_connected_socket on unconnected nw_connection
2019-09-30 17:59:38.395820+0800 kardashian[8997:267907] [] nw_socket_handle_socket_event [C270.1:1] Socket SO_ERROR [61: Connection refused]
2019-09-30 17:59:38.397339+0800 kardashian[8997:267907] [] nw_socket_handle_socket_event [C270.2:1] Socket SO_ERROR [61: Connection refused]

[rrapiteanu]

Possible solution: Check if your mac and phone are on the same wifi network lol :((.

[echokk11]

Possible solution: Check if your mac and phone are on the same wifi network lol :((.

of cause it is

[EternalChildren]

it still exists in react-native@0.61.2. i have try each solution above, but don't work for me. Is there a perfect solution to this problem?

[lefoy]

For people complaining about "me too" and +1s, don't say it is not useful because it is, nobody is looking at this issue and the bot will just close the issue if there's no reply. So yes, keep the issue alive, github will hide similar messages.

[CodeToTee]

FWIW, I was a hitting different issue that led me here. Specifically, when running on an actual iOS device, I was receiving a red-box message that "Connection to http://my-ip-address:8081/debugger-proxy?role=client timed out. Are you running node proxy? If you are running on the device, check if you have the right IP address in RCTWebSocketExecutor.m.

I noticed that this issue occurred when I switched between two different networks (call them A and B). When running on network B, the IP address in the message above was from network A. I finally figured out that if I delete the test application from the iOS device, then re-run, the app would then correctly use network B and the issue was resolved. So, now I know that when I change networks, I simple delete the test app (and its data) to resolve this issue.

There is probably a more precise way to resolve this, but deleting the app worked fine for me. Clearly something on the iOS device is remembering the IP address from a different network and trying to reuse it.

Hopefully this post will save someone some time!