Troubleshooting
A check comes back failed
Section titled “A check comes back failed”result.error says why. Not supported on this platform means the plugin
isn’t available (web, desktop, or a missing native build). Timed out after 5s means the native check didn’t answer; try again. See
Error handling.
The emulator or Simulator shows as detected
Section titled “The emulator or Simulator shows as detected”Expected: that’s the emulator check working. Root and jailbreak aren’t
affected. On the iOS Simulator jailbreak is notApplicable, and on Android
emulators root comes back clear because emulator system properties are only
weak signals.
A weak signal is listed but the check is clear
Section titled “A weak signal is listed but the check is clear”Expected. Weak signals, such as debuggable_flag on debug builds, are
reported so you can see them, but never decide the result. See
Detection results.
Mock location never detects a mocked location
Section titled “Mock location never detects a mocked location”Check result.locationPermissionGranted. The SDK doesn’t request location
permission; your app must. On iOS, location signals rarely fire today. See
Mock location.
screenshots never fires
Section titled “screenshots never fires”- On Android it needs Android 14 (API 34) or later.
- Check you haven’t removed the merged
DETECT_SCREEN_CAPTUREpermission. - It fires only while your app is in the foreground.
setScreenshotProtection returns failed
Section titled “setScreenshotProtection returns failed”There’s no window or activity yet, for example when called before runApp
has shown anything. Call it once your UI is on screen.
iOS: “unable to override package ‘device_shield’”
Section titled “iOS: “unable to override package ‘device_shield’””This only happens when building the plugin’s own example app, not your app. See Installation.