microg / microg/GmsCore

Play Integrity is broken

Open
#2,855 8 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

To reproduce
Steps to reproduce behavior:

  • Check through any checkers/error in apps requiring game integrity.

Expected Behavior

  • SafetyNet walkthrough

Screenshots

Screenshot_2025-04-09-18-37-01-193_com.google.android.gms.jpg

Screenshot_2025-04-09-18-35-06-454_com.henrikherzig.playintegritychecker.jpg

Screenshot_2025-04-09-18-36-38-519_com.openai.chatgpt.jpg

Screenshot_2025-04-09-18-34-26-485_com.google.android.gms.jpg

Screenshot_2025-04-09-18-34-22-211_com.google.android.gms.jpg

System

  • Android Version: HuperOS 2.0.200.2 A15

Additional Context

  • Also tried putting both the microG/Companion version release. And from the main branch from the git repository (build). The result is the same. Also versions with the main branch became less stable when installing to the system partition (frequent bootloops)

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

No source file, test, or entry point is identified. Reproduce the Play Integrity checks on HuperOS 2.0.200.2 A15 using the reported microG versions and compare the results with the screenshots. A concrete fix still needs a defined expected behavior for the SafetyNet walkthrough.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
mobile, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.