nw_socket_handle_socket_event [C39.1:1] Socket SO_ERROR [61: Connection refused]

[wzup]

React Native always sends this strange logs in Xcode console. This log is just infinite.

What does this log mean?
Is it normal for RN?
How to remove this behavior from my RN app?

[react-native-bot]

We are automatically closing this issue because it does not appear to follow any of the provided issue templates.

Please make use of the bug report template to let us know about a reproducible bug or regression in the core React Native library.

If you'd like to propose a change or discuss a feature request, there is a repository dedicated to Discussions and Proposals you may use for this purpose.

[wzup]

This is ridiculous!
Fix your bot. I raised a question that your bot doesn't understand.

[EricPKerr]

@wzup i'm running into this issue too. Did you resolve?

[msand]

Dupe of #21030

[ryd0rz]

+1

[vocampos]

+1

[ImranNaseem1989]

+1

[kisakov]

+1

[zazagag]

+1

[msand]

This should be fixed in the latest react-native. Provide a reproduction using the latest version, rather than +1 a closed issue which is a duplicate of a resolved problem.

[airlaser]

@msand I'm not seeing this fixed in 0.59.3. I see the code that should fix it, I'm definitely on 0.59.3, but I'm still getting the endless spam.

[lioPixiumDigital]

Still here in 0.59.5 too

[GreenRidingHood]

i have the same problem, my app stuck after success and metro-bundler shows 100%,
there is another ticket #24023 for this

react-native-cli: 2.0.1
react-native: 0.59.8
xcode Version 10.2.1 (10E1001)
build system Legacy

#24023 (comment) , i will try @patrickkempff solution and see

[GreenRidingHood]

@wzup like my previous comment @patrickkempff solution worked for me,

at AppDelegate.m , changing

return [[RCTBundleURLProvider sharedSettings] jsBundleURLForBundleRoot:@"index" fallbackResource:nil];

to

return [NSURL URLWithString:@"http://<ip of the packager>:8081/index.bundle?platform=ios"];

[mpmprudencio]

+1

[DataGreed]

same problem

[RWOverdijk]

@msand This issue has been around for a long time, and issues about this keep getting closed left and right. It's not fixed, still exists, and is really annoying, too.

Anything we can do to help?

[airlaser]

My solution was to switch to flutter, it's been more performant and lacks the various little issues like this. And when they do happen, they get fixed.

[msand]

@RWOverdijk Are you getting this error once on startup? Or does it keep writing that to the output every so often? The issue used to be that it kept retrying and eating up more memory. Now I only see it once on startup, so in that sense the issue is fixed already. I think facebook has some internal tools which aren't open source, and react-native is trying to connect to that, failing and thus causing this message. Either way it should only happen in development mode, and shouldn't be causing any issues as far as I know at the moment. Or do you have any other symptoms than this being written to output once?

I'm not on the core team, so I don't know anything about the actual difference in development environment internally at facebook vs open-source. And I don't have any power to change the logic related to this. I guess a configuration flag which would disable the system from even trying to connect would be useful, and wouldn't cause developers to go looking for the cause and fix for this warning/error message. What do you think @shergin ?

[RWOverdijk]

@msand This issue pops up while running, too. I filter out my logs now, but any other logs become impossible to read. And it keeps becoming more and more, like some old task keeps retrying while new tasks get spawned. I followed the upgrade paths from rndiff, so perhaps something wasn't in there and I missed a step? I'm on 0.59.10 right now, making the step to 0.60 once I fix issues with other libs, but I read that it should be fixed in 0.59.9 as well.

[packetstracer]

+1 here. Updated my Xcode and react-native-ble-plx in my project, and cannot start the app it gets stuck in Loaded 100%

[philipbapr]

+1 here. I just update my RN to the latest with xcode latest version to and this issue still appear.

Since this issue already close without any fix maybe we can create a new one