Origin
Native Application (non-browser app)
Web URL or App name
OKX
Passkey Action
Build Information
OKX
6.168.1
com.okinc.okex.gp
Google Play Store
Additional Information
When attempting to authenticate using a passkey in the OKX Global Android application, the system defaults to Google Password Manager instead of Bitwarden. This occurs despite Bitwarden being set as the primary/default Autofill and Passkey provider in Android settings.
Steps To Reproduce
Ensure Bitwarden is set as the default Autofill and Passkey provider in Android Settings.
Open the OKX Global Android application.
Trigger the Passkey authentication process (during login or in security settings).
Observe that the Android system prompts Google Password Manager rather than the Bitwarden passkey dialog.
Expected Result
Bitwarden should intercept the WebAuthn/passkey request and present the saved passkey for the OKX app.
Actual Result
Google Password Manager forcefully intercepts the passkey request, preventing the use of the passkey stored in Bitwarden.
Environment
Device: Xiaomi 15T
Operating System: Android 16
Bitwarden Version: 2026.4.0 (21434)
OKX App Version: 6.168.1
© Bitwarden Inc. 2015-2026
Version: 2026.4.0 (21434)
📱 Xiaomi 25069PTEBG 🤖 @.*** 📦 prod
🧱 commit:
@.***
💻 build source: bitwarden/android/actions/runs/23952219208/attempts/1
🦀 SDK: 2.0.0-5676-14521973
🌩 Server: 2026.4.0 @ US
Additional Context
Regular password autofill might be working correctly, but the specific passkey (FIDO2/WebAuthn) call seems to be hardcoded or misdirected to Google Play Services/Google Password Manager within this specific application.
Issue Tracking Info
Origin
Native Application (non-browser app)
Web URL or App name
OKX
Passkey Action
Build Information
OKX
6.168.1
com.okinc.okex.gp
Google Play Store
Additional Information
When attempting to authenticate using a passkey in the OKX Global Android application, the system defaults to Google Password Manager instead of Bitwarden. This occurs despite Bitwarden being set as the primary/default Autofill and Passkey provider in Android settings.
Steps To Reproduce
Ensure Bitwarden is set as the default Autofill and Passkey provider in Android Settings.
Open the OKX Global Android application.
Trigger the Passkey authentication process (during login or in security settings).
Observe that the Android system prompts Google Password Manager rather than the Bitwarden passkey dialog.
Expected Result
Bitwarden should intercept the WebAuthn/passkey request and present the saved passkey for the OKX app.
Actual Result
Google Password Manager forcefully intercepts the passkey request, preventing the use of the passkey stored in Bitwarden.
Environment
Device: Xiaomi 15T
Operating System: Android 16
Bitwarden Version: 2026.4.0 (21434)
OKX App Version: 6.168.1
© Bitwarden Inc. 2015-2026
Version: 2026.4.0 (21434)
📱 Xiaomi 25069PTEBG 🤖 @.*** 📦 prod
🧱 commit:
@.***
💻 build source: bitwarden/android/actions/runs/23952219208/attempts/1
🦀 SDK: 2.0.0-5676-14521973
🌩 Server: 2026.4.0 @ US
Additional Context
Regular password autofill might be working correctly, but the specific passkey (FIDO2/WebAuthn) call seems to be hardcoded or misdirected to Google Play Services/Google Password Manager within this specific application.
Issue Tracking Info