Endpoint Assistant 2.x Known Issues
Technical Articles ID:
KB85892
Last Modified: 2022-12-13 11:45:44 Etc/GMT
Summary
Recent updates to this article:
To receive email notification when this article is updated, click Subscribe on the right side of the page. You must be logged on to subscribe.
| Date |
Update |
| December 13, 2022 |
Added EA 2.3.0 General Availability (GA) release details. |
This article contains important information about known issues of high or medium rating that are outstanding with this product release. This article will be updated if new issues are identified post-release, or if additional information becomes available. To read the Release Notes, see:
| Product Version |
Release Date |
Release Notes |
EOL |
EA 2.3 - Android (Build: 2.3.0)
EA 2.3 - iOS (Build: 2.3.7) |
December 13, 2022 |
Release Notes |
- |
EA 2.2 - Android (Build: 2.2.152)
EA 2.2 - iOS (Build: 2.2.99) |
May 17, 2018 |
Release Notes |
- |
| EA 2.1 - Android (Build: 2.1.116) |
September 26, 2017 |
Release Notes |
- |
| EA 2.0 - iOS (Build: 2.0.63) |
August 8, 2016 |
EOL |
June 15, 2019 |
| EA 2.0 - Android (Build: 2.0.28) |
November 9, 2015 |
EOL |
June 15, 2019 |
Issue resolutions in updates and major releases are cumulative; Technical Support recommends that you install the latest version. To find the most recent release for your product, go to the Product Downloads site. All issues that are tagged as resolved are included in the latest release, which is available from the Product Downloads site using a valid Grant Number. Updates are cumulative; so, Technical Support recommends that you install the latest one. For information about the latest releases, see the supported environments article included in the "Environment" field above.
Critical
| Critical |
| Reference Number |
Related
Article |
Found
Version |
Resolved
Version |
Issue Description |
| 1115017 |
- |
2.0 |
- |
Issue: Application crash on Android device after clicking the (.mea) file attachment in the Endpoint Assistant 2.0 enrollment email. |
Non-critical
| General |
| Reference Number |
Related Article |
Found
Version |
Resolved
Version |
Issue Description |
| 1222456 |
- |
2.0 |
2.2 |
Issue: Privacy link takes the user to a landing page, and not directly to the privacy document. |
| 1087704 |
- |
2.0 |
Expected
Behavior |
Issue: On scanning an enrollment QR code, immediately after the MEA passcode strength definition has been changed, the user might see the following error:
Generic Error Occurred
Workaround: The user can retry enrollment. Navigate to Manage Keys, Conduit Server, and then click the Enroll option. |
| Android-specific |
| Reference Number |
Related Article |
Found
Version |
Resolved
Version |
Issue Description |
| 1222268 |
- |
2.0 |
2.2 |
Issue: Date / Time entries aren't localized correctly on Android devices. |
| 1213690 |
- |
2.1 |
2.2 |
Issue: Opening an enrollment file (.mea) or encrypted file (.frpenc) on a Samsung Android 7.0 device might cause MEA to crash when handling the file. |
1178148
1183535 |
|
2.0 |
2.1 |
Issue: The error "unknown error while processing" is seen when setting up a PIN on certain devices, such as Google Pixel and Samsung Galaxy S7 Edge devices. |
| 935900 |
|
1.1 |
2.0 |
Issue: [Android (HTC platform)] In the Change Passcode screen, the text on the Cancel option isn't correctly rendered. |
| 935823 |
|
1.1 |
2.0 |
Issue: [Android (all platforms)] In some scenarios, the message "Datastore needs to be unlocked before accessing any objects" appears when trying to scan the Quick Response Code.
Workaround: Reauthenticating resolves the problem, if this message is seen when closing the app using either of the options below:
|
| 935562 |
|
1.1 |
2.0 |
Issue: [Android (all platforms)] In some scenarios where ePO enforces a stronger passcode rule, the current passcode rules aren't accepted even though they might be adequate. This issue forces the user to change the passcode again before allowing a Quick Response scan to complete.
Workaround: Changing the passcode correctly updates the rules, allowing the passcode to then be scanned. |
| 1211343 |
|
2.1 |
- |
Issue: User Interface shows an empty page after a background sync. This issue is seen when the user is unenrolled and shows the server details page. |
| 1224039 |
- |
2.0 |
- |
Issue: Keyboard remains visible during some steps of the recovery process when no text input is needed. |
| 1151200 |
- |
2.0 |
- |
Issue: Nexus X device shows an inverted camera image in portrait mode, preventing QR codes from being scanned correctly.
NOTE: The issue can also potentially apply to other devices running Android 6 or Marshmallow.
Workaround: Scan QR codes in landscape mode; the image is then captured in the correct orientation. |
| 115017 |
- |
2.0 |
- |
Issue: When accessing a (.mea) file from an enrollment email using a Gmail application (app), the MEA app might crash.
Workaround: Open the enrollment email in another email app, or open on a non-mobile device and scan the QR code with a phone to enroll. |
| 1086408 |
- |
2.0 |
- |
Issue: [Android 4.1.2] The following issue is seen in either of the following scenarios:
- When accessing a file encrypted with a key that isn't assigned to the user
- When accessing a file encrypted with a key that isn't available
Symptoms:
- An appropriate error message isn't shown
- The user might see a screen flicker before being navigated back to the previous application
NOTE: Android 4.1.x and 4.2.x are no longer supported with EA 2.2.
|
| iOS-specific |
| Reference Number |
Related Article |
Found
Version |
Resolved
Version |
Issue Description |
| 1224041 |
- |
2.0 |
- |
Issue: Keyboard remains visible during some steps of the recovery process when no text input is needed. |
| 1140521 |
- |
2.0 |
Google Drive |
Issue: Unable to open File and Removable Media (FRP) encrypted files from the Google Drive app for iOS.
Resolution: An update by Google Drive resolves this issue. |
| 1147843 |
- |
2.0 |
- |
Issue: When opening an EA or FRP enrollment email on an iPhone, the embedded QR code isn't always displayed correctly.
Workaround: If the enrollment email is opened on the phone itself, the (.mea) attachment must be used to enroll the app. |
|
