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

Issue 684057 link

Starred by 1 user
Status: WontFix
Owner:
msarda@chromium.org
Closed: Feb 2017
Cc:
pav...@chromium.org
mastiz@chromium.org
█ tschumann@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Not able to sign in to Chrome on a testgaia account

Project Member Reported by jnaveen@chromium.org, Jan 23 2017 
ENVIRONMENT and STATS
Chrome version: 57.0.2984.0
Sync server: testgaia

REPRO STEPS
1. Sign in to Chrome using a testgaia account

ACTUAL RESULTS
Error "Sorry, there seems to be a problem. Please try again." message is displayed. See the attached screenshot

EXPECTED RESULTS
Signed in to Chrome without any errors.

ADDITIONAL INFO
testgaia_signin.JPG
40.1 KB View Download
testgaia_signin_internals.JPG
71.1 KB View Download

Comment 1 by pav...@chromium.org, Jan 24 2017

Cc: pav...@chromium.org
Owner: msarda@chromium.org
Mihai: could you triage this bug. It seems like issue happens during sign-in flow. I'm not sure what extra information you'll need, maybe network trace?

I tried to reproduce this issue , but it worked as intended. I got to sync confirmation dialog and about:signin-internals showed that account is signed in.
I ran chrome 57.0.2987.8 with parameters from https://sites.google.com/a/google.com/chromesync/the-sync-server/run-with-gaia-staging

Comment 2 by msarda@chromium.org, Jan 25 2017

Status: Started (was: Untriaged)
I have tried to reproduce this yesterday and I managed to hit a DCHECK 5-10 seconds after the sync confirmation was shown. It looks like a timeout is firing at at unexpected time.

I did not yet have time to figure out entirely why that timeout fired.

Comment 3 by jnaveen@chromium.org, Feb 1 2017 

The original bug reported in comment #0 is no more reproduced. I am able to sign in to Chrome and sync data successfully between two chrome clients. Is anything fixed here?

Comment 4 by msarda@chromium.org, Feb 2 2017 

I have not done any work to fix it. Are you testing on corp network?

Comment 5 by jnaveen@chromium.org, Feb 2 2017 

Yes, I had tested on corp network.

Comment 6 by msarda@chromium.org, Feb 3 2017

Status: WontFix (was: Started)
It looks like this got fixed somehow (per comment #3).
►

Sign in to add a comment