We have an app from the Google Play store that we want to be the only app that the end user has access to.  In MaaS360 I setup a policy with Kiosk mode enabled, set it to automatically launch the app and display only the app, and put in the correct app ID.  The time after app launches automatically was not set.

When the policy applied, it looked like the app just kept re-spawning.  I then set the time after app launches to 5 seconds- what happens then is that I see the MaaS360 background with a 5 second countdown.  Once the countdown expires, the app launches but then goes back to the background with the countdown timer.  It just keeps looping- is there a setting I missed somewhere?  The app runs fine on its own.

------------------------------
Chad Martin
------------------------------

Hi Chad 

For Android devices there is a piece of middleware called the MaaS360 App Launcher which is not on the Play Store but which needs to be allow-listed in App Compliance in order for Kiosk/COSU to run correctly. 

App ID: com.fiberlink.maas360.android.launcher

Please update this in the policy, make sure the device gets the new policy version, and restart the device and test. 

Please let me know how you get on. 

Best

------------------------------
Eamonn O'Mahony
Client Success Manager
IBM Security
Dublin
------------------------------

Wow- thank you so much, Eamonn!  I guess I just automatically assumed that the launcher would be automatically approved since it is part of MaaS360... All is right with the world now :)

------------------------------
Chad Martin
------------------------------

Original Message:
Sent: Fri November 15, 2024 07:00 AM
From: Eamonn O'Mahony
Subject: Kiosk Mode with Forced App Looping

Hi Chad 

For Android devices there is a piece of middleware called the MaaS360 App Launcher which is not on the Play Store but which needs to be allow-listed in App Compliance in order for Kiosk/COSU to run correctly. 

App ID: com.fiberlink.maas360.android.launcher

Please update this in the policy, make sure the device gets the new policy version, and restart the device and test. 

Please let me know how you get on. 

Best

------------------------------
Eamonn O'Mahony
Client Success Manager
IBM Security
Dublin
------------------------------

Hi Chad

Have noted this for feedback. Am glad to hear it's working again.

Best regards

------------------------------
Eamonn O'Mahony
Client Success Manager
IBM Security
Dublin
------------------------------

Original Message:
Sent: Sat November 16, 2024 01:57 PM
From: Chad Martin
Subject: Kiosk Mode with Forced App Looping

Wow- thank you so much, Eamonn!  I guess I just automatically assumed that the launcher would be automatically approved since it is part of MaaS360... All is right with the world now :)

------------------------------
Chad Martin
------------------------------


Original Message:
Sent: Fri November 15, 2024 07:00 AM
From: Eamonn O'Mahony
Subject: Kiosk Mode with Forced App Looping

Hi Chad 

For Android devices there is a piece of middleware called the MaaS360 App Launcher which is not on the Play Store but which needs to be allow-listed in App Compliance in order for Kiosk/COSU to run correctly. 

App ID: com.fiberlink.maas360.android.launcher

Please update this in the policy, make sure the device gets the new policy version, and restart the device and test. 

Please let me know how you get on. 

Best

------------------------------
Eamonn O'Mahony
Client Success Manager
IBM Security
Dublin