D04
iOS binary encryptionPending
requireEncryptedBinary flags development and ad hoc builds, and stays clean for App Store builds.
How to read this page
A scenario is one test case: prepare the environment, run the steps, then compare the expected result (written before the run) with the observed result (copied from the run, with screenshots).
- D04 · D
- Run on a real phone, used normally.
- Pending
- Not run yet. The expected result is written down; there is no observed result.
Why it matters
A decrypted App Store binary is the classic sign of a cracked or re-signed app.
Environment
- Device
- Physical iPhone
- Builds
- Development/Ad Hoc and TestFlight/App Store
Setup
Prepare the environment.Then run the steps.
- 01Enable ios.requireEncryptedBinary.
Steps
What to run.What to read.
- 01Run a development build.
- 02Run a TestFlight or App Store build.
Expected result · written before the run
Status: compromised1 signal.
Development build: flagged (expected). App Store build: clean.
Observed result
Not run yet.No observed result.
Checks this scenario covers
Every check this test case touches — including ones that aren't expected to fire here. The expected and observed results above say which ones should and did. Each links to how the check works.