Status Update
Comments
an...@google.com <an...@google.com> #2
I notice the same issue and LogCat shows the following message:
Google Play services out of date. Requires 3159100 but found 3136130
Google Play services out of date. Requires 3159100 but found 3136130
ss...@google.com <ss...@google.com> #3
Same here.
"Google Play services out of date. Requires 3159100 but found 3136130"
"Google Play services out of date. Requires 3159100 but found 3136130"
bb...@google.com <bb...@google.com>
ns...@chromium.org <ns...@chromium.org>
bb...@google.com <bb...@google.com> #4
me as well....
Google Play services out of date. Requires 3159100 but found 3136130
Google Play services out of date. Requires 3159100 but found 3136130
bb...@google.com <bb...@google.com> #5
I was hopeful that the release of API 18 (4.3) would have created a solution to this, unfortunately it includes version 3158130
jb...@yubico.com <jb...@yubico.com> #6
Having the same issue:
07-25 00:03:54.998: W/GooglePlayServicesUtil(27293): Google Play services out of date. Requires 3159100 but found 3158130
07-25 00:03:54.998: W/GooglePlayServicesUtil(27293): Google Play services out of date. Requires 3159100 but found 3158130
Description
Steps to reproduce the problem
Problem Description
What I’ve discovered from the chrome://device-log is that at the CTAP layer, the call to the HSK is being populated with an allowCredentials list containing the credential ID of the iCloud Keychain credential, which of course the HSK cannot honour. There should not have been an allowCredentials list injected into the CTAP message.
Summary
WebAuthn API injects allowCredentials list to CTAP when no allowCredentials supplied
Custom Questions
Which component does this fall under?
Blink>SecurityFeature
Does this work in other browsers?
Yes - This is just a Chrome problem
Additional Data
Category: API
Chrome Channel: Stable
Regression: Yes