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

Issue 606064 link

Starred by 1 user

Issue metadata

Status: Verified
Owner: ----
Closed: May 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Error messages while creating new Gmail account from Sign-in screen

Project Member Reported by sdantul...@chromium.org, Apr 22 2016

Issue description

Google Chrome	51.0.2704.23 (Official Build) dev (32-bit)
Revision	0
Platform	8172.9.0 (Official Build) dev-channel veyron_speedy

What steps will reproduce the problem?
(1) Create a new gmail account from Sign-in screen
(2) At the end of user creation click 'I Agree'

What do you see instead?
1. Sorry your email or password could not be verified. Please try again. (Attached screenshot)
2. Enter the new user gmail id and password. Error screen is shown. (Attached screenshot)
3. Click Next on the error screen. Sign-in screen is shown again. Now enter the user id and password again. New user is successfully logged in.

 
IMG_20160422_125829.jpg
2.5 MB View Download
IMG_20160422_153134.jpg
2.0 MB View Download

Comment 1 by x...@chromium.org, Apr 25 2016

Also repro this issue on 52.0.2712.0(Platform 8088.0.0 link)

Comment 2 by x...@chromium.org, Apr 25 2016

Cc: alemate@chromium.org xiy...@chromium.org
Labels: -Pri-2 M-50 Pri-1
Also repro this on 50.0.2667.0 (Platform 7982.0.0 link). The error shows up here: https://code.google.com/p/chromium/codesearch#chromium/src/chrome/browser/chromeos/login/existing_user_controller.cc&l=611. 

Selected log message:
[oauth2_token_fetcher.cc(133)] Unrecoverable error or retry count max reached. State: 7, network error: 0, message:
[oauth2_token_initializer.cc(40)] OAuth2TokenInitializer - OAuth2 token fetch failed
[existing_user_controller.cc(45)] OAuth2 token fetch failed

+xiyuan@ in case he saw this before.
+alemate@ in case it might be related to the AccountId series CLs 

Comment 3 by x...@chromium.org, Apr 25 2016

Sorry the version in #2 is 50.0.2657.0

Comment 4 by xiy...@chromium.org, Apr 25 2016

Did we get user name and password from the account creation flow? If not, we need to check with Gaia team. Otherwise, we can debug to see why it is rejected.

Comment 5 by x...@chromium.org, Apr 26 2016

It seems that the root cause is in Gaia side. Opened an issue in Buganizer: https://buganizer.corp.google.com/u/0/issues/28398036

Comment 6 by x...@chromium.org, May 9 2016

Status: Fixed (was: Untriaged)
It has been fixed in https://buganizer.corp.google.com/u/0/issues/28398036.
Status: Verified (was: Fixed)
ChromeOS:7978.74.0/50.0.2661.103

Sign in to add a comment