JuanSeBestia/react-native-wifi-reborn

Not working on Expo - WifiManager is null

Closed this issue · 6 comments

Hello,

I have done a custom expo dev build however when trying to use the library I get the following error:

Imported via import WifiManager from "react-native-wifi-reborn";

ERROR [TypeError: Cannot read property 'connectToProtectedSSID' of null]

If i try to do console.log(WifiManager); I gett
LOG null

Any ideas on a solution would be great.

having the same issue.. did you find any solution?

having the same issue.. did you find any solution?

Not yet...
Let me know if you find a solution 😀

Hello,

I have done a custom expo dev build however when trying to use the library I get the following error:

Imported via import WifiManager from "react-native-wifi-reborn";

ERROR [TypeError: Cannot read property 'connectToProtectedSSID' of null]

If i try to do console.log(WifiManager); I gett LOG null

Any ideas on a solution would be great.

You need to go with react-native fully bare or try by ejecting from expo inside the expo surrounding i couldn't connect to hidden wifi or even to use the library just do a fully react-native bare project else eject from expo it helps.

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community attention? This issue may be closed if no further activity occurs.

Hello,
I have done a custom expo dev build however when trying to use the library I get the following error:
Imported via import WifiManager from "react-native-wifi-reborn";
ERROR [TypeError: Cannot read property 'connectToProtectedSSID' of null]
If i try to do console.log(WifiManager); I gett LOG null
Any ideas on a solution would be great.

You need to go with react-native fully bare or try by ejecting from expo inside the expo surrounding i couldn't connect to hidden wifi or even to use the library just do a fully react-native bare project else eject from expo it helps.

I am using a custom expo dev build - this shouldnt be a problem

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community attention? This issue may be closed if no further activity occurs.

not stale