NetInfo.isConnected.addEventListener: diverging behaviors on Android and iOS about react-native-netinfo HOT 3 CLOSED

I think I've managed to reproduce this with an integration test actually. I believe that it's a timing issue. It emits on both platforms if you subscribe close to the app launch, however, if you set up a listen a while after the app launch then the Android one is not called and the iOS one is. You should be able to confirm this by instead setting up the listener on a button press.

I am looking into making it so the listener will always emit when you begin listening to it, and then on any changes, on both platforms.

from react-native-netinfo.

I did some basic testing and I could not repro this bug (which was filed before the migration to this repo). I realize this contradicts this snackable example, and I don't really have an explanation for why that is.

I am using @react-native-community/[email protected] and I've linked the migrated project on Android and iOS.

Here is the code I tested

NetInfo.addEventListener("connectionChange", (connectionInfo) => console.log(JSON.stringify(connectionInfo)));

Note that I never called NetInfo.isConnected.fetch()

On iPhone 6 - 12.1 Simulator

• The connectionChange event listener fired on app launch

On a real Android HTC Desire 530 (Android 6.0.1)

• The connectionChange event listener fired on app launch

This leads me to conclude that this is the current behavior (which is unclear from the docs BTW):
connectionChange event listener fired on initial register AND on subsequent network state changes.
es

from react-native-netinfo.

🎉 This issue has been resolved in version 2.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

from react-native-netinfo.