Resolve common account, device, and NFC problems.
Start with the message shown by the app, then check account role, phone settings, network access, and tag position before repeating a security-sensitive operation.
General questions
What is the purpose of the Android app?
It connects authenticated Xibernetix users to physical-device workflows. Depending on role, users can maintain device records, manage credentials, communicate over NFC or Bluetooth, and review security activity.
Which Android versions are supported?
The current application declares Android API 34 as its minimum SDK and API 36 as its compile and target SDK. A real NFC-capable phone is required for physical tag scans.
Why do different users see different screens?
Maker, operator, and administrator roles have different responsibilities. Both the app and backend enforce those boundaries; signing in successfully does not grant every role.
Can I use the app without an internet connection?
Some previously loaded screens may remain visible, but account requests and many device operations require the backend. NFC authentication also needs the network when the tag's diversified key is not available in encrypted local preferences.
Sign-in and passkeys
Why is passkey creation unavailable?
Confirm that the phone has a screen lock, a compatible credential provider, and current Google Play system components. Also verify that this account is eligible and does not already have the same credential registered.
Why does Google sign-in fail or return to the login screen?
Use the Google account linked to the Xibernetix profile and confirm network access. A deployment administrator should verify that the installed application ID and signing certificate have the correct Android OAuth client and that the backend accepts the configured Web OAuth client ID.
I removed a passkey, but Android still offers it. Why?
The backend passkey record and the credential stored by the phone are separate. Remove the passkey from the app and, when appropriate, remove the matching credential from Android's password manager.
NFC scanning
The phone does not detect the tag. What should I check?
Enable NFC, keep the scan screen in the foreground, find the phone's antenna position, remove thick or metallic cases, and hold the phone still against the tag. Confirm that the phone actually includes NFC hardware.
Why does the app say the tag is unsupported?
Secure processing requires ISO-DEP and a historical-byte mapping that resolves to a registered tag processor. Generic NDEF labels and other NFC technologies may be discoverable without supporting the Xibernetix secure authentication workflow.
Why did authentication fail even though tag details appeared?
Hardware details are collected before or independently of final identity verification. Failure can indicate an interrupted exchange, missing diversified key, cryptographic mismatch, invalid card status, unreadable operator file, or an operator-ID mismatch. Treat the authentication status—not the presence of details—as authoritative.
What does AUTH_DELAY mean?
The tag is rate-limiting authentication after unsuccessful attempts. Keep the tag away from the RF field for the interval required by its security configuration before trying again. Repeated immediate scans can extend the problem.
What should I do if the phone moved during provisioning?
Do not assume the tag is ready. Keep it in the approved inventory, wait for any authentication delay to clear, and scan it again with the same environment and operator. If it still fails, record the displayed status and contact support rather than attempting to format it.
Can another operator use a provisioned tag?
Not as the verified owner under the current workflow. Existing tags succeed only when the operator ID stored in file 2 matches the subject of the signed-in operator's token.
When contacting support
Include the application flavor and version, Android version, phone model, selected role, approximate time, the visible response status, and whether the tag was new or previously provisioned. Do not send authentication tokens, master keys, session keys, or full production logs through an unapproved channel.