Skip to content
This documentation is also available as markdown. For a complete index of all pages, see llms.txt at /llms.txt

App Configurations

App Configurations holds the settings that belong to a sealed app rather than to a single sealing run. Some of them — the Dex package lists and the signing certificate entries — are what the Selective options in the sealing wizard read from, so configure them here before you seal.

Open Android Mobile App Security → App Configuration.

Apps are listed as cards showing the app name, its package name, and the three toggles described below. The list shows apps sealed by you or your team members. Use the search box to filter by app name or bundle ID, and SHOW MORE to load further entries.

Click a card to open that app’s configuration page.

These appear both on the app card and on the left side of the configuration page.

ToggleDescription
ServiceWhether DoveRunner tracks hacking events for the app. Usage-based charges apply while it is on. Turn it off when you stop using an app or want to pause protection.
Data SealingHas no effect on apps sealed with version 3.x — Data Sealing was removed in 3.x and the toggle is still shown in error. See Android DataSealing.
Custom BlacklistActivates the Custom Blacklist feature for the app. The blacklist itself is edited in the Custom Blacklist section, which stays locked until this toggle is on.

Below the toggles, Transfer Account → REQUEST TRANSFER moves a sealed application to another DoveRunner account — useful when promoting an app from a POC account to production, or handing ownership to another team member.

Feeds the Dex Encryption → Selective option on Step 2 of the sealing wizard. Selective encryption lets you choose which Java/Kotlin classes or packages are encrypted, to balance protection against cold-boot performance.

FieldDescription
Package or Class NameThe target to encrypt. Placeholder: Enter Package, Class Name or File Name.
Target TypeJAVA/Kotlin Class — the named class only.
JAVA/Kotlin Package (Classes under the package) — every class under the package.

Click ADD to add the entry. Existing entries are listed below with a DELETE action.

Package Selection for Dex String Obfuscation

Section titled “Package Selection for Dex String Obfuscation”

Feeds the Dex String Obfuscation → Selective option on Step 2. Obfuscation operates at the package level only.

The section has two tabs:

TabEffect
INCLUSION LISTPackages whose strings will be obfuscated.
EXCLUSION LISTPackages skipped during obfuscation, even if they match the inclusion list. Use it for third-party libraries or reflection-heavy code.

Enter a package name — the field accepts wildcard patterns such as com.thirdparty.sdk.* — and click ADD. Each list shows its entry count in the tab label, and entries can be removed with DELETE.

Holds the certificate fingerprints that the Enable Signing Certificate Identity Check option on Step 2 compares against at runtime, to detect resigned or repackaged copies of your app.

Each entry has two fields:

FieldDescription
Certificate nameA label of your choosing, so you can tell entries apart.
SHA-256 fingerprintThe certificate’s SHA-256 fingerprint — 64 hexadecimal characters, without colons or spaces.

Use + Add Certificate Entry to add a row and × to remove one. You can store up to 5 entries; the counter above the list shows how many are in use, for example 3 / 5 entries. Click Save Entries to store them.

Multiple entries let you cover more than one valid signing identity, for example an upload key and a Play App Signing key, or a staging and a production certificate.

The Custom Blacklist is part of DoveRunner’s Over-the-Air (OTA) update service. It lets you block apps that DoveRunner’s default blacklist does not cover, and push that list to installs already in the field.

To add an entry, enter the Package Name, choose an Action Type, and click ADD:

Action TypeBehavior when the package is detected
Kill & ReportTerminates the app and reports the detection.
ReportReports the detection without terminating the app.

The section shows two tables, and understanding the split matters:

TableMeaning
Custom Blacklist ListYour working draft. Adding or deleting entries here has no effect on running apps.
Published Blacklist ListWhat is actually live and delivered to installed apps over the air.

Editing the draft changes nothing until you click PUBLISH, which pushes the draft to the published list. Two further controls manage what is live:

  • STOP LIVE UPDATE — stops delivering the published list to apps.
  • CLEAR PUBLISHED — empties the published list.

For the blacklist to reach a sealed app, that build must also have had Over the Air Update enabled on Step 5 of the sealing wizard.