-
Notifications
You must be signed in to change notification settings - Fork 7.3k
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
iPhone can't connect to wifi server in AP mode #2536
Comments
Here's what happens with 1.0.1:
This is the stack trace decoded:
So probably not really saying much, but the console output does demonstrate that network activity occurred. |
Is this related to espressif/esp-idf#2915? |
Looks like I closed it by mistake! |
@judge2005 looks like the line that exploded is Wifigeneric.cpp:342 if(event->event_id < 26) log_d("Event: %d - %s", event->event_id, system_event_names[event->event_id]); base on the crash error, it looks like #if ARDUHAL_LOG_LEVEL >= ARDUHAL_LOG_LEVEL_DEBUG
const char * system_event_names[] = { "WIFI_READY", "SCAN_DONE", "STA_START", "STA_STOP",
"STA_CONNECTED", "STA_DISCONNECTED", "STA_AUTHMODE_CHANGE", "STA_GOT_IP",
"STA_LOST_IP", "STA_WPS_ER_SUCCESS", "STA_WPS_ER_FAILED", "STA_WPS_ER_TIMEOUT",
"STA_WPS_ER_PIN","AP_START", "AP_STOP", "AP_STACONNECTED",
"AP_STADISCONNECTED", "AP_STAIPASSIGNED", "AP_PROBEREQRECVED", "GOT_IP6",
"ETH_START", "ETH_STOP", "ETH_CONNECTED", "ETH_DISCONNECTED",
"ETH_GOT_IP", "MAX"};
#endif Chuck. |
That was on v1.0.1, which doesn't have any range checking there at all. I added +ve and -ve range checking, the result is that there is nothing printed to the console with this version after:
|
Talk about timing. The latest build works fine, other than the Pico refuses to start up properly on power-on. Closing... |
Hardware:
Board: ESP32-PICO-KIT V4
Core Installation version: master
IDE name: Sloeber
Flash Frequency: ?
PSRAM enabled: ?
Upload Speed: 115200
Computer OS: Windows 10
Description:
I'm using AsyncWifiManager to handle setting up an AP and a captive portal. I am finding that an iPhone is only occasionally redirected to the captive portal. The problem seems to lie with DNS requests - I hve instrumented both DNServer and WiFiUDP. In the cases where connection is established, DNServer responds to a DNS request. In the case where it doesn't, no DNS request is registered. However, I was getting the following printed out in the console when I attempted to connect to the AP (whether or not it succeeded):
E (22491) event: mismatch or invalid event, id=63
E (22491) event: default event handler failed!
So it seems that the iPhone was actually sending a request of some sort.
I updated to the latest (i.e. master) as of March 2, 2019. The event errors go away, but the problem doesn't.
Sketch:
Debug Messages:
The text was updated successfully, but these errors were encountered: