Short answer: Android Keystore availability alone does not establish that an application’s key is hardware-backed. Check the key created by the actual app on the proposed device image. If remote proof is required, validate fresh attestation on a trusted server.
Specify the key and the failure you need to prevent
Identify whether the app signs records, protects a local secret or uses a system-wide credential. Android Keystore keys and KeyChain credentials serve different application designs. Record the algorithm, key size, permitted operations and any user-authentication requirement.
Distinguish extracting a key from using it without authorization. Also define how the server recognizes the device and business account. Hardware protection of a key does not replace application permissions or confirmation that a business record was accepted.
Check the exact key, then its attestation
Generate the intended test key on the exact app and device build. Android’s Keystore documentation describes checking KeyInfo and the reported security level. A result for one key is not a result for every key on the device.
StrongBox is optional and supports a constrained set of operations. If it is required, test the requested algorithm and failure handling. Otherwise, define whether a trusted execution environment meets the project’s requirement. Do not silently substitute a different level when the security policy forbids it.
For remote proof, follow Android’s key-attestation guidance for challenge, certificate-chain, trust and revocation checks on a trusted server. A client-side label alone is not equivalent to that decision.
Connect the cryptographic result to the app
For an illustrative maintenance app, create the signing key using the required restrictions and record its security level. Have the trusted server evaluate a fresh attestation, then verify a signed test record against the intended enrolled device and authorized account.
Include a wrong account or unenrolled device. Keep key-generation failure, insufficient security level, invalid attestation and account rejection as distinct results. Never export private keys or include credentials in ordinary screenshots and test reports.
Plan replacement and recovery
A device-bound, non-exportable private key is not a portable backup. Define how a lost device is revoked, how a replacement is enrolled and how unsent work is reconciled. An application backup should not be assumed to restore the original key.
Send the required operation, target SDK, security level, attestation policy and replacement process to Integration & Support. Keep the evidence tied to the offered Android PDA Barcode Scanners and firmware. Include ordinary scanning and submission tasks in the pilot so the security check also supports the working application.
Device options for this task
Compare AIDC GO HX-21 and AIDC GO HX-27 for Android barcode work. Request build-specific evidence for the required key operation, security level and attestation policy; the listed Android version is not that evidence.