Debugger, hooks and developer mode flags
Apps can read whether ADB, developer options or a debugger are on.
In one line
Can check if developer mode or a debugger is turned on, with no prompt on Android
Apps can read whether ADB, developer options or a debugger are on.
Used in anti-tamper and fraud checks. Reveals a technical person or a reverse-engineer.
What it can and can't do
What the user does: Nothing. The app checks when it starts or before a sensitive step
It can
- Check if Android USB debugging is on
- Check if Android developer options are on
- Check if a debugger is attached to the app
- Guess on iPhone with indirect tests, which are not reliable
It cannot
- Turn developer mode on or off
- See what you are doing in a debugger
- Get a clear yes or no on iPhone; no official flag exists
- Tell why developer mode is on
How it differs between platforms: Android shows apps these settings directly. On iPhone apps only guess from side effects.
On Android and iPhone
| Android | iPhone | |
|---|---|---|
| Status | Supported | Partial |
| First version | Android 4.2 (API 17) | 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 | Settings.Global.ADB_ENABLED, DEVELOPMENT_SETTINGS_ENABLED, Debug.isDebuggerConnected() | Heuristic |
| Notes | Readable with no permission | None |
Data you get
What comes back: Flags
Shape: boolean
How often: On check
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
adb | boolean | None | true, false | 1 bit |
Technical limits
- Heuristic only
The story
What it is
Apps can check if your phone is in developer mode or is being debugged.
For you
You never see this check. Some apps refuse to run or log you out if developer options or a debugger are on. If you are a technical person, an app may act oddly just because you left them on.
For makers
Banks and games use it to catch people who poke at the app, copy it or cheat. It is one of many signals added to a risk score, not proof on its own.
Where you see it
| Type | Example | Apps |
|---|---|---|
| banking | A bank app refuses to open while USB debugging is on, to block screen readers that steal logins. | None named |
| games | A competitive game flags a player running a debugger to change scores or speed. | None named |
| payments | A payment app asks for extra checks when developer mode is on. | None named |
| security | A security tool counts debugger flags among signs of reverse engineering of an app. | None named |
| media | A streaming app blocks playback when a debugger could capture protected video. | None named |
| ads | An ad firm discards traffic from phones in debug mode as likely test or fraud. | None named |
Risks
- Punishes tinkerers
- False alarms
Android and iPhone in short
- Android: Apps can read settings for ADB and developer options with no prompt.
- iPhone: iPhone apps can detect a debugger attached to the app, but not Settings flags.
Good uses and abuse
Legitimate uses
- Anti-tamper
Known abuse
- Fingerprint
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 2 of 5 | How revealing the data is |
| Utility | 3 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 2 | 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: Based on official documentation.