Open mirabo-trunghoang opened 5 months ago
@mirabo-trunghoang
React Native WifiManager.connectToProtectedSSID()
calls NEHotspotConfigurationManager
internally.
I found NEHotspotConfigurationManager issue that may be helpful for your issue.
Hi @simago
It seems the connection is not completely established after calling WifiManager.connectToProtectedSSID()
, then Theta function initialize()
would not have enough data to perform initialization, right?
Do you have any suggestions for us to handle this situation? How does the Theta mobile app (the official app) handle this?
Thanks for supporting.
@mirabo-trunghoang
I think there is a delay between the completion of WifiManager.connectToProtectedSSID()
and the completion of WiFi connection.
I could not find Theta application using WifiManager.connectToProtectedSSID()
.
@simago Yes, I'm just curious about how the Theta mobile app handles the connection. Regarding the connection not being fully established after calling the WifiManager function, I'm thinking of solving it by adding a delay (3 seconds) before calling the Theta initialization function, but it's also not guaranteed to work 100%.
When I call initialize(), sometimes it throws this error:
Note that the iPhone is connected to the Theta camera Wifi already, and if I tried to call this function several times, it was successful (maybe the second time or third time,...). Almost the time, it failed when trying to connect after the first time installing the app.
The code I implemented. I use WifiManager to connect to the Theta Wifi first then call initialize()
I know it may encounter some error when connecting but in the production, it seems not acceptable. Please help to figure out the season why this issue happens. Thanks.