2022 Release Notes

MaaS360 product release notes for 2022

Android Release Summaries

Android 7.90 Release Summary

MaaS360 makes the Android app version 7.90 beta available in Play Store on 6th June 2022.

Configure background apps for Android Kiosk mode >>

When a device is locked to single app or multi-app kiosk mode, you can specify a list of apps that are allowed to run in the background. These background apps are hidden from the Kiosk home screen and users cannot interact with them. Kiosk apps can invoke these background apps to execute custom system functions. For example, you can add Android System WebView as a background app to render web content on some Android devices.

Note: Supported only for Android Enterprise devices.

All MaaS360 apps are now compliant with Android 12 >>

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

Behavior changes

  • Special permission required to set exact alarms - Exact alarms schedule an alarm to be delivered precisely at the stated time. MaaS360 uses exact alarms to perform time-sensitive actions such as Out of Compliance Timer, Calendar/Task reminders, and Selective Wipe on inactivity. Apps that target Android 12 must have the SCHEDULE_EXACT_ALARM permission in order to set exact alarms. The apps that have SCHEDULE_EXACT_ALARM permission can access Alarms & reminders capability that appears within the Special app access screen in system settings. This permission is auto-granted to apps on new enrollments or upgrade to MaaS360 app version 7.90. However, both users and system can revoke Alarms & reminders special app access. If the Alarms & Reminders access is revoked, the app stops functioning and all future exact alarms are cancelled.
  • Support for new Bluetooth permissions to use Bluetooth features - Apps that target Android 12 must use the new dynamic permissions BLUETOOTH_SCAN, BLUETOOTH_ADVERTISE and BLUETOOTH_CONNECT to access Bluetooth functionality. To grant the new Bluetooth permissions, users must allow the app to access Nearby devices. This permission is not granted by default. Users must grant the Nearby devices permission on the device to allow the device to discover and connect to nearby Bluetooth devices. MaaS360 app needs this permission to collect peripheral device data.
  • Passcode length & Quality cannot be set for profile owners anymore - In the previous releases, the passcode settings: Minimum Passcode Quality and Minimum Passcode Length were deprecated for Android 12+ Profile Owner (PO) devices in favor of Minimum Password Complexity, but administrators were allowed to push deprecated policies to the devices. The deprecated policy settings: Minimum Passcode Quality and Minimum Passcode Length are no longer supported on Profile Owner (PO) devices when they enroll with or upgrade to MaaS360 for Android app version 7.90+. Administrators must use Minimum Password Complexity to set passcode settings on PO devices running MaaS360 for Android app version 7.90+.

Control notification permission for managed apps through Security policies >>

Android 13 introduces a new runtime notification permission, allowing users to focus on the notifications that are most important to them. Apps that are installed on Android 13 will now request the notification permission from the user before posting notifications. Effective 10.86, MaaS360 makes it easier for administrators to control notification permission through Security policies. Administrators can use Android Enterprise policies to automatically grant notification permission to the managed Google Play apps, and also to block apps that use the notification permission on managed devices.

Note: Supported only for Android Enterprise devices.

Google Play app management enhancements >>

  • Granular instant installation options - MaaS360 adds new granular instant installation options for Google Play apps - Install once and Retry installation. These options are available in the Add app workflow and the App Summary page. Instant once is the default option for the existing apps that have the Instant Installation option selected. Both the options install the app on devices automatically.
  • New granular installation state for the Install once option - When an app is distributed with the Install once option, the Status is changed to Distributed and State is changed to App Available with auto install once setting in the App Distribution page.
  • Support for asynchronous API for better management of apps - In the previous releases, MaaS360 used different synchronous APIs for various app management tasks, which caused issues in app config distribution and app distribution. Effective 10.86, MaaS360 moves to the newer Google API (asynchronous), wherein all those tasks are performed by a single API and thereby reducing the delays occurring across app config and app distributions.
  • Removed deep link support for app installation - Users can no longer use deep links to install apps directly from the Play Store.

Added My Device section in Android Kiosk mode >>

MaaS360 adds the My Device section to allow users to view device related information such as Device ID directly in the kiosk mode. In previous releases, if MaaS360 app was not added to the kiosk launcher, users had to exit the kiosk mode and access the device related information from the MaaS360 app.

Defect Fixes

Defect #
44831 When a config file without an extension was pushed to internal device storage through Docs, MaaS360 automatically added a .unknown file extension. As a result, third-party apps were unable to read the file.
44788 Remote device enrollment via Experitest was unsuccessful, and a blank screen was displayed when the MaaS360 app was launched from the Work profile.
44704 The runtime permissions configured through Android MDM policies were not applied to the DO devices.
44702 Android device users did not receive email notifications for Exchange favorite contacts.
44506 Secure Mail attachments could not be opened/imported into a third-party app called Secure ID.
44296 The firewall policy settings are not applied to Samsung devices that are enrolled in Device Admin mode.
44277 After enrolling the Pixel 6 Pro device in Android Enterprise mode, the MaaS360 agent failed to report the Device Enrollment Mode information to the MaaS360 portal.
44244  Attachments in Outlook did not open with Secure Viewer on devices enrolled in DO mode.