[com.android.chrome] Chrome doesn't log in to existing / new account
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 3.2k
- Avg merge
- 12d 11h
- Merged PRs (30d)
- 4
Description
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:
- Log into a Google account in microG
- Open Chrome's setting page, and click "Sign in to Chrome", then click "Add account"
- microG's sign in screen shows up
- "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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the flow from Chrome settings: choose “Sign in to Chrome,” select “Add account,” and observe microG’s sign-in screen reporting that the account is already on the device. Compare this behavior across the listed Android, Chrome, and microG versions; done means an existing Google account can sign in to Chrome without being prompted to add it again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- authentication, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100