--- title: "Troubleshooting" description: "Troubleshooting guide for common issues with the DoveRunner Mobile App Security CLI tool and their solutions." --- > For the complete documentation index, see [llms.txt](/llms.txt). Errors that occur when using the DoveRunner Mobile App Security CLI Tool are identified by exit codes. Use the table below to locate your exit code and follow the resolution steps. If the issue cannot be resolved, contact the [DoveRunner HelpDesk](https://support.doverunner.com). ## Exit Code Reference | Exit Code | Description | Action | |-----------|-------------|--------| | **100** | No parameter sent to the CLI Tool | Check that all required parameters are configured in your CI settings | | **101** | Configuration file path not entered, or file not found at the specified path | Verify that a valid configuration file path has been entered | | **103** | Failed to retrieve sealing information | Verify CLI Tool access; contact HelpDesk with the log if the issue persists | | **110** | Authentication failed, or sealing option validation failed | [See details below](#110--authentication--option-validation-failed) | | **120** | Invalid sealing option delivered to CLI Tool | [See details below](#120--invalid-sealing-option) | | **130** | Failed to upload APK/AAB file | Verify the file exists at the `srcapk` path and network is available; [see retry behavior](#network-retry-behavior) | | **140** | Failed to request sealing | Send the log to HelpDesk for analysis; [see retry behavior](#network-retry-behavior) | | **150** | Sealing process failed | Send the log to HelpDesk for analysis; [see retry behavior](#network-retry-behavior) | | **160** | Failed to download sealed APK/AAB | Check network connectivity; [see retry behavior](#network-retry-behavior) | | **250** | Unstable server | Retry after 5 minutes; contact HelpDesk with the log if the issue persists | --- ## 110 — Authentication / Option Validation Failed ### Authentication failure **1. `authkey` not entered or not valid** Verify that the entered `authkey` matches the key issued for your account. **2. Tool version or hash value is not valid** The CLI Tool may have been modified or failed the integrity check. Download the official version from the DoveRunner Mobile App Security console and try again. **3. Package not registered to the `authkey`** Only app packages registered to your account can be sealed. Request package registration before proceeding. ### Sealing option validation failure **1. Invalid `block_environment` value** — only `emulator` and `rooting` are accepted. **2. Invalid `allow_external_tool` value** — only `macro` and `sniff` are accepted. **3. Invalid `deploymode` value** — only `test` and `release` are accepted. **4. Invalid `dex_encrypt` value** — only `yes` and `no` are accepted. **5. Invalid `app_type` value** — only `GAME` and `NON_GAME` are accepted. **6. Unsupported option or typo** — check for unsupported option names or incorrect values. ### Network instability during authentication The CLI Tool retries the connection every 10 seconds, up to 10 times. If the network stabilizes within that window, the process continues automatically. ``` [Retry message] 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 **1. Invalid `url`** Sealing cannot proceed if the URL is invalid or blocked by a firewall. The CLI Tool uses HTTPS (SSL) — ensure your environment allows outbound HTTPS connections. **2. Invalid `srcapk` path** The `srcapk` option was not entered, or no APK/AAB file exists at the specified path. **3. Invalid `sealedapk` path** The `sealedapk` option was not entered. --- ## Network Retry Behavior For exit codes **130**, **140**, **150**, and **160**, the CLI Tool automatically retries the network operation every 10 seconds. Exit codes 130, 140, and 160 retry up to 10 times; exit code 150 retries up to 40 times during the sealing process. Once the network stabilizes, the process continues automatically. ``` [Retry message] The request can not be completed temporarily. Try again... ( 1 / 10 ) ``` If the network remains unstable after all retries, the following error messages are shown: ``` [Exit code 130] 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) [Exit code 140] Request sealing failed. Please try sealing again. Contact us through Helpcenter if the problem is not resolved. [reason : cause of exception] (exit code: 140) [Exit code 150] Process sealing failed. Please try sealing again. Contact us through Helpcenter if the problem is not resolved. [reason : cause of exception] (exit code: 150) [Exit code 160] 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) ``` --- ## Other Symptoms ### Sealing takes more than 1 hour Apps larger than 500 MB may take additional time for upload and download, but the sealing process itself should not exceed 1 hour. If sealing has been running for more than 1 hour with no progress, this indicates abnormal behavior. **What to do:** Leave the current session as-is and start a new sealing session. If the issue recurs, contact HelpDesk with the sealing log. ### Sealing fails with an app registered to a different account If you attempt to seal an app that is registered under a different account, sealing will fail. Verify that the `authkey` used and the account that owns the app belong to the same team or organization. ### Upload or download speed is too slow Slow transfer speeds are typically a network issue rather than a sealing problem. **What to do:** 1. If on Wi-Fi, switch to a wired connection and try again. 2. If still slow, contact HelpDesk with your current region, app size, and sealing log. ### Other errors For any error not covered in this guide, contact [HelpDesk](https://support.doverunner.com) with the sealing log and your environment details.