Emulator and simulator detection
Apps read build fields and hardware traits to spot emulators.
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
| Android | iPhone | |
|---|---|---|
| Status | Partial | Supported |
| First version | Android 1.0 (API 1) | iOS 2.0 |
| Permission or entitlement | Not listed | none |
| Protection level | none | none |
| How access is granted | none | none |
| What the user sees | Not listed | Not listed |
| How long it lasts | Not listed | Not listed |
| How to take it back | Not listed | Not listed |
| Store policy | None listed | None listed |
| API | Build.FINGERPRINT starting with generic, Build.HARDWARE goldfish or ranchu, sensors list | Reliable for the official simulator |
| Notes | Heuristic | None |
Data you get
What comes back: Emulator flag
Shape: boolean
How often: On check
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
emulator | boolean | None | true, false | 1 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
| Type | Example | Apps |
|---|---|---|
| games | A game rewards daily logins, so it blocks emulators that run many fake accounts for bonuses. | None named |
| ads | An ad network discards installs that came from emulators because no real person will buy. | None named |
| banking | A bank app refuses to open on an emulator where malware testers hunt for flaws. | None named |
| shopping | A retailer stops bots that use emulators to grab limited sneakers. | None named |
| rideshare | A ride app blocks fake driver accounts run from emulated phones. | None named |
| developer | Developers 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
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 1 of 5 | How revealing the data is |
| Utility | 2 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 1 | Rough identifying entropy, when known |
Related capabilities
Related
- Root and jailbreak detection. Can guess if your phone is rooted or jailbroken, but cannot be sure
Same idea on the web
- Automation (webdriver) flag. Can tell if Selenium, Playwright, or Puppeteer is controlling the browser
Sources
How well checked: Inferred from related behavior.