Skip to Content
Platform.Ontology

Emulator and simulator detection

Apps read build fields and hardware traits to spot emulators.

Gets silentlyDevice detailsIntegrityAndroid and iPhoneWhen the app opensWhile you use it

In one line

Can tell if the app is running on a fake phone used for testing

Apps read build fields and hardware traits to spot emulators.

Used to block bots and farms. A real phone with unusual build fields can be flagged by mistake.

What it can and can't do

What the user does: Nothing. The app checks when it starts or when you sign in

It can

  • Spot the official iPhone Simulator reliably
  • Guess an Android emulator from build names and hardware clues
  • Block or limit features when it thinks it is on a fake device

It cannot

  • Always catch Android emulators; the test is a guess and can be fooled
  • Tell you apart from a real phone in many cases
  • Learn anything personal from this check alone

How it differs between platforms: iPhone Simulator is easy to detect. Android emulators are guessed from clues, which can be faked.

On Android and iPhone

AndroidiPhone
StatusPartialSupported
First versionAndroid 1.0 (API 1)iOS 2.0
Permission or entitlementNot listednone
Protection levelnonenone
How access is grantednonenone
What the user seesNot listedNot listed
How long it lastsNot listedNot listed
How to take it backNot listedNot listed
Store policyNone listedNone listed
APIBuild.FINGERPRINT starting with generic, Build.HARDWARE goldfish or ranchu, sensors listReliable for the official simulator
NotesHeuristicNone

Data you get

What comes back: Emulator flag
Shape: boolean
How often: On check

FieldTypeUnitRangePrecision
emulatorbooleanNonetrue, false1 bit

Technical limits

  • Heuristic only

The story

What it is

Apps try to tell if they run on a real phone or a fake one on a computer.

For you

You do not see it. If you run an app on a computer or an unusual phone, it may refuse to open or hide some features. Most real phones pass without notice.

For makers

Emulators let fraudsters run hundreds of fake users. Makers check build fields and hardware to block bots, fake installs and cheaters. Real phones with odd settings can get flagged by mistake.

Where you see it

TypeExampleApps
gamesA game rewards daily logins, so it blocks emulators that run many fake accounts for bonuses.None named
adsAn ad network discards installs that came from emulators because no real person will buy.None named
bankingA bank app refuses to open on an emulator where malware testers hunt for flaws.None named
shoppingA retailer stops bots that use emulators to grab limited sneakers.None named
rideshareA ride app blocks fake driver accounts run from emulated phones.None named
developerDevelopers run their own app on emulators to test, and turn the check off for those builds.None named

Risks

  • Can block real users
  • Easy to dodge

Android and iPhone in short

  • Android: Checks look at build fields and sensors. Play Integrity gives a verdict.
  • iPhone: iOS apps know when they run on the Simulator, which is easy to tell on a Mac.

Good uses and abuse

Legitimate uses

  • Fraud prevention

Known abuse

  • False positives

Scores

ScoreValueMeaning
Sensitivity1 of 5How revealing the data is
Utility2 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bits1Rough identifying entropy, when known

Same idea on the web

Sources

How well checked: Inferred from related behavior.

On this page