Troubleshooting¶
getClassification() always returns insufficient or undetermined¶
Cause: One of the following:
- The user has not consented, so nothing is recorded.
- The session has fewer actions than the model asks for, 8 with the built-in model: the result
is
insufficient. See Evidence. - The result is
undetermined: the score lies betweenbotThresholdandhumanThreshold. - Capture was paused and never resumed.
- The SDK cannot score:
isScoringisfalseand the result isinsufficient. - Automation detection stopped the SDK:
stoppedis notnulland the result isinsufficient. Seestoppedis notnull. - The user's input happened where the SDK cannot see it — typing, or a web view — and your app does not report it.
- The app came back after more than five minutes in the background, and the evidence started over.
Solution: Check each in turn:
final dea = DeaSdk.instance!;
debugPrint('consent: ${dea.consent.decision}'); // must be granted
debugPrint('scoring: ${dea.isScoring}'); // must be true
debugPrint('error: ${dea.error}'); // must be null
debugPrint('stopped: ${dea.stopped}'); // must be null
final read = dea.getClassification();
debugPrint('result: ${read.result}, actions: ${read.actions}, '
'score: ${read.value}, thresholds: ${read.botThreshold}..${read.humanThreshold}, '
'model: ${read.modelVersion}');
insufficientmeans fewer actions than the model asks for yet:actionsis below 8 with the built-in model, andscoreisnull.undeterminedmeans the score lies between the two thresholds.- Make sure every
pause()has a matchingresume(). - For input the SDK cannot see, see Report input the SDK cannot see.
getClassification() throws ThresholdMissing¶
Cause: The loaded model has no bot threshold. Its version is on the exception's
modelVersion.
Solution: Catch ThresholdMissing at the decision point and take your fallback path. Make sure
model updates are running — they do unless you set modelUpdates: false — so the SDK replaces
the model when DEA publishes a newer one; checkForModel(force: true) checks at once. See
Options.
getClassification().actions stays at 0 while the user interacts¶
Cause: Nothing is being recorded. Usually the user has not consented yet; otherwise capture is
paused, or events excludes the input you are testing.
Solution: Show the consent dialog and accept it — see
User Consent. If consent is granted, check for a
pause() without a matching resume(), and check events.
Nothing appears in the log with debug: true¶
Cause: The published Flutter package carries no log. debug and onLog have no effect in it.
Solution: Check the SDK from code instead — see Verify your setup.
isScoring is false and error is set¶
Cause: The core is not running. error says which of these it is:
erroris aCoreMismatch:dea_sdkis at a different version fromdea_baseordea_automation_detection. The SDK refuses to run with mixed versions and stays paused.erroris the exception the load threw: the core could not be loaded on this device. The package ships it for Androidarm64-v8aandx86_64, so a device that can only run 32-bit apps (armeabi-v7a) has none.
Solution: For mixed versions, download all three zips from the same release, and point
dea_base and dea_automation_detection at those copies:
dependencies:
dea_sdk:
path: vendor/dea/sdk
dependency_overrides:
dea_base:
path: vendor/dea/base
dea_automation_detection:
path: vendor/dea/automation_detection
Then run flutter pub get.
For a library that could not be loaded, test on a 64-bit device or emulator. On a device without
the core the SDK keeps running, and getClassification() answers insufficient.
What stops while the core is not running:
| Stops | What the app sees |
|---|---|
| Score | Classification.unscored (insufficient); isScoring false; coreStats null |
| Model restore and updates | model is version 0, source embedded, updateFault no_core; checkForModel answers cancelled, "model updates are not running" |
| Automation detection | Never starts |
Proofs: record, sendProof, getProof |
proof.not_signed, outcome refused, dea.reason: no_core |
Scored signRequest |
null; lastRequestRefusal "nothing signed: no core to compose the evidence"; no log entry |
replaySession |
null |
sdk.ready |
sdk.core_failed instead; error set |
| Capture, mixed versions only | Nothing is captured |
Capture, integrations, attest() and unscored signRequest keep working.
stopped is not null¶
Cause: With automationDetection: true, the SDK found a sure sign that automation drives the
app. It stopped every operation at once. This applies on every account and build, test builds
included. The stop lasts until reset() or a new start.
Solution: Call reset(), for example at the next session, or start the SDK again: launch the
app again, or call dispose() then init. resume() and setConsent(true) do not lift the stop.
If automation goes on, the SDK stops again. For your own automated tests, leave
automationDetection off. A staging or test build logs automation.detected with the signal that
fired, then sdk.stopped with dea.reason: automated.
With automationDetection on, a rooted Android device or a jailbroken iPhone also stops the SDK: a
staging build logs sdk.device_compromised with the trace it found, then sdk.stopped. reset()
lifts the stop, then the SDK stops again on the same device. A test build only logs it and keeps
running.
An external touchscreen on Android does not stop the SDK: a staging or test build logs it as
automation.soft_signal, and the SDK keeps running.
| Stops | What the app sees |
|---|---|
| Capture | Nothing is recorded; resume() and setConsent(true) do not start it again |
| Score | getClassification() answers insufficient with actions 0 and every number null |
| Model updates | checkForModel answers without a request |
| Attestation | attest() answers failed without a request; attest.failed with dea.reason: automated. Automatic renewal stops |
Proofs: record, sendProof, getProof |
Nothing signed, without a request; proof.not_signed, dea.reason: automated; lastProofRefusal automated |
signRequest |
null; proof.not_signed with automated; lastRequestRefusal automated |
| Integrations | Nothing more is sent; what was sent before the stop stays sent |
reset() lifts the stop, and dispose() works as always.
Options passed to a later init are ignored¶
Cause: DeaSdk.init was called more than once. The first call's options stay in effect. A
staging or test build logs sdk.init_repeated, and dea.option names the first option that
differs.
Solution: Call DeaSdk.init once, in main(). If you really need different options, call
DeaSdk.instance?.dispose() first.
The consent dialog appears on every launch¶
Cause: The answer is not being stored. Either remember: false is passed, or the SDK's native
plugin is not registered in the app (for example, in an add-to-app setup), so the answer cannot be
saved.
Solution: Remove remember: false unless the device is shared. Otherwise make sure the app
uses the generated plugin registrant, and rebuild the app fully rather than hot-restarting after
adding the package.
attest() returns unsupported¶
Cause: One of the following:
- No
appKeywas passed toDeaSdk.init.attestation.detailthen says so. - No signing key could be created: the SDK's native plugin is not registered, or the device has no secure key storage.
Solution: Pass the appKey DEA issued for this platform's app — see
Options. Otherwise rebuild the app fully after adding the
package, and test on a real device.
attest() returns failed¶
Cause: attestation.detail says which of these it is:
- Google or Apple would not issue a token.
detailstarts withPlay Integrity refusedorApp Attest. - DEA refused the registration.
detailnames the request and the status DEA answered, for example/api/attest answered 403. - DEA could not be reached.
- Attestation is paused after earlier refusals.
detailstarts withattestation paused until. - Automation detection stopped the SDK, and no request was made. See
stoppedis notnull.
Solution:
- On Android, test with a build installed from a Google Play testing track, on a device with Google Play services, and check that your app's Play Console entry is linked for Play Integrity — see Attest.
- On iOS, a
detailmentioninginvalidKeyusually means the App Attest capability is missing from the build — see Attest. - Check that the
appKeyis the one DEA issued for this platform's app: the Android key on Android, the iOS key on iOS. - A paused attestation resumes by itself at the time
detailgives.
attest() passes but platformAttested is false¶
Cause: The platform had no token to give: the app runs on the iOS Simulator, or on iOS 12 or 13, where App Attest is not available.
Solution: Test attestation on a real device with iOS 14 or later — see Attest.
Touches inside a web view do not count¶
Cause: A web view handles its own touches, and Flutter does not route them to the SDK.
Solution: Forward them with capturePointer — see
Report touches inside a web view.
If forwarded touches still do not count, check that their kinds are listed in
events and that x and y include the web view's offset in
the window.
sdk.app_id_missing in the log¶
Cause: No appId was passed, the appId is blank, or it is unknown-app. The SDK runs under a
production appId DEA has not registered.
Solution: Pass the appId DEA issued for this app — see
Accounts and keys.
The model never updates¶
Cause: Updates are off. DeaSdk.instance?.model.updateFault says why; null means they are running.
updateFault |
Cause | Solution |
|---|---|---|
no_core |
The core did not load | See isScoring is false and error is set |
disabled |
modelUpdates: false was passed to init |
Remove it |
no_storage |
No modelDirectory, and the platform gave no folder (any platform other than Android and iOS) |
Pass a modelDirectory |
Solution: Apply the row for the value you read. With null, updates are running: a check runs
at every start, and checkForModel asks now.