Starting wifi-connect on-boot or even manually and letting iOS and Android devices connect to the access point (AP) takes more than a minute for the captive portal login screen to appear on the device’s default browser. However, connecting to the AP via laptop or desktop computer experiences little to no-delay.
This is in reference to issue#279 on the balena wifi-connect repository.
Here’s the url: [https://github.com/balena-io/wifi-connect/issues/279].
As mentioned by @majorz, the application is written in Rust, therefore, it is compiled as native. I suspect that it has something to do with how mobile operating systems deal with captive portals in general and how wifi-connect currently doesn’t have a mechanism to deal with this.
Referencing one of @charliesneath’s research.
Here’s the url: [https://stackoverflow.com/questions/43897967/captive-portal-apple-devices-not-getting-automatic-browser-popup/43924110#43924110]
I am not really familiar with this, so I am asking help in locating where wifi-connect fulfills one of these rules, if not it would be great if you guys can point me to the right direction so I can modify it on my end. Thank you so much and any insight would be greatly appreciated.