IBM MaaS360

IBM MaaS360

Join this online user group to communicate across Security product users and IBM experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only

Kiosk Mode Unexpected Exit? Here’s Why It Happens and How to Resolve It

By Sweta Kumari posted 16 hours ago

  

Authors: @Sweta Kumari and @Preethi T M

Kiosk Mode Unexpected Exit? Here’s Why It Happens and How to Resolve It

Introduction

Android Kiosk mode is a feature that allows IT admins to block unwanted apps and websites, restrict device access and lockdown Android devices only to run approved apps and websites. By enabling Kiosk, the device can be controlled to use single app or multiple apps. This mode is heavily used by admin to manage frontline workers.

A device can exit kiosk mode intentionally through a policy change, an admin action, or in some cases, by the user (if the configuration allows it). However, in real-world situations, a device may sometimes exit out of kiosk mode due to unexpected system events, app crashes, or configuration conflicts. When this happens, both the user and the admin expect the device to stay locked, but it ends up returning to a normal state. To help identify and fix such issues, the MaaS360 Agent continuously sends detailed kiosk status updates to the MaaS360 Portal. These granular status indicators allow the admin to clearly see why the device went out of kiosk mode—whether it was due to a policy mismatch, network failure, forced reboot, or any other trigger. By reviewing these insights, the admin can quickly analyze the root cause and take corrective actions to restore kiosk mode, ensuring a seamless and controlled user experience.

Admin View: Device Kiosk Mode Status

The admin can view the Kiosk Mode status of a device directly within the Device View, as shown in the screenshot below.

A screenshot of a computer AI-generated content may be incorrect.

Kiosk Mode — Advanced Device Filtering for Admins

The screenshot below illustrates the section in the MaaS360 Portal where admin can filter and search the device list based on the granular Kiosk Mode status.

A screenshot of a computer AI-generated content may be incorrect.

User View: Device Kiosk Mode Status

The user can view the Kiosk Mode status of a device by navigating to MaaS360 Agent → Settings → Kiosk settings.

             Screens screenshot of a phone AI-generated content may be incorrect.

Troubleshooting Kiosk Mode: Status Insights and Resolution Steps

The table below lists all the granular kiosk mode status reported by the device, along with the possible causes for exiting kiosk mode and the recommended troubleshooting steps to resolve each issue.

Kiosk Mode Status on Portal

Kiosk Mode Status on Agent UI

Possible Causes

Troubleshooting Fix

Exited: Via Admin action

Kiosk is exited by admin via portal action

Admin has manually applied “Exit Kiosk” action to the device from MaaS360 portal to take the device out of kiosk mode.

User can contact admin.

Exited: Via Password

Kiosk is exited by user via password

User has exited kiosk manually via admin bypass passcode.

Admin can check with the user.

Exited

The admin has intentionally disabled the kiosk policy from MaaS360 portal, allowing the device to operate in normal mode.

User can contact admin.

Error: Pending Enablement

Failed to initialize. Turn on accessibility setting and retry.

This issue occurs when Kiosk Mode is enabled but the required Accessibility Service gets disabled due to a system event, OS optimization, manual change, or device reset. Since the accessibility permission is necessary for enforcing kiosk restrictions, the kiosk launcher fails to initialize correctly.

1.Go to Settings → Accessibility on the device.

2. Locate the MaaS360 Launcher Accessibility Service.

3.Enable the Accessibility permission again.

4. Retry enable kiosk

Download queued

Downloading Kiosk app

MaaS360 Launcher APK download is in progress and got stuck due to network interruption or slow/unavailable internet.

Ensure the device has a stable internet connection, then Retry Enable Kiosk.

Not Available

Kiosk payloads are either not sent yet or not processed by the portal.

Check the device’s internet connectivity. Then either the admin can perform “Request Data Refresh” from the portal, or the user can tap “Update Device Data” from MaaS360 Settings on the device to resend the payload.

Device provisioning pending

Device is not provisioned

The device is not provisioned, so kiosk mode cannot be enabled.

Ensure device is provisioned successfully and then retry enabling kiosk.

Error: Download failed

Kiosk app download failed

The kiosk APK could not be downloaded due to a network or server error.

Check internet and server reachability → Retry Enable Kiosk.

Pending Enablement

Initializing set up / Failed to initialize

Kiosk failed to initialize because the required Accessibility setting is turned OFF.

Ask the user to turn ON the Accessibility setting for the MaaS360 Launcher app and retry enabling kiosk.

Error: Kiosk Mode type Empty

Kiosk mode unknown

Error in policy parsing between the Agent and the MaaS360 Launcher app, likely due to policy data corruption.

Try re-enabling kiosk by uninstalling the MaaS360 app once and then re-applying the kiosk policy from MaaS360 portal.

Error: Agent data refresh failed

Unable to parse Agent data. Possible data corruption.

Error: Policy disabled

Unable to parse Policy. Possible data corruption.

Error: Apply policy failed

Unable to apply policy.

Error: Pre-conditions failed

Activation failed due to non-compliance. Pre-conditions not fulfilled.

Error: Download cancelled

Kiosk app download cancelled by user

User manually canceled the MaaS360 Launcher app download.

Retry Enable Kiosk and ask the user not to interrupt or cancel the MaaS360 Launcher app download.

Error: Installation failed

Kiosk app installation failed due to an error

Possible version conflict — an existing MaaS360 Launcher may already be installed.

Check if MaaS360 Launcher is installed. If it is present, uninstall it and then retry enabling kiosk.

Not installed

Installing Kiosk

Unpinning pending

Removing lock task mode

Right after device enrollment, the Agent app may still be in lock task mode and not yet unpinned, which can prevent kiosk mode from being enabled.

Reboot the device, disable the kiosk policy, wait for the lock task mode to clear, and then enable the kiosk policy again.

Error: Unpinning pending

Unable to remove lock task mode.

Error: Not installed

Kiosk is not installed on device.

The MaaS360 Launcher app may have been manually uninstalled from the device.

Ask the user to enable kiosk manually by going to MaaS360 > Settings > Kiosk Settings.

Error: Activation failed

Kiosk activation failed

The MaaS360 SDK activation may have failed during kiosk app initialization.

Option 1: Try rebooting the device.

Option 2: Ask the user to uninstall the MaaS360 Launcher app from the device, then try enabling kiosk again.

Allowlisted applications not installed

Allowlisted applications are not installed on device.

If the policy is set to “Once any allowed app is installed”, the device won’t enter Kiosk Mode if no whitelisted apps are installed or will exit Kiosk Mode if all whitelisted apps are removed.

Verify if admin has removed all the whitelisted applications from app catalog or user has manually uninstalled all of the whitelisted applications. Ensure at-least one of the whitelisted applications is installed on the device and then try enable kiosk again.

Exited: Allowlisted applications uninstalled

Kiosk is exited due to non-compliance. Required application may have been uninstalled.

Not Applicable

·       Kiosk policy is not valid.

·       Kiosk mode type could be empty.

·       No whitelisted app is installed when "Set device to Kiosk mode" is set to "Once any allowed app is installed"

·       Check the kiosk policy.

·       Kiosk mode type should not be empty.

·       One of the whitelisted applications is installed on the device if "Set device to Kiosk mode" is set to "Once any allowed app is installed" in the kiosk policy.

Error: Fetching kiosk information failed

Gathering Kiosk information failed

MaaS360 Agent failed to receive MaaS360 Launcher APK information.

The admin can perform a Request Device Refresh action, or the user can select Update Device Data in the MaaS360 Agent Settings. Then, try enabling Kiosk Mode again.

Launcher not set

Setting up Kiosk as default launcher

·       Device fails to set MaaS360 Launcher as default Launcher.

·       User has manually removed MaaS360 Launcher as default launcher.

Ask user to set MaaS360 Launcher as default Launcher from device settings.

Error: Enablement failed

Unable to set up Kiosk

Error: Launcher not set

Unable to set Kiosk as default launcher

Proactive Tips for Preventing Kiosk Mode Issues

1.    Stable Connectivity: Ensure devices have a reliable Wi-Fi connection during policy deployment and updates.

2.    Battery Optimization: Exclude the MaaS360 agent from battery optimization settings to prevent the OS from killing its background processes.

3.    Regular Agent and kiosk Updates: Keep the MaaS360 agent and MaaS360 Launcher app updated to the latest version to benefit from bug fixes and compatibility improvements.

4.    Pre-Deployment Testing: Always test new kiosk policies on a small group of devices before rolling them out to your entire fleet.

Conclusion

By understanding the granular kiosk status and their associated causes, administrators can quickly pinpoint the root of the issue and take effective corrective actions.

Following the proactive best practices—such as maintaining stable connectivity, excluding MaaS360 from battery optimization, keeping agent and launcher apps updated, and testing kiosk policies before deployment—can significantly reduce the chances of kiosk failures.

Ultimately, consistent monitoring of kiosk status from the MaaS360 portal ensures device compliance, stability, and a seamless end-user experience across your managed device fleet.

1 comment
14 views

Permalink

https://community.ibm.com/community/user/blogs/sweta-kumari/2025/11/20/kiosk-mode-unexpected-exit-here-why-it-happens

Comments

Satyaa Kumbhar
14 hours ago

Kiosk Mode issues can be tricky, and this guide does a solid job connecting each status to the exact cause and fix, something admins usually struggle with. The dual visibility from both the admin and user side is especially helpful.


The proactive tips around connectivity, battery optimization, and policy testing are spot-on too. Overall, a super useful reference for anyone managing Android devices in kiosk mode. Thanks for sharing!