Introducing AirWatch Launcher 4.0 for Android

The VMware Workspace ONE Team is excited to announce that AirWatch Launcher 4.0 for Android is publicly available.

What’s New in this App Version

  • ALAU-170034: Support for Android Corporate-Owned, Single-Use (COSU) setup for all Launcher modes.
  • ALAU-170027: Configure floating home button for Multi App mode and Template mode.
  • ALAU-170031: Display large wallpaper in Multi App mode. (Requires AirWatch Console 9.3+)
  • ALAU-170069: Display localized application names as per device language settings on Launcher Multi App mode.
  • ALAU-170116: Configure Launcher in work managed mode without COSU

Bugs Fixed in this App Version

  • ALAU-169281: Resolved issue with “Invalid profile error” when username and organization group name incudes upper case character.
  • ALAU-169957: Resolved issue with App Compact crash.
  • ALAU-170051: Resolved an issue where Launcher screen goes blank after AirWatch Agent upgrade until home button is clicked.
  • ALAU-170039: Resolved issue where changes made to Bookmarks profile are not reflecting in Launcher after reading the edited bookmarks.
  • ALAU-169898: Resolved issues with receiving Launcher profile through Service from the AirWatch Agent
  • ALAU-170094: Resolved issue with ‘Out of memory’ exception error.
  • ALAU-170056: Resolved issue where widget prompts are blocked on Sony devices.

Customer Impact

Take advantage of these updates by meeting the minimum requirements and downloading AirWatch Launcher 4.0 for Android.

Minimum Requirements

  • Android 4.0+
  • AirWatch Admin Console 9.1+
  • AirWatch Agent 8.1+ for Android

Impact of COSU APIs for Android Enterprise (AFW) Customers

Corporate-Owned Single-Use (COSU) is the new standard method to implement a Launcher/Kiosk use-case for Work-Managed devices as per Google recommended standards. This new method of the Launcher configuration on the device has several distinct advantages, but does come with several caveats.

Advantages of COSU:

  • It is the Google recommended approach, and will be better maintained and updated moving forward.
  • More security with fewer ways for users to exit the Launcher.
  • Automatic configuration so that users no longer need to select Launcher as the default.

Caveats of COSU:

  • Native Notification/Status Bar is blocked in COSU mode for security reasons, customers will need to use the Launcher Notification area to provide notifications to end users.
  • Soft-keys such as Back, Home, and Recent Tasks are blocked in COSU mode for security reasons. End users can use the newly developed customizable floating home button to return from an application to the Launcher screen.
    • The Recent Tasks option still remains in the Launcher profile on the console and will not work due to COSU blocking it on the device. AirWatch is working on restoring functionality of this option in the future through another mechanism.

How to Download AirWatch Launcher 4.0 for Android

Prior Version is Installed – The admin can decide when to push the app once it is available on the AirWatch Console as a seeded application.

  • For devices that support silent install of applications, the Launcher application seamlessly updates over the existing application version without disrupting device enterprise functionality. For devices that do not support silent install of applications, users are prompted to install the new version.
  • For Android Marshmallow and above, the user is prompted to grant permission for the Launcher to have access to the Usage Data, if they have not already granted the permissions.
  • For Android Lollipop, users are prompted to grant permissions for Launcher to have access to Usage Data only if the admin has pushed a profile requiring the user to do so (more details present in previous technical bulletins).

Prior Version is Not Installed –  Once the admin decides to push the AirWatch Launcher to the devices, the Launcher gets downloaded to the device as a seeded application.

  • For Samsung SAFE devices, Launcher is setup without any end user interaction and the native launcher is replaced by AirWatch Launcher. For non-SAFE devices, the user is directed through a two-step process to set the AirWatch Launcher as the default Launcher.
  • For Android Marshmallow and above, the user is prompted to grant permission for the Launcher to have access to the Usage Data, if they have not already granted the permissions.
  • For Android Lollipop, users are prompted to grant permissions for Launcher to have access to Usage Data only if the admin has pushed a profile requiring the user to do so (more details present in previous technical bulletins).

Support Contact Information

To receive support, either submit a ticket via the My Workspace ONE portal or call your local support line.

 

Best Regards,

The VMware Workspace ONE Team

 

Other Languages: 日本語

Have more questions? Submit a request

0 Comments

Article is closed for comments.