Troubleshooting
Errors occurred during the use of DoveRunner Mobile App Security CLI Tool can be found and explained under the Exit Code in this table. Errors can be resolved by following the procedures. However, ‘DoveRunner Mobile App Security Help Center (https://helpcenter.appsealing.com)’ can be used to inquiry issues that cannot be resolved through this chapter.
| Exit Code | Description | Procedures |
|---|---|---|
| 100 | No parameter sent to the CLI Tool | Go to 3.1 DoveRunner Mobile App Security Jenkins parameter settings and check if the ‘required’ fields and Sealing options has been sent to the CLI tool execution parameter. |
| 101 | Configuration file path not entered or the file does not exist in the entered path. | Make sure that the valid configuration file path has been entered. |
| 103 | Failed to retrieve information for Sealing | Check if the access to CLI Tool has been granted. Please send the CLI Tool log and OS environment to our Helpcenter if this continues to occur. |
| 110 | Failed to authenticate CLI Tool | CLI Tool authentication can fail due to the following reasons: |
| 1) authkey is not entered or not valid | ||
| -Check if the enteredauthkey is the issued authkey. | ||
| 2) tool version or the hash value is not valid | ||
| -CLI Tool has been modified or failed to pass the validity check. Please try again using the official version from DoveRunner Mobile App Security. | ||
| 3) Sealing with different package other than the package registered to the authkey | ||
| - Unregisteredtitle (package name) cannot be Sealed using the tool. Please request package registration and then proceed to Sealing. | ||
| Sealing option validity check may have failed. | ||
| 1) When(emulator, rooting) ** block option is not valid** | ||
| -block_environment cannot be configured other than’emulator’, ‘rooting’. | ||
| **2) When allow_external_tool option (macro, sniff) is not valid ** | ||
| - allow_external_tool cannot be configured other than ‘macro’, ‘sniff’. | ||
| 3) Invalid deploy mode - deploymode cannot be configured other than’test’, ‘release’. | ||
| 4****)** Invalid dex encrypt option - dex_encrypt cannot be configured other than ‘no’ or ‘yes’ | ||
| 5 ) **** Invalid App Type **- app_type cannot be configured other than ‘GAME’ or ‘NON_GAME’ | ||
| 6)** Invalid Sealing Optio** n**Using un-supported Sealing Option or typo in the entered value. | ||
| The CLI Tool retries to connect to the network every 10 seconds in total of 10 tries when the network in unstable during the authentication process. It’ll proceed to next step once the network in stable. However, error will occur if the network in unstable after the end of retries**. | ||
| [Message during retry] | ||
| The request can not be completed temporarily. Try again… ( 1 / 10 ) | ||
| [Error message] | ||
| Validation check failed. Please try sealing again. Contact us through Helpcenter if the problem is not resolved. [reason : cause of exception] (exit code: 110) | ||
| 120 | Invalid Sealing option delivered to CLI Tool | Sealing option validity check can fail due to following reasons : 1) Invalid url - Sealing cannot be processed if the url is invalid or because of firewall. Since CLI Tool usesHTTPS (SSL) protocol make sure that the environment allows connection to https during Sealing.2) Invalid srcapk path - srcapk option was not entered or there is no APK/AAB file in the path that was entered. 3) Invalid sealedapk path - sealedapk was not entered. |
| 130 | Failed to upload the APK file | Make sure that the APK/AAB file defined in the Sealing option ‘srcapk’ exist and the network is connected. |
| The CLI tool retries to upload the APK/AAB file every 10 seconds in total of 10 tries when the network in unstable during the upload process. It’ll proceed to the next step when the network is stable. However, error will occur if the network in unstable after the end of retries. | ||
| [Message during retry]The request can not be completed temporarily. Try again… ( 1 / 10 ) | ||
| [Error message] | ||
| APK/AAB file upload failed. Please try sealing again. Contact us through Helpcenter if the problem is not resolved. [reason : cause of exception] (exit code: 130) | ||
| 140 | Failed to request Sealing | Error occurred during Sealing request. Please send the log to Helpcenter for analysis. |
| The CLI Tool retries to connect to the network every 10 seconds in total of 10 tries when the network in unstable during the Sealing request process. It’ll proceed to next step once the network in stable. However, error will occur if the network in unstable after the end of retries. | ||
| [Message during retry] | ||
| The request can not be completed temporarily. Try again… ( 1 / 10 ) | ||
| [Error message] | ||
| Request sealing failed. Please try sealing again. Contact us through Helpcenter if the problem is not resolved. [reason : cause of exception] (exit code: 140) | ||
| 150 | Failed Sealing | Error occurred during Sealing process. Please send the log to Helpcenter for analysis. |
| The CLI Tool retries to connect to the network every 10 seconds in total of 10 tries when the network in unstable during the Sealing process. It’ll proceed to next step once the network in stable. However, error will occur if the network in unstable after the end of retries. | ||
| [Message during retry] | ||
| The request can not be completed temporarily. Try again… ( 1 / 40 ) | ||
| [Error message] | ||
| Process sealing failed. Please try sealing again. Contact us through Helpcenter if the problem is not resolved. [reason : cause of exception] (exit code: 150) | ||
| 160 | Failed to download Sealed APK | Error occurred during download of the Sealed APK/AAB file. |
| APK/AAB file is downloaded after the Sealingprocess has been finished. The CLI Tool retries to connect to the network every 10 seconds in total of 10 tries when the network in unstable during the download process. It’ll proceed to next step once the network in stable. However, error will occur if the network in unstable after the end of retries. | ||
| [Message during retry] | ||
| The request can not be completed temporarily. Try again… ( 1 / 10 ) | ||
| [Error message] | ||
| APK/AAB file download failed. Please try sealing again. Contact us through Helpcenter if the problem is not resolved. [reason : cause of exception] (exit code: 160) | ||
| 250 | Unstable server | Unexpected error occurred in the server. Please try again after 5 minutes. If the issue continues to occur then please send the log to the Helpcenter. |