Multiple inconsistencies in lib behavior (Android)

Tested on React Native (Android only):

• 0.59.8
• 0.60.3
• 0.62.2

We are trying to integrate this library in a production level. So far, we’ve stumbled upon numerous issues, that do not appear to have been resolved in version 4.1.0.

Xiaomi Redmi Note 8 Pro - MIUI version 11.0.3.0 (based on Android P)

• Wifi permission request loop that breaks randomly (with or without user interaction)
• Connects to Wifi with internet connectivity, but cannot perform external API requests

Huawei P30 Lite - EMUI version 9.1.0 (based on Android P)

• Connects to Wifi with internet connectivity inconsistently
• Cannot connect to IOT device in the same WLAN

Xiaomi A2 Lite - Android One (Android Q)

• Connects to Wifi consistently, always without internet connectivity

Example usage:

const connect = () => {
  WifiManager.forceWifiUsage(true);
  WifiManager.connectToProtectedSSID(ssid, password, false)
    .then(() => {
      // do stuff
    })
    .catch(() => {
      // handle error
    })
    .finally(() => WifiManager.forceWifiUsage(false));
};

Based on the information above, can you point me to a certain direction as to what the issue may be?

[Rapsssito]

@dimgrav, looks like forceWifiUsage() causes some connectivity issues (see #76). If you are using a TCP connection to communicate with your IoT devices, a possible workaround is react-native-tcp-socket, it allows you to bind your socket to an specific interface (ethernet, wifi, cellular, etc.) without forcing the whole app to use the WiFi connection.

Disclaimer: I am the creator and mantainer of react-native-tcp-socket

[eliaslecomte]

Yes it should be fixed.

What’s the code you are currently using?

try {
  await WifiManager.connectToProtectedSSID(ssid, password, false);
  await WifiManager.forceWifiUsage(true)
  // execute api calls here
} finally {
  await WifiManager.forceWifiUsage(false))
}