Introducing VMware AirWatch Launcher 3.0 for Android

The VMware AirWatch® team is excited to announce that AirWatch Launcher 3.0 for Android is publicly available.

What’s New in this App Version

  • ALAU-169700: Improved install flow to persist Launcher when deployed as a profile in a product (Requires AirWatch Agent 7.1 for Android)
  • ALAU-169077: Added ability to clear application data when doing check-in/check-out using the Custom Settings profile
  • RUGG-1595: View Launcher install status from the Security section of Device Details Page in the AirWatch Console (Requires AirWatch 9.1)
  • ALAU-169667: Dynamic whitelisting of activities of a package

 

Bugs Fixed in this App Version

  • ALAU-169797: Resolved issue with Launcher skipping the set passcode screen when using Shared Device mode.
  • ALAU-169774: Resolved bug where Enterprise browser app shortcut does not appear in the Launcher.
  • ALAU-169768: Resolved issue with Launcher getting stuck in a loop when prompted to select Launcher as default.
  • ALAU-169762: Resolved issue with custom widgets not displaying properly.
  • ALAU-169758: Resolved issue with Launcher blocking access to a setting after accessing sub-settings.
  • ALAU-169743: Resolved issue where open applications push to the background during Agent upgrade.
  • ALAU-169741: Resolved issue where installed app icons do not display on the Launcher until after reload.
  • ALAU-169675: Resolved issue where apps selected to launch on start up do not launch following exiting and reopening Launcher or rebooting device.
  • ALAU-169663: Resolved issue where login button in shared device mode is being cropped at bottom.
  • ALAU-169815: Resolved issue where user is unable to access Emergency Call on lock screen when in multi-user staging mode.

 

Customer Impact

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

Minimum Requirements

  • Android 4.0 (Ice Cream Sandwhich) or higher
  • AirWatch Console 9.1 (unless used in conjunction with AirWatch Agent 7.1 for Android)
  • AirWatch Agent 7.1 for Android (This is highly recommended in order to utilize new featues and other useful fixes)
  • Note for customers using a AirWatch Console version prior to 9.1: In order to prevent the unintended uninstall of the Launcher from occurring on all devices running an older seeded version of the Launcher, AirWatch Agent 7.1 for Android must be used. This issue (ARES-1657) is resolved in the AirWatch Console 9.1 as well as within the AirWatch Agent 7.1  for Android.

 

How to Download AirWatch Launcher 3.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, the users will be prompted to install the new version.
  • For Android Marshmallow and above, the user will be 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, the users will be 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, the Launcher will be setup without any end user interaction and the native launcher will be replaced by AirWatch Launcher. For non-SAFE devices, the user will be directed through a two-step process to set the AirWatch Launcher as the default Launcher.
  • For Android Marshmallow and above, the user will be 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, the users will be 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 open a Support Request, please call your local AirWatch support line or submit a Support Request via myAirWatch.

 

Best Regards,

The AirWatch Team

Have more questions? Submit a request

0 Comments

Article is closed for comments.