S09
Ignore specific signalsValidated
Ignored signals move to result.ignored and do not affect the status.
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).
- S09 · 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
Teams need to silence a known signal (for example debugger_attached in development) without losing visibility.
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.
- 01Configure both Android tamper checks with values that will fail.
Steps
What to run.What to read.
- 01Call checkIntegrity with ignore: ['tamper_signature_mismatch', 'tamper_untrusted_installer'].
Expected result · written before the run
Status: clean1 signal.
result.ignored lists both tamper signals.
Observed result · copied from the run
Status: cleanObserved 2026-09-30.
status clean · ignored: tamper_signature_mismatch, tamper_untrusted_installerChecks 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.