If users are being blocked due to jailbreak detection after upgrading the SDK, please collect the information below before contacting the support team. The more information you provide, the faster the cause can be identified.
It is often difficult to request end users to perform tests such as DFU restore.
This guide is divided into mandatory collection items and optional collection items if possible. The reproduction tests are also structured step-by-step, so you may proceed only as far as feasible.
This guide is divided into mandatory collection items and optional collection items if possible. The reproduction tests are also structured step-by-step, so you may proceed only as far as feasible.
1. Confirm Detection Scope and Patterns Mandatory — Check First
- Whether the issue occurs with only one specific user or multiple users
If multiple users: Please also check if there are any patterns concentrated on specific device models / iOS versions / countries or regions. - Whether detection happens every time the app runs or intermittently
If intermittent: Please record if it mainly occurs under certain conditions (specific time periods, network environments, app states, etc.). - From which app version or SDK version the detection started occurring
2. Device and Environment Information Mandatory
- Device model (e.g., iPhone 14 Pro)
- iOS version
- App version
- DoveRunner iOS SDK version
- Date and time of detection occurrence (including timezone)
- Device UUID provided by AppSealing SDK
Optional — Can be checked through the SDK API if possible.
3. Correlation with Timing If possible
- Whether it happened right after an iOS update
- Whether it occurred after restoring from iCloud or iTunes backup
- Whether the device has MDM or corporate profiles installed
4. SDK Debug Logs Only on Internal Test Devices
SDK debug logs are the most important information for root cause analysis. However, builds with debug logs enabled output detailed SDK internal operations, so they must not be distributed to real users.
Please collect only if you can reproduce the same detection phenomenon on internal test devices.
- Enable debug log level when initializing the DoveRunner SDK (build using debug SDK)
- Reproduce detection or restart the app to trigger detection
- Collect at least 5 minutes of logs before and after detection
- Export the entire console log as a
.txtfile
Before sending, be sure to remove or mask any personal information such as user ID, name, or email.
Recommended file name format:
Recommended file name format:
[CompanyName]_[DeviceModel]_[YYYY-MM-DD]_doverunner.txt5. Reproduction Tests Mandatory As far as possible
Step 1 — Simple Test (Minimal User Cooperation)
- Delete and reinstall the app (without resetting the device) — check if detection still occurs
- Install the app on another device with the same model and iOS version — check if detection occurs
Step 2 — Detailed Test (Only if possible)
- Restore device in DFU mode and reinstall app — check if detection occurs
If detection disappears after DFU restore, the cause may be remnants of a previous jailbreak. Please be sure to include these results when submitting — they are critical evidence for determining the cause.
| Order | Device | iOS | Test Details | Detection Occurred |
|---|---|---|---|---|
| 1 | — | — | App reinstallation (no reset) | Y / N |
| 2 | — | — | Another device (same model) | Y / N |
| 3 | — | — | Reinstallation after DFU restore | Y / N |
6. User Background Information If possible — Voluntary Response
- Whether the device has a history of jailbreak
- Whether the device is second-hand
- Whether jailbreak-related apps were previously installed
7. Summary of Submitted Information
| Item | Priority |
|---|---|
| Detection scope and pattern (scale of occurrence, reproduction conditions, first affected version) | Mandatory |
| Device model · iOS version · App version · SDK version · Detection date and time | Mandatory |
| Simple reproduction test results (app reinstallation / another device) | Mandatory |
| SDK debug logs (.txt, if reproducible on internal test devices) | If possible |
| Device UUID (provided by AppSealing SDK) | If possible |
| Correlation with timing (iOS updates, backup restore, MDM presence) | If possible |
| DFU restore test results | If possible |
| User background information (jailbreak history, second-hand device status, etc.) | If possible |
Note: If detection is resolved after DFU restore, it is more likely that remnants of a previous jailbreak are the cause rather than a false positive by the SDK. Conversely, if the same detection occurs even after DFU restore, it is more likely a false positive requiring SDK logic review. In either case, including the test results when submitting will greatly assist in identifying the cause.