DocumentationAPI Reference
SDK reference · Android SDK

Known Issues

This page lists the known issues, limitations, and intentional constraints you are most likely to run into with the Incode Android SDK. Each entry describes a lasting, customer-facing issue, not a temporary bug. The release notes track and resolve temporary bugs.

This list is a quick summary. Changelog and Migration Guide hold the authoritative, version-specific notes. Check those pages for the exact release where a behavior changed, or a limitation started or ended.

NFC

  • NFC reads only the first ID. In a flow that captures multiple IDs, NFC scanning supports only the first captured ID. See NFC Scan.
  • The SDK tries PACE protocol, then falls back to BAC. See NFC Scan for retry behavior.

Capture-Only Mode

  • Forward metadata to the Incode API. When Deepsight is enabled in Capture-Only mode, the metadata field must be forwarded from IdScanResult and SelfieScanResult to the Incode API. See Capture-Only Mode.

Delayed Mode

  • Limited module support. Delayed mode, also called offline mode, supports only the Combined Consent, Document Scan, Face Match, ID Scan, Process ID, and Selfie Scan modules. See SDK Modes.

On-Device Face Processing for Selfie Scan V2

  • Constrained configuration. SelfieScan.Builder.setOnDeviceFaceResultsSubmissionEnabled(...) requires end-to-end encryption and auto-capture. See Selfie Scan.

Video Streaming

  • Minimum RAM requirement. Video streaming requires more than 2 GB of RAM. On devices with 2 GB or less, setStreamFramesEnabled(true) is ignored.
  • Mutually exclusive with Deepsight Video Liveness. If you enable both Deepsight Video Liveness and video streaming on the Selfie Scan module, video streaming is ignored.
  • Higher minSdk. The optional video-streaming dependency requires minSdk 24 or higher. See Installation.

Emulators and Test Mode

  • Emulators return dummy results, not real captures. With Test Mode enabled, camera-dependent modules return a dummy result, such as ResultCode.EMULATOR_DETECTED. Remove setTestModeEnabled(true) before you build for production. See Installation.

Device Environment Detection

  • Hook or virtual-environment detection ends the app. Detecting a hook or virtual environment crashes the app immediately. Your code cannot catch or handle this crash. Emulator and root detection do not stop onboarding, and you cannot disable any of these checks. See Migration Guide.

Layout and Orientation

  • Selfie capture is orientation-locked. In Selfie Scan UI v2, tablets are locked to landscape and phones are locked to portrait. See Selfie Scan.

Optional Dependencies and minSdk

  • Google Wallet ID requires minSdk 28. The optional wallets dependency, used for Google Wallet ID verification, requires minSdk 28. See Google Wallet and Installation.

Version Line Scope

  • The 6.x.x line is not yet feature-complete. The 6.0.0 line supports only the Face Authentication, Face Match, ID Scan, Process ID, and Selfie Scan modules, plus a subset of optional dependencies. It does not include the UI v1 module variants. Use the 5.x.x line if your integration needs anything outside that scope. See Changelog.

Was this page helpful?