Assigned
Status Update
Comments
h1...@gmail.com <h1...@gmail.com> #2
My Google Play Services version:40.1.20-23[0][PR]614033715
bl...@google.com <bl...@google.com> #3
Automated by Blunderbuss job android-credential-manager-autoassigner for config android_credman_config for component 1301097.
re...@google.com <re...@google.com> #4
Could you confirm that you have Google accounts on the device?
Also, please attach logs/ideally bug report when executing this flow so we can take a look at what is happening.
h1...@gmail.com <h1...@gmail.com> #5
I'm sure there is a valid Google account logged in on the phone. This is the log generated when the above code snippet was executed on this Xiaomi phone.
h1...@gmail.com <h1...@gmail.com> #6
So far, I have tried several Xiaomi phones, and they all have the same issue. If you can get a Xiaomi device, you should be able to easily reproduce this problem.
Description
Component used: Credentials
Version used:1.3.0
Devices/Android versions reproduced on:Xiaomi 13 pro /Xiaomi HyperOS 2.0.3.0. VMBCNXM/android15
If this is a bug in the library, we would appreciate if you could attach:
This issue only occurs on Xiaomi's HyperOS. The same project runs normally on other devices.But this phone can log in normally using com.google.android.gms:play-services-auth:21.1.0