What do I need to do to make the GMSCore apk compiled by Android Studio pass the signature deception?
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 3.2k
- Avg merge
- 12d 11h
- Merged PRs (30d)
- 4
Description
Describe the bug：
I used a OnePlus phone to flash the crdroid system, and then installed the source code compiled apk, but the self-check showed that the signature deception did not pass. However, I installed the downloaded release version and it showed that the signature deception passed.
What do I need to do to make the GMSCore apk compiled by Android Studio pass the signature deception?
My own compiled apk
Download release apk
Mobile phone system
System
Android Version: 14
Custom ROM: crDroid 10.10
microG
microG Core version: 0.3.5.244735-3
microG Self-Check results: Partially checked
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
The report identifies an Android Studio-built GMSCore APK, a downloaded release APK, and crDroid 10.10, but no source files or tests. Start by comparing the build and signing configuration for the two APKs, then reproduce the microG Self-Check result on Android 14. Done means the Android Studio build passes the signature-deception check.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100