-
Notifications
You must be signed in to change notification settings - Fork 7.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A bug when connecting to not-available endpoints #3056
Comments
A fix was merged recently that should address this. Can you update and check if it's still happening? |
I've tested with the latest release I could find on the Boards Manager - 1.0.3-rc1 and the issue still occurs Thanks for the quick response, |
Dont test with the latest release , test with master. |
Yeah I just tested with latest master and confirmed it is fixed now (and reproduced the error on 1.0.3-rc1). |
Ok, didn't know that. Thanks guys, I'm waiting for the next stable release. Gil. |
My hardware:
Node-MCU ESP32 was used, but I was able to reproduce with any esp32 module I had around me.
I am trying to connect to an endpoint which I know does not exist, however the method
WiFiClient.connect
returnstrue
(should befalse
). Then, any calls forsend
will crash the esp32.The code I'm using to reproduce is exactly the same as the sketch
WiFiClientBasic
:Notice that
client.connect(host, port)
returnstrue
, even tho the endpoint doesn't exist!The crash stacktrace (decoded):
The text was updated successfully, but these errors were encountered: