Android kiosk Flutter app shows “failed host lookup” while other apps have internetSolved

The “failed host lookup” error occurring exclusively within one app—while system apps like Google Chrome work perfectly—indicates that the device network is healthy, but the specific app lacks the authority to use it.

Even if a device is managed or locked down via Hexnode MDM, an app cannot bypass Android’s native security framework. For a Flutter/Android app to access network resources, it must explicitly request permission in its source code.

The app’s source code must be updated and rebuilt with the proper network permissions:

1. Open the Flutter project’s Android source files and locate the AndroidManifest.xml file (typically found in android/app/src/main/AndroidManifest.xml).

2. Add the following internet permission tag inside the <manifest> tag, but outside the <application> tag:

3. Rebuild the APK and distribute the updated version via the Hexnode console.

If an app fails both inside and outside of Kiosk Mode, the issue is code-related (as detailed above). However, if the app fails only when Kiosk Mode is active, Hexnode may be blocking background processes the app relies on.

To verify if Hexnode is blocking any app packages, use the following verified workflow:

Step 1: Scan for Blocked Packages

1. In the Hexnode console, go to Manage and select the affected Android device.

2. Click Actions > Scan Device.

3. Once the scan completes (verified via Action History), navigate to the Applications tab on the device summary page and check the Blocked Packages list.

Step 2: Allow the App in the Background

If the app or its dependencies appear as blocked packages, they must be whitelisted within the Kiosk policy:

1. Go to Apps > Add Apps > Upload as Bundle ID.

2. Add the blocked app package name as a bundle ID.

3. Open the applied Kiosk policy, navigate to Android > Kiosk Lockdown > Background Apps, and add the bundle ID there.

4. Save and publish the policy.

Regards,
Mary Romero