New issue
Advanced search Search tips

Issue 841748 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 838576
Owner: ----
Closed: May 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

Cannot sign in to Chrome for Android

Reported by loorong...@gmail.com, May 10 2018

Issue description

Chrome Version       : 66.0.3359.158
OS Version: Android 7.0 (EMUI 5.1)

What steps will reproduce the problem?
1. Preparation: Android phone already connected to a Google Account (call it "X"), not sign in to Chrome yet.
2. Open Chrome.
3. Go to menu icon > Settings > Sign in to Chrome.
4. Choose Google Account X.

What is the expected result?
Choose Google Account X without having to type anything (since the phone is already connected to this account).

What happens instead of that?
Google Account screen appears and ask to "Add your account". After entering the email address of X, get "This account already exists on your device" error. 

Please provide any additional information below. Attach a screenshot if
possible.

Attached is the log file captured by "adb logcat". A lot of error about "com.google.android.gms.chimera". Some other apps such as Google Play Books (close immediarely upon launching), Google Assistant (unable to go to Setting) and DBS Paylah! (unable to scan QR code) are also started to fail with "com.google.android.gms" related errors in log file.

Google Play Service: 12.6.73 (040408-194189626).

UserAgentString: Mozilla/5.0 (Linux; Android 7.0; RNE-L22 Build/HUAWEIRNE-L22) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.158 Mobile Safari/537.36

 
Using Huawei Nova 2i.

My issue has similar log error as https://issuetracker.google.com/issues/65359941
Labels: Needs-Triage-M66
There are a few other Huawei users from Chrome Help Forum who also experienced the same issue.

https://productforums.google.com/forum/#!topic/chrome/MVpRFj7GAO8;context-place=forum/chrome
Components: Services>SignIn
Labels: Triaged-ET OS-Android
As per comment#0 this issue seems to be specific to OS=Android. Hence adding appropriate label.

Thanks!
Uninstalling all Google Play Services updates to pre-installed version, then use "adb install -r" to install 12.5.29 solves the issue. Hence this is not a Chrome issue, the real culprit is Google Play Services.
Mergedinto: 838576
Status: Duplicate (was: Unconfirmed)
Hey all,

We're already tracking this in  bug 838576 , so I'm going to merge this into there.

#5 - Would you be able to share your Google Play Services findings on the other bug?

Thanks for the report!

Sign in to add a comment