NO NETWORK · NO TELEMETRY · FAILS CLOSED · v0.3.0

S03

Treat the emulator as compromisedValidated

With treatEmulatorAsCompromised on, the same emulator signal makes the status compromised.

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

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

Apps that must not run on emulators need a one-line policy switch, without losing the signal in normal use.

Environment

App
Example app
Devices
iPhone 17 Pro simulator (iOS 26.4) and Pixel 9 Pro emulator (API 37)
Library
0.1.0 and 0.2.0

Setup

Prepare the environment.Then run the steps.

  1. 01Open the example app home screen.

Steps

What to run.What to read.

  1. 01Turn on “Treat emulator as compromised”.
  2. 02Wait for the badge to update.

Expected result · written before the run

Status: compromised1 signal.

  • simulator / emulator

Observed result · copied from the run

Status: compromisedObserved 2026-09-29.

evidence
Status badge changed to COMPROMISED on both platforms; the only signal was the simulator/emulator signal.

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
← S02 Android emulator baselineS04 Fail-closed gate →