-
Notifications
You must be signed in to change notification settings - Fork 239
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting Error as "Your device doesn't support credential manager" For Android 14 devices when we try to call credentialManager.createCredential() function #70
Comments
Hi this is due to some OEMs not enabling passkeys on their devices. Could you please update your app to sue 1.2.1, we ahve added a fix there. Let us know if you still see the error, feel free to reopen this. |
Hi @niharika2810 ,
We checked in the Google settings or device settings, and we couldn't find any option for enabling or disabling the passkey. Could you provide further assistance with this issue? |
@niharika2810 I am still getting this issue in one of the latest Moto G73 (Android 14) device. |
Hey, would you mind creating a bug with all details required in that template? Please add version details, bug report, video rcording, device details, api version used etc. Sharing the bug link here : https://issuetracker.google.com/issues/new?component=1301097&template=1773864 |
I also encountered the same problem on my side. Do you have a solution for this problem |
Hey would you mind creating a bug with all details required in that template? Please add version details, bug report, video rcording, device details, api version used etc. Sharing the bug link here : https://issuetracker.google.com/issues/new?component=1301097&template=1773864 This will help us test and verify the issue on these devices. |
I have a Motorola g13 with Android 14 and I do have the same issue as other users had described here. Well I only want to mention, that the idea with passkey(s) (e.g. use of fingerprints) for confirmation works with other APPs well (e.g. financial transactions in Bitpanda)... The issue is well known in the android developer community regarding 'Android 14' as there are new workarounds/features in the use of identification processes with Java/Kot(z)lin → ( https://developer.android.com/identity/sign-in/credential-manager#java )... To make my blabla short: File a bug, before somebody of the high financial observers gets any idea about a fraud/scam scheme/story and reports the issue to the authorities of the Google Play Store concerning this APP ...(isn't there a Trust Wallet Token on the horizon???)... How is that to think about? [Stop asking people about sensitive device information. This is bad manner in the financial crypto industry... Just one opinion, lads. The APP is called 'TRUST ...' (!). Right? ✊🇺🇸👍] Check on this as well: chrome://flags/#web-authentication-android-credential-management Copy&Paste the link in your Chrome Browser and set "Android Credential Management for passkeys [At least this flag might help you use web3 performances in your web browser. The APP probably remains a problem. 😎] |
Change-Id: I2d96b5b0083f6f1b8c82d2bcd024684c6eaf42df
facing same issue from past few days on android 14 devices.. tested on s23 ultra failed |
facing same issue for the android 14 |
Hi @niharika2810 and team
We have successfully implemented passkeys following the guidelines provided in the Android documentation: https://developer.android.com/training/sign-in/passkeys#kotlin.
The passkeys functionality works as expected on Android versions 13 and below. However, we encountered an issue on devices running Android 14, where users received an error message stating "Your device doesn't support credential manager."
According to the documentation, the minimum supported version for Credential Manager on Android devices is 4.4 or Android 19.
We'd like to ask you to resolve this issue quickly. Thank you.
The text was updated successfully, but these errors were encountered: