Hello,
I am currently planing to bring my app (GitHub - Drexel2k/OpenEatsJournal: Open Eats Journal is a free, data minimized and privacy friendly open source eats journal to track your food intake, nutritions, calories and weight. · GitHub) to F-Droid. I have already a signing key and a keystore for the Google Play Store.
Shall I reuse it or is it better to create a new one for F-Droid? Any recommendations/best practices?
Thanks for any help!
we encourage repro builds so we host the upstream APK: Submitting to F-Droid Quick Start Guide | F-Droid - Free and Open Source Android App Repository
but looking at Releases · Drexel2k/OpenEatsJournal · GitHub I don’t see you publish your signed APKs?
No I have nothing done yet, I am still in the state of reading and gathering information.
I am following this tutorial: How to Publish Your Flutter App on F-Droid - DEV Community
There I need a signing key to sign the APK…
Ok, when I read here:
This approach allows publishing both APKs signed by the (upstream) developer and APKs signed by F-Droid. This enables us to ship updates for users who installed apps from other sources than F-Droid (e.g. Play Store), while also shipping updates for apps which were built and signed by F-Droid.
it seems valid and reasonable to use the same signing key.