S04

Fail-closed gateValidated

Protected content renders only for clean. Compromised shows the blocked view with its signals.

Validatedios · android

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).

S04 · 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

The recommended integration pattern must hold on both platforms, including navigation and retry.

Environment

App: Example app, IntegrityGate component
Devices: iPhone 17 Pro simulator and Pixel 9 Pro emulator
Library: 0.1.0

Setup

Prepare the environment.Then run the steps.

01Open the example app home screen.

Steps

What to run.What to read.

01Open the protected screen: “Protected content” is shown.
02Go back (Android: hardware back button).
03Turn on “Treat emulator as compromised”.
04Open the protected screen again.
05Tap “Try again”.

Expected result · written before the run

Status: compromised1 signal.

simulator / emulator

“Access blocked” lists the signal; retry stays blocked.

Observed result · copied from the run

Status: compromisedObserved 2026-09-29.

evidence

Protected content while clean; “Access blocked” listing simulator (iOS) / emulator (Android) once the switch was on; Try again stayed blocked; Android back returned home.

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.

All scenarios

← S03 Treat the emulator as compromised S05 Signing certificate mismatch →