So it’s fixed or not?
Pics of your repo order setup?
Pics of app details in F-Droid with Versions expanded?
Seems like it does, f-droid shows it just as regular update (before that it was warning about incompatible signature for some reason), but giving error “Not installed” every your try of updating it.
microG repo was deleted and then added back again to avoid showing it under the name “UnifiedNlp (no GAPPS)” instead of the “microG Services Core”, so it’s placed at first (at the bottom).
1 Like
Is that what you meant?
But here is more detailed info about installed version and .apk from github or microG site:
2 Likes
Hey thanks @Danko for joining! And yes, confirmed from me too that new repo still gives the same error. BUT are we sure the problem is signature? Because here they say the problem is about redirecting. (@Licaon_Kter is actually in this subject)
Ah, and @SkewedZeppelin , not sure if you read my question, but if gps isn’t a google thing, do you have an idea of how to implement location services on this 8.1 without google services? Would be great to have this since it’s the whole point of why I’ve opend this post. (edit: i think you might be refering to apps, which do work without google, but I am referring to browser/websites using gps/location, sorry for the inconvenience)
I seem to have misunderstood your first post. Sorry.
1 Like
Today’s morning the problem was finally (I’m not sure) gone and update works — those redirection in microG repo was temporarily disabled, as main developer said.
1 Like
Works!
Big thanks @Danko and @Licaon_Kter (and all the others)
Ah, and for those testing location in a browser, duckduckgo did not work (as nicely neglected in this post) but Fennec browser did work.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
I’ve just updated f-droid app from 1.15.6 to 1.16 and facing again probably those old annoying bug with signature incompability, but now it’s definitely on f-droid’s side, not on microg repo.
By the way, app can’t be downgraded back due to the “Error -25: new package has older version code than currently installed package”. But seems like it’s caused by LOS4microg ROM in my case, in which f-droid is preinstalled as a system app.
That’s an Android feature, not sure any ROM in the recent history allowed downgrades.
O.K. If so, but what’s the solution? wait for the new build of f-droid?
Picture App Manager Signature of the installed microg pls?
It’s from official microg repo, was installed and updated from f-droid last times without any problems (except one bug in October, mentioned earlier).
Indeed it is 
Any suggestions?
After updating f-droid on another device to the latest stable 1.16.1 ver. I get the same issue with sudden microg “incompability”, but it’s definitely some weird bug due to the new build of f-droid.
This thing you need to find out: how does your ROM implements signature spoofing. Then you can make your MicroG work right.
The most recent signer bug has nothing to do with microG but broke with some changes (probably this → https://github.com/f-droid/fdroidclient/blob/master/CHANGELOG.md#116-alpha0-2022-12-02) introduced in F-Droid 1.16
I just came across an old R/11 emulator image w/ microG in my Android Studio installation (for a completely different reason) and decided to try to reproduce this by updating the F-Droid client incremental until things break:
Version is left to right 1.14 → 1.15.6 → 1.16 → 1.16.1 (latest)
I also enabled Force old index format in 1.16.1 and updated the repos but to no avail.
Downgrading F-Droid to 1.15.6 (from https://f-droid.org/repo/org.fdroid.fdroid_1015056.apk) using adb
adb install -r -d org.fdroid.fdroid_1015056.apk
fixes this, tho you lose all your custom repos, probably for the same reason.
Cheers
@defkev this message would be super useful to have as an issue, so we can track it: Issues · F-Droid / Client · GitLab