Android 8.50 Release Notes

MaaS360 makes the Android app version 8.50 available on the Play Store on 25 March 2024.

Support for Zebra Android 13 devices and later

In this release, administrators can use these actions with Android Agent 8.50 for Zebra Android 13 devices and later.

For more information, see the Push Profile actions to manage Zebra and Bluebird devices section.

MaaS360 is compatible with Zebra Android 13 devices and later.

The new app Zebra OEMConfig powered by MX (Android 11 and above) has been added to the MaaS360 portal to support Zebra OEM config for Android 11 and later versions. This new app adheres to Google’s policy, ensuring that only one policy is published on the device. It supports for Google’s feedback channel. MaaS360 offers support for the new Zebra OEM.

For more information, https://www.ibm.com/docs/en/maas360?topic=security-using-oemconfig-apps-apply-advanced-device-configuration-policies-in-maas360.

MaaS360 now adopts all the latest API changes for Android 14

MaaS360 is now compatible with Android 14 and adopts all the behavior changes related to Android 14.

Supports device enrollment as part of device provisioning by default >>

Previously, administrators manually configured additional attribute, such as force_enrollment_before_provisioning, to enroll devices before device provisioning for DO enrollments. https://www.ibm.com/support/pages/node/6841251.

• To enroll after device setup, the additional attribute force_enrollment_before_provisioning must be set to NO when creating the enrollment configuration for QRcode, KME, and Zero-Touch enrollments.
• For token-based enrollments, users will always enroll the device before device provisioning, as there is no option to set the force_enrollment_before_provisioning configuration to NO.
• Impact on COSU devices for DO enrollments: The new state Device Provisioning Pending is displayed on the Device summary page in the MaaS360 portal when the user enrolls before device provisioning, and Kiosk is set as the default policy if the device setup is in progress after completing enrollment.

  For more information, see https://www.ibm.com/support/pages/node/7023191.

Introduction of new option to view more details to troubleshoot enrollment issues >>

Administrators require device details along with logs to troubleshoot enrollment issues quickly. If the device is locked during enrollment, users are unable to share logs with the required details for administrators to troubleshoot, which is more essential for non-GMS or dedicated devices.

For example, if the device is locked during enrollment, Bluetooth is not set up, making it difficult for users to share logs.

MaaS360 introduces the new View details option to view error details and share the necessary details with the administrator to resolve the issue.

The View details option allows users to view error details such as the error description, device ID, account ID used for enrollment, and corporate ID of the account, which can be used to troubleshoot issues encountered during enrollment.

Enhancements in Kiosk Launcher UI for ease of access to Kiosk Settings >>

Previously, the corporate settings were removed from the device when a device was selectively wiped due to being out of compliance. The enable Kiosk option is inside corporate settings, so the user cannot enable it to resolve the device's out-of-compliance.

In this release, to resolve this, MaaS360 introduces the new screen Kiosk Settings for more visibility and to allow users to enable Kiosk from the device. It also helps users to apply the rules when the device is not in Kiosk mode and is out of compliance.

For example, in cases where a device is out of compliance and selective wiping is required due to the disabled Kiosk, Kiosk Settings is now out of the Corporate Settings and available after the wipe. Users can enable it to address compliance issues and see the process's status.

Additionally, users can view detailed status and associated information on the status indicator in the Kiosk Settings.

Automatically allow all apps from the App Catalog in Kiosk for multiple app mode >>

MaaS360 introduces the new Allow all apps from app catalog policy, which automatically allows all apps from the App Catalog to be used in the Kiosk without adding them individually to the App IDs for the allowed Apps policy for each app. The apps from the App Catalog distributed and installed on the devices are displayed in the Kiosk.

Support to update device data from Kiosk Launcher settings >>

Users were unable to get the automatic app updates and must wait until the client/server sync occurs successfully. These updates had to be done through the MaaS360 core app, which was not allowed in the Kiosk Launcher.

Previously, users must exit Kiosk mode to update device data.

In this release, MaaS360 introduces the new Update Device Data option for updating device data without exiting Kiosk mode. It enables users to manually take control and trigger connecting from Kiosk Launcher settings to update device data.

Users can tap this option in the Kiosk settings to establish the connection and manually request device data updates from the Kiosk.

Support to allow/disallow all apps from the App Catalog in App Compliance >>

Previously, apps distributed from the App Catalog were allowed by default in the App Compliance. Configured Allowed Apps is an existing policy setting. This setting only applies to apps installed by users.

In this release, MaaS360 introduces the new Allow all apps from app catalog policy, where administrators can control and allow/disallow all apps from the App Catalog based on this policy.