This feature is available for: ✓ Blueprints 2.0
This feature is in Beta. It's only available for certain customers at this time.
This feature is in Beta. It's only available for certain customers at this time.
Occasionally, you may run into errors when interacting with features throughout the console. The following error messages offer an explanation for why the error occurred and possible follow-up actions to resolve the issue.
| Feature | Error Message | Reason Why It Occurred | Possible Follow-up Actions |
| Blueprints | Invalid Blueprint Received. Cannot proceed with provisioning. | Provisioning issue. | Update to the latest Esper Agent version. |
| No parameters are provided. | Provisioning issue. | Contact Esper Support. | |
| Settings are invalid or not present to proceed with Provisioning. | Provisioning issue. | Contact Esper Support. | |
| Wi-Fi Sync | Device was not able to add wifi {SSID} which was passed in blueprints. | When the addition of a Wi-Fi access point fails. | Verify the Wi-Fi credentials are correct |
| Device was not able to connect with wifi passed in blueprints. | When the connection fails. |
|
|
| Settings | Failed to set screen timeout. Permission denied. | Android version for screen timeout is not supported. |
Some devices have minimum screen timeouts that aren’t compatible with some of Esper’s timeout options. Adjust the timeout setting to an acceptable minimum for that device. Consult your device manufacturer for more information. The minimum version for screen time out is Android 6. Screen timeouts are also compatible with a Knox-supported device (Samsung) or with a Supervisor plugin. |
| Content File issue error messages |
Create path failed - {path} -- {pathStatus.message} | Failed to create a path for the file. | Android restricts some folders. Choose a different folder or see how to obtain the correct file path. |
| Failed to restore the local version of the file {file-name} | When a file sync fails. | Verify the folder you’re saving the file to exists and has the correct write permissions. | |
| Permission wasn't granted to specified Location | When permission isn’t granted to save in the specified location. | Enable permissions or choose a different file path. | |
| Storage Permission Grant issue | Storage permission issue. | Enable permissions or choose a different file path. | |
| Unable to Sync Content, not able to create file in device at {path} | When the file isn’t created at the specified file path. | See how to obtain the correct file path. | |
| System Update Policy error messages | Invalid system update policy | When System Update Policy doesn’t match any predefined policy. | Choose a different update policy. |
| Maintenance window params absent | When TYPE_INSTALL_WINDOWED is set and window params are absent | Contact Esper. | |
| Maintenance window params are invalid | When TYPE_INSTALL_WINDOWED is set and window params are invalid | Validate the time provided for the install. | |
| System update policy Disable Updates is not compatible on this device. Setting policy to Postpone Updates | When Disable Update Policy is not compatible with your device. | Choose a different update policy. | |
| Apps | {Package-name} cannot be downgraded below preloaded version. | When a version below the preloaded version tries to install. |
As a rule, devices cannot receive downgraded versions of apps they’re running. If you need to install an earlier version, you’ll need to uninstall the app and install the earlier version. |
| {package-name} not installed on device | When trying to uninstall an app which is not present | Verify the app name and version in the blueprint and on the device. | |
| App could not be uninstalled due to an unknown error | Application issue. | Contact Esper Support. | |
| App is not supported on this Android version. | Application issue. | Verify the app is compatible with the Android version. | |
| App not installed on device | Application install issue. | Verify the app is compatible with the device and the network connection is stable. | |
| Couldn't Install Google Play Apps. | This may happen if you try to install a Google Play app on an Android Open Source Project (AOSP) device. AOSP devices do not support Google Play apps. | Install the APK of that app instead or use a Google Mobile Service (GMS) device. | |
| Download failed with error code: + errorCode | When the APK download fails | Verify the network connection is stable. | |
| Error occurred during installing + {exception message} | When an exception occurs | Try again or contact Esper Support. | |
| Error retrieving application info | When an exception occurs | Try again or contact Esper Support. | |
| Failed to install app due to Exception | When an exception occurs | Try again or contact Esper Support. | |
| Failed to install: {packageName}, reason: {reason} | Application install issue. | See the reason provided. | |
| Integrity Verification Failed | When a hash mismatch occurs | Validate the APK uploaded to the Esper Cloud. | |
| Invalid operation | The operation could not be performed. | Try again or contact Esper Support. | |
| Min SDK version is null | Application package issue. | Verify the minimum SDK version. | |
| User canceled the installation, cannot provision the device | When a user denies the request. | Verify the request with the device user. | |
| Version code is null | Application package issue. | Verify the version code. |