Closed grasmash closed 9 months ago
Hmm do you mean it gets stuck? Could you try the Espressif sample app? Because our code for provisioning:
self.espDevices[deviceName]!.provision(ssid: ssid, passPhrase: passphrase, completionHandler: { status in
// Prevent multiple callback invokation error
guard !invoked else { return }
switch status {
case .success:
resolve([
"status": "success"
])
invoked = true
case .failure(let error):
reject("error", error.description, nil)
invoked = true
case .configApplied:
break
}
})
Is pretty similar to the code called in the ESP sample app for iOS:
Yes, the call gets stuck, although I can see by monitoring the ESP that the credentials are sent as expected. However, the call just hangs and doesn’t proceed to the next line.
I can try out the sample app and see if I encounter the same behavior.
Tried the sample app. It hangs at "Confirming Wi-Fi connection" for 10+ minutes with this output:
Opened and upstream issue: https://github.com/espressif/esp-idf-provisioning-ios/issues/77
Closing as this is an upstream issue.
const espResponse = await device.provision(ssid, password);
never resolves, whether there is an error or success. It does send the credentials.