microg / microg/GmsCore

The GmsClient: unable to connect to service: com.google.android.gms.auth.api.signin.service.START on com.google.android.gms happens on v0.2.23.214816

Open
#1,646 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Java
Stars
14.6k
Forks
3.2k
Avg merge
12d 11h
Merged PRs (30d)
4

Description

When trying to login with your google account on a native app you get the error The GmsClient: unable to connect to service: com.google.android.gms.auth.api.signin.service.START on com.google.android.gms

Steps to reproduce the behavior:

  1. Install 9gag
  2. Login with google account

Expected behavior
Should login with the configured google account

Screenshots
Hard to make a screenshot since you see a screen flashing for a few ms

System
Android Version: 11
Custom ROM: Lineage 18.1 microG (guacamole)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Google login failure on Android 11 with Lineage 18.1 microG, following the listed 9gag login steps and observing the GmsClient error. Done means a configured Google account can complete login without the service connection failure.

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
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.