microg / microg/GmsCore

[0.3.2.240913-hw] getDeviceID failed (Some apps fail to log in using Google)

Open
#2,384 1 comment 0 reactions 0 assignees View on GitHub

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: All Play Games dependant applications (example: PUBG MOBILE)
Package id: example: com.tencent.ig

Describe the bug
Inside an application, which requires Play Games authorization/manual login via GMS onboarding, it falls under a condition, where "Failed to find Google Services" or "Google Play games inaccessible" type errors appear

To Reproduce
Steps to reproduce the behavior:

  1. Have Play Games and microG-hw installed on device
  2. Go to PG dependant application, and tap on log in

Expected behavior
User will expect a "Select account" dialogue, where further steps will be taken

Screenshots
Screenshot_20240524_214952_com f0x1d logfox

System
Android Version: 12 (Sv1/Pre-QPR; API 31)
OEM ROM: EMUI 14.2/HarmonyOS 4.2 (HUAWEI System Image 104.2) on HUAWEI P60 (LNA) with SM8475

microG
microG Self-Check results:
Screenshot_20240524_215401_com google android gms
Screenshot_20240524_215403_com google android gms

Additional context
Add any other context about the problem here.

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 Play Games login failure on the listed Android 12 and Huawei setup, then trace the getDeviceID and GMS onboarding entry points named in the report. Compare the observed errors with the expected account-selection dialogue; the issue is done when affected Play Games-dependent applications can proceed through login.

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
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.