GmsCore icon indicating copy to clipboard operation
GmsCore copied to clipboard

[com.android.chrome] Chrome doesn't log in to existing / new account

Open FrzMtrsprt opened this issue 4 years ago • 8 comments

Affected app Name: Chrome Package id: com.android.chrome Version: 88 / 89 / 90

Describe the bug When trying to log into Chrome, it prompts me to sign into a new account instead of logging into an existing account. This happens no matter if I have added a Google account in microG in advance.

To Reproduce Steps to reproduce the behavior:

  1. Log into a Google account in microG
  2. Open Chrome's setting page, and click "Sign in to Chrome", then click "Add account"
  3. microG's sign in screen shows up
  4. "This account is already on your device"

Expected behavior Clicking "Sign in to Chrome" should sign me in directly.

Screenshots No

System Android Version: 8.1 / 11.0 Custom ROM: LineageOS 15.1 / LineageOS 18.1

microG microG Core version: 0.2.17 / 0.2.18 microG Self-Check results: All ticked

Additional context Signing into Chrome used to work on the same device with the same rom, and this issue appeared somewhere around Chrome 87. I don't know if this matters but on LineageOS 15.1, the signature spoofing feature was enabled by the Nanodroid patcher.

FrzMtrsprt avatar Apr 20 '21 06:04 FrzMtrsprt

Screenshot_20210420-090025_microG_Services_Core

both enabled?

RobertoWa avatar Apr 20 '21 07:04 RobertoWa

both enabled?

Yes

FrzMtrsprt avatar Apr 20 '21 07:04 FrzMtrsprt

So I just tried logging into my account in Chrome 85 which was successful. Then I installed Chrome 90 on top of that, and my account disappeared when I opened Chrome. What happened?🤔 Edit: I tried all the big versions between 85 and 90, most of them were downloaded from APKmirror, single APK. All the versions before 89 worked, but 89 and 90 didn't work. Is it related whether the installation package is a single APK or spilt APKs?

FrzMtrsprt avatar Apr 20 '21 07:04 FrzMtrsprt

I have the same problem on two of my devices, a Nexus 5X running LineageOS 17.1 and a Galaxy TAB S2 running Lineage OS 16. Chrome sync was working and stopped after an update. Chrome is installed and updated through Aurora Store but after the problem first occurred I've tryed installing several versions both as single and split APK.

bluray93 avatar Apr 23 '21 06:04 bluray93

Not an answer, why use Chrome in the first place? Try Bromite, Fennec or Brave

mizzunet avatar Jul 01 '21 21:07 mizzunet

Same problem here. OPPO Watch 4 Pro (OWW221) running ColorOS for Watch 6.0 (Android 11) with microG 0.2.28.231657 (231657056). Chrome version 117.0.5938.60 (593806020). Signature spoof by modify target apk to PackageManager reflection hack.

MlgmXyysd avatar Sep 13 '23 15:09 MlgmXyysd

Anyone solved this?

GuyZhangZhang avatar Apr 18 '24 04:04 GuyZhangZhang

Hi, I have tested GmsCore v0.3.2.240913 and on Chrome 126, sync works (bookmarks etc) except for passwords.

On Chrome Beta 127 and Chrome Canary 128, the device is unable to log in to existing accounts. "Turn on sync" directs to the add account menu, which eventually fails as account has already been added.

Do you have any idea why password sync is not working on Chrome 126? This feature is quite important. Thanks :)

AndrewKeYanzhe avatar Jul 07 '24 07:07 AndrewKeYanzhe