Hash mismatch failure F-droid client, microG repo, GmsCore 0.3.10
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
When attempting to update GmsCore 0.3.9.250932 to 0.3.10.250932 via official F-droid client and using the microG F-droid repo, receiving "Hash not matching" errors despite multiple attempts.
To Reproduce
LineageOS 22.2 (Android 15)
F-droid client 1.23.0
microG Self-Check: all ticked except "interact with work profile" (There is no work profile on this device)
With all microG repo hosts enabled in F-droid, receive the following error:
"Download failed!"
"Hash not matching"
This remains true if I solely enable either the "media.Githubuser content..." or "raw.Githubuser content..." mirrors.
If I solely enable the "microg.org" mirror, I get a 404 error instead.
Version 0.3.9 was installed as an update of 0.3.6 using files directly downloaded from the Github releases page.
Expected behavior
App updates without errors.
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
No source files or tests are identified in the report. Start by reproducing the update with LineageOS 22.2, Android 15, F-Droid 1.23.0, and the listed microG repository mirrors, then trace the download and hash-validation path. Done means the GmsCore update completes without a hash-mismatch or mirror 404 error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100