Wifi Access Point Mode - HttpListener hangs

[Alex-111]

Target name(s)

ESP32-S3 DevkitC-1

Firmware version

latest - 1.8.1.370 ESP32-S3

Was working before? On which version?

No response

Device capabilities

No response

Description

When setting up a SoftAP the HttpListener sometimes does not accept any new requests.

How to reproduce

I started with the provided sample code "WifiAP" and would like to setup a simple Wifi Access Point with a very basic webserver. I tested with my Android phone to connect to the SSID and via Browser I requested http://192.168.4.1. The first request seems to work...

But especialy, when I connect my Smartphone to another SSID and then return back to my nanoFramework AP, no requests are accepted anymore and the browser just hangs.

It just seems that the socket listener just does not return anymore.

Here is my smaple code: https://github.com/Alex-111/WiFiAPTest/tree/master

Expected behaviour

I would expect that HttpListener always accepts webrequests,regardless if I connect my Smartphone to another WIFI and then later connect it again to the SoftAP.

Screenshots

No response

Aditional information

No response

[josesimoes]

@Ellerbach wondering if this is somewhat related (or similar) with the fix you've made the other day on the webserver...

[Ellerbach]

I tested the code and it works as expected for me:
First request, I open a browser and went to the 192.168.4.1 page.
Then I connected to another SSDI
Then I connected back to the MySsid
Then went again to the page:

[Ellerbach]

I've been repeating multiple times with different processes (closing the browser before leaving, leaving it open, refresh, etc), it always worked as expected.
So closing this issue. This may be due to the browser, phone specific.

[Alex-111]

@Ellerbach Thanks for testing!

Please could you tell me more about your setup:
What firmware do you use? What device do you use? Maybe it is specific to a special device/firmware combination?

[alberk8]

I have the same issue as @Alex-111 and I am using Android Phone.

[Alex-111]

@josesimoes As more peaple have this issue I think we should investigate a little bit more before closing the issue?

[josesimoes]

@Alex-111 : @Ellerbach owns this issue, up to him. 😉