S08
Misconfigured tamper options fail closedValidated
Blank or wrongly typed tamper options report unknown instead of silently skipping the check.
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).
- S08 · S
- Run on a simulator or emulator — a virtual device on a computer.
- Validated
- Run, and the result matched what was expected.
Why it matters
An empty CI variable or a typo must not turn off a check you configured.
Environment
- App
- Example app (Expo SDK 57, React Native 0.86)
- Device
- Pixel 9 Pro emulator (sdk_gphone16k_arm64), API 37
- Build
- Debug, installed with adb
- Library
- 0.2.0
Setup
Prepare the environment.Then run the steps.
- 01Call checkIntegrity from the debugger with each option below.
Steps
What to run.What to read.
- 01expectedSigningCertificates: [' : ']
- 02expectedSigningCertificates: 'nope' (not an array)
- 03allowedInstallers: [1, null]
- 04allowedInstallers: [] (empty = not configured)
Expected result · written before the run
Status: unknownNo signals.
Reason: incomplete
The empty list is the one case that means “not configured” and stays clean.
Observed result · copied from the run
Status: unknownObserved 2026-09-30.
Reason: incomplete
blank: unknown/incomplete · 'nope': unknown/incomplete · [1,null]: unknown/incomplete · []: cleanChecks 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.