Google Messages stuck in “Almost There” setup loop on Android in kiosk modeSolved

Hello @merlynn ,

This behavior can occur if Google Messages depends on supporting packages that are blocked by kiosk restrictions, or if the app is unable to register its required runtime permissions correctly.

A good first check is whether any packages are being blocked while the app launches:

1. Run a Scan device action for the affected Android device.
2. Open the device in Hexnode UEM and go to the Applications section.
3. Check the Blocked Packages list.
4. If a package related to Messages or its required services is listed, add it to Hexnode UEM using its package name or bundle ID.
5. In the kiosk policy, go to Android Kiosk Lockdown > Background Apps and add the required package there.
6. Save and reapply the policy.

Also confirm that Google Messages is configured as the default SMS app if your workflow requires it. For SMS apps, the default app role is often required in addition to standard app permissions.

I found a blocked package and added it using the package name, then added it as a background app in the Android kiosk policy. The policy saved correctly, but Google Messages still gets stuck on the same “Almost There” screen.

I also exited kiosk mode completely on one device and tested again, but it still opens Settings and loops back to the setup screen.

If the same loop occurs even when the device is outside kiosk mode, it usually indicates that the kiosk policy is not the component blocking Google Messages.

In this case, the likely cause is the Google Messages setup flow failing at the device or OS layer. The app requires core access such as SMS, Phone, and Contacts, and the “Almost There” screen appears when it cannot complete that initial permission/default-app handshake.

The following checks are still worth trying:

• Make sure Google Messages is fully updated.
• Force stop Google Messages.
• Clear the app cache from Android Settings > Apps > Messages > Storage & cache.
• If messages are backed up or not needed, clear app storage as well.
• Push the required app permissions through Hexnode App Permissions policy.
• Confirm Google Messages is selected as the default SMS app in Android Settings and in the applicable Hexnode restriction policy.

If the issue persists after these steps and also happens outside kiosk mode, it points more toward a compatibility issue between that Google Messages build and the device’s Android 14 framework rather than a Hexnode restriction.

Using an alternate SMS app is a valid workaround when Google Messages cannot complete its setup flow on specific Android 14 device builds.

Regards,
Simon Scott
Hexnode UEM