Skip to content

Failing to verify signature with Öffi repo

  • Device OS and version: i ) AospExtended-v5.0-ALPHA (Android 8.0.0) no root access ii) crDroid 4.0 (Android 8.1.0) root access via Magisk v15.3
  • Device model/manufacturer: i ) Motorola Moto G5 (cedric) ii) OnePlus 5T (dumpling)
  • F-Droid version (in the About screen): 1.0.2 in both cases
  • F-Droid privileged extension version (if installed): i ) n/a ii) 0.2.7

What did you do? (clear steps if possible) What did you see?

I added the repository https://oeffi.schildbach.de/fdroid/repo A few seconds after that and everytime I de- and re-activate it, I get an overlay notice "The Repository was not signed correctly: Signing certificate does not match!". Consequently, I do not get to see Öffi to install it.

I did try "Force old index format", but it did not help.

What did you expect to see instead?

Less error messages, more Apps. :)

The last time I installed Öffi via F-Droid successfully was at least a few months ago.

  • always on manufacturer-provided OSs
  • always < Android 8 (maybe < 7, even)
  • might have always been pre-F-Droid_v1.0

Unfortunately, I have no device with its manufacturer-provided Android at hand. I wish, I'd have tried with the 5T, before I wiped it clean, but aside from enjoying facerecognition for a bit wiping it clean was the first thing I did.

This might not be an F-Droid issue, but I don't find a way to contact Andreas "Öffi" Schildbach. (Google+ doesn't count.)

Can anyone exclude Android 8+ or F-Droid 1+ or the Öffi repo from my set of suspects? Is their a way to investigate this? I cannot find something useful for this in F-Droids UI. I wouldn't shy away from tackling this with Termux and root access, if that helps - just need directions.

Regards, Djoga'Ro

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information