Android 8.41/8.40 Release Notes

MaaS360 makes Android app version 8.41/8.40 available on Play Store on 04 January 2024.

Streamlined contact search with a clearer distinction between Local and Directory contacts >>

MaaS360 enhances contact search functionality in the MaaS360 for Android app, providing a clearer distinction between local and directory contacts. In the previous releases, all contacts were displayed together and users had to click the Load more link to view contacts from the server.

Now, when users select the new Search Global Address List checkbox, MaaS360 retrieves and displays local contacts in the Local Contacts section and contacts from the server in the Directory section. To initiate a search, users must enter a minimum of four characters. This improvement streamlines contact search and provides a more organized view of available contacts.

Configure the minimum OS version requirement for Android Enterprise enrollments >>

MaaS360 now allows administrators to set a minimum OS version requirement for Android Enterprise devices, ensuring that only devices running compatible OS versions are enrolled in MaaS360. When this setting is enabled, only devices running the specified OS version or higher will be able to enroll in MaaS360.

In the past, administrators had to set a minimum and maximum OS version range through Compliance Rules. However, the rule was applied only after a device was already enrolled, leading to delays in unenrolling the non-compliant devices. Users were unsure as to why the devices were unenrolled from MaaS360.

The new feature addresses those issues by validating the OS version up front. Devices that don't meet the minimum OS requirement will be blocked from enrolling in MaaS360, and users will receive a clear error message explaining the reason for the enrollment failure.

The path to the new setting: Setup > Settings > Advanced Enrollment Settings > Advanced Management for Android Devices > Set lowest Android OS version allowed for enrollment.

Important information regarding inactive Google accounts and Android Enterprise >>

Google has recently announced that they reserve the right to delete inactive Google Accounts and their associated data if an account remains inactive for at least two years. This policy applies to personal Google Accounts. Google has clarified that admin accounts associated with Android Enterprise administration are exempt from the inactive Google account policy.

You can follow the recommendations on this page to ensure that your Android Enterprise binding remains active and to avoid disruption to your device management activities.

Simplified sign-in and sign-out for shared kiosk devices >>

MaaS360 adds a new policy setting Show Sign in and Sign Out options for shared devices to streamline the sign-in and sign-out process for corporate shared devices that are enrolled in Device Owner mode. When this setting is enabled, users can seamlessly sign in and sign out directly in the kiosk launcher. In the previous releases, administrators had to add the MaaS360 app to the app allowlist in COSU policies. This enhancement eliminates the need for users to take the extra step of launching the MaaS360 app simply for authentication purposes.

Note:
  • Path to the new policy setting: Security > Policies > Android MDM policy > Android Enterprise Settings > COSU (Kiosk mode) > Kiosk Launcher Settings > Show Sign in and Sign Out options for shared devices.
  • This policy setting is available only in the kiosk multi-app mode. Meaning, that the Show custom Home page with allowed apps option should have been selected in the COSU Mode Type. This option is not available in single-app mode.
  • Other common shared device scenarios, such as policy assignment, app distribution, and app removal, will continue to function as usual.