Android 13 kiosk devices not showing captive portal Wi-Fi login popupSolved

Hello,

Thanks for reaching out to Hexnode Connect.

This behavior is typically seen when Android’s native captive portal components are blocked from running in the background while the device is locked in kiosk mode.

Android 13 handles unauthenticated captive portals much more restrictively than older versions like Android 11. In a managed kiosk environment, the newer OS will treat captive portal redirects or login overlays as restricted unless the required system processes are explicitly allowed to run. (Android 11 devices may still show the popup without these explicitly allowed, depending heavily on the specific OEM implementation).

To resolve this, you need to whitelist the native Android captive portal-related system apps as background apps within your kiosk policy.

Here is how you can configure this:

1. Navigate to Policies > Kiosk Lockdown > Android Kiosk Lockdown > Multi-App > Background Apps.
2. Click on Add Apps and add the Android captive portal login component.

   (Note: If it is not listed as a regular app, use the Add by Bundle ID option. The bundle ID is typically com.android.captiveportallogin or com.google.android.captiveportallogin. Depending on the device, the system HTML viewer com.android.htmlviewer may also be required for the overlay to render).

3. Save the changes and associate the updated policy with a test Android 13 device.
4. Reconnect to the Wi-Fi network to verify that the captive portal login page successfully appears.

By whitelisting these specific system components, you allow the OS to trigger and render the Wi-Fi sign-in popup while keeping your other kiosk restrictions intact.

I hope this helps. If you find any more issues or need further assistance feel free to reach out.

Best regards,
George,
Hexnode UEM