AirWatch administrators may find that Android restriction profiles first created in AirWatch Console 7.0 will block the navigation bar on Samsung devices running Android Oreo (8.0) or higher. Restriction profiles created in AirWatch Console 7.0 and below included a payload to disable the navigation bar by default and will disable software navigation keys such as Home, Recent Tasks, and Back. This profile payload cannot be enabled or disabled through the Console Profile Configuration UI.
AirWatch administrators should be advised that the payload does not affect Samsung devices running Android Nougat (7.1) and below. Additionally, administrators should note that profiles created in AirWatch Console 7.1 and higher leave the navigation bar enabled by default.
In order to determine whether a restriction profile is affected by this issue:
- Log into the AirWatch Console and navigate to:
Devices > Profiles & Resources > Profiles > List View
- Select the radio button of the Android restriction profile in question
- From the available actions, click the XML button
- Use CTRL+F (Windows) or CMD+F (macOS) in order to find the
- If the value for the flag is set to
False, the profile was created prior to AirWatch Console 7.1 and will impact Android Oreo users on Samsung devices
SaaS environments (Shared & Dedicated):
AllowNavigationBar flag has been set to “True” on all Restrictions Profiles in AirWatch SaaS environments, so new enrollments will no longer be affected by this issue. These profiles will not be automatically re-pushed to existing devices. Therefore, to correct this issue for currently-enrolled devices, any installed Restrictions Profiles must be manually re-pushed to these devices.
Admins can run the SQL script found in the myAirWatch Portal to resolve this issue. The implications are the same as described above for SaaS environments. It is recommended that admins take a backup of the AW Database before running SQL scripts such as this.
An alternative resolution is to create a new Android Restrictions Profile and manually copy over the settings of the affected profile. Once the new profile has been applied to devices, administrators should deactivate the affected profile.
Our product team has been engaged and is actively working to resolve the issue.
Other Languages: 日本語