After quite a long time (about 2 years) we updated our app (RUTMath, com.hexbit.rutmath) to version 0.2.1 but unfortunately F-Droid didn’t detect the update.
What is the correct way to investigate the cause of this issue?
not sure, from checkupdates_runner 3/10 (#10956698203) · Jobs · F-Droid / checkupdates-runner · GitLab
2025-08-08 04:29:33,186 INFO: Processing com.hexbit.rutmath
2025-08-08 04:29:48,071 ERROR: Environment variable {env: serverwebroot} is not set!
2025-08-08 04:29:48,071 ERROR: serverwebroot: has blank value!
We already have this version code: RUTMath/androidApp/build.gradle at v0.2.1 · przemarbor/RUTMath · GitHub
Maybe if you bump these 2 and retag… 
1 Like
You changed your signing key? 
First of all, I apologize for the late reply.
Secondly, can I write here for the help with the signing key or should I start a new thread?
Do explain here…
OK. To put things straight… I am the originator of the project.
The program was developed by several students.
Two years ago, one of them took charge of the matter and was the one who submitted the application to F-Droid via this fork.
Additionally, he configured the GitHub workflows on our side so that the entire F-Droid update process would run automatically after properly tagging a commit. This worked excellent and I didn’t need to get too involved in the technical details of synchronization between our repo and F-Droid.
But contact with this person was lost and in the meantime, other people made further changes that we now wanted to publish as a new version. Unfortunately, the entire automatic update process stopped working, but before we fix it, I would like to get this new version on F-Droid right away.
So, I ended up having to learn all of the stuff, but I’m starting almost from the scratch…
Your comments made me aware that I need to update not only
/metadata/com.hexbit.rutmath.yml
but also
androidApp/build.gradle
Thanks.
When it comes to signing keys… If you could provide any hints where to start from on this matter… Honestly, I guess we didn’t change it, or to put it clearer: I’m not aware of changing the key.
However we made quite significant changes recently in the project, namely we moved from Kotlin to Kotlin Multiplatform. Is it possible that this is what caused the key to change?
no, the key is something separate that you need to keep safe, eg. see Reproducible builds, signing keys, and binary repos | F-Droid - Free and Open Source Android App Repository
$ wget https://github.com/przemarbor/RUTMath/releases/download/v0.2.1/androidApp-release.apk
$ apksigner verify --print-certs --verbose androidApp-release.apk | head
Verifies
Verified using v1 scheme (JAR signing): true
Verified using v2 scheme (APK Signature Scheme v2): true
Verified using v3 scheme (APK Signature Scheme v3): false
Verified using v3.1 scheme (APK Signature Scheme v3.1): false
Verified using v4 scheme (APK Signature Scheme v4): false
Verified for SourceStamp: false
Number of signers: 1
Signer #1 certificate DN: C=US, O=Android, CN=Android Debug
Signer #1 certificate SHA-256 digest: 8cff2bca460cedca0698752dba73389652f1c29aae8e92db3256ccc0a01f7b10
looks like your CI signed with a debug key and not your proper key
so… fix that
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.