New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 823865 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Pixelbook not successfully enrolling in CryptAuth

Project Member Reported by jhawkins@chromium.org, Mar 20 2018

Issue description

Chrome Version: 67.0.3373.0
OS: CrOS

What steps will reproduce the problem?
(1) Visit chrome:proximity-auth
(2) Press 'Enroll' in CryptAuth

What is the expected result?

Enrollment succeeds

What happens instead?

11:43:32.294
cryptauth_api_call_flow.cc:80
API call failed:
{
 "error": {
  "errors": [
   {
    "domain": "global",
    "reason": "invalidArgument",
    "message": "Bad Request"
   }
  ],
  "code": 400,
  "message": "Bad Request"
 }
}
11:43:32.296
cryptauth_enroller_impl.cc:225
FinishEnrollment API failed with error: HTTP status: 400

 
proximity_auth_logs_2018-03-20T20_13_19.537Z.txt
5.1 KB View Download
Cc: agan@google.com
Owner: jhawkins@chromium.org
Status: Started (was: Available)
Failure begins in this CrOS build:

67	10497.0.0	67.0.3373.0	(multiple)	release	canary
Labels: RegressedIn-67
I believe the regression is from this CL:

https://chromium.googlesource.com/chromium/src/+/770d4f39d7656acec764bbf4bcf2256ed8efa1fe

I am testing a fix to set the display diagonal size to 0 instead of being unset.
Status: Fixed (was: Started)
Fixed by https://chromium-review.googlesource.com/c/chromium/src/+/980814, and I put the wrong bug number in the CL.

Sign in to add a comment