Open apprehensions opened 1 year ago
Fresh.
Dude. You're missing the main issue, it is related to F-Droid installation failing on third party clients.
You can only update the microg with the official microG build. Some custom roms (omnirom, /e/OS,...) have a own build with own signature.
@apprehensions
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.
Actually it is the opposite, if it say "No versions with compatible signature" it mean that it care about the signature. If another client try to update even if the signature is different then it is bugged.
this occurs when signature spoofing for microG is unavailable because F-Droid sees the real microG signature whereas the repo metadata has the Google signature to ensure updates work once spoofed.
Describe the bug Installing GmsCore from the MicroG F-Droid repository fails due to a signature mismatch
To Reproduce Steps to reproduce the behavior:
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.