F-Droid: GmsCore invalid signature
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
Installing GmsCore from the MicroG F-Droid repository fails due to a signature mismatch
To Reproduce
Steps to reproduce the behavior:
- Use a non-official F-Droid client such as Droid-ify or Neo Store (See below for why F-droid is excluded.)
- Install GmsCore from the MicroG F-Droid repository
- See error: 'Could not validate microg Services Core: Invalid signature.'
Expected behavior
GmsCore installs from F-Droid as expected
System
Android Version: 13
F-Droid: 1015056
Additional context
The regular F-Droid client does not care about the signature: No versions with compatible signature, as for another F-Droid client such as Droid-Ify, Neo Store, etc - it does and fails installation due to a checksum mismatch. This could be a repository problem.
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 installation through a non-official F-Droid client such as Droid-ify or Neo Store, using the MicroG F-Droid repository and Android 13. Compare the repository signature with the installed GmsCore package and verify that installation completes without the invalid-signature or checksum-mismatch errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100