SIGSEGV in production for all instances invoking setReachabilityStatus

• [ x] I have reviewed the documentation
• [x ] I have searched existing issues
• [x ] I am using the latest React Native version

We’re seeing elevated crash reports relating to a member invocation setReachabilityStatus on several instance types, resulting in a SIGSEG triggered by unrecognized selector sent to instance.

Here’s info from a crash report:

Environment

Environment: OS: macOS High Sierra 10.13.4 Node: 9.4.0 Yarn: 1.3.2 npm: 5.6.0 Watchman: 4.9.0 Xcode: Xcode 9.3 Build version 9E145 Android Studio: 3.0 AI-171.4443003

Packages: (wanted => installed) react: 16.3.0 => 16.3.0 react-native: 0.55.0 => 0.55.0

Steps to Reproduce

1. Open app that uses the setReachabilityStatus method in native code somewhere.
2. Go home, then change your network (disable cellular service)
3. Open the app back up
4. The app will crash

Expected Behavior

No crashes 😃

Actual Behavior

Lots of crashes

[mmmulani]

are you able to repro this on master? my understanding is that https://github.com/facebook/react-native/commit/9d45de60accda028d11b715a3407119353a81d2c#diff-82c5d95c19a17c3f2375f0b1e09f6da4 solves this

[devey]

@mmmulani sorry for the delay. I tried with 0.55.4 and works smoothly; it would be great to cheery into 0.55.3.

Thanks.