Signature key fingerprint of file 'stats/publishsigkeys.jar' does not match repo_key_sha256 in config.py
The publish test failed on jenkins. My guess is that this is because the test runs are not preserving the keyring between build runs, but someone some other piece got preserved.
@uniqx how do you think we should handle this in the tests? Should each test run just start out by deleting stats/publishsigkeys.jar or all of stats/?
$ fdroid update --nosign
WARNING: us.dangeru.la_u_ncher413_414.apk (us.dangeru.la_u_ncher413) has no metadata!
Use `fdroid update -c` to create it.
CRITICAL: Signature key fingerprint of file 'stats/publishsigkeys.jar' does not match repo_key_sha256 in config.py (found fingerprint: 'b072129cbb36e8f0cb3b210bc388d41779e6c67c7333d3872a2f8e469eba1c7f')