APKs signed with debug key? about chrono HOT 6 CLOSED

I fixed the versioning issue to what you suggested as well.

Great, thanks! That will make it easier to switch between armeabi and arm64, both directions (e.g. to some 32bit backup device while the 64bit one is in for repair). For this one time it will mean people having installed it from my repo will have to uninstall and reinstall (as versionCode decreased), but that won't affect too many people as you acted right away. Would have been harder had we waited a couple of weeks. And was needed for F-Droid.org anyway 🤷‍♂️

Currently facing some issues in getting the builds to be reproducible but working on that.

That Howto-link above will be a great help with that. Helped me more than once, and I'm very thankful to @obfusk for providing it! You can find the original here which probably will receive updates earlier (should there be any), as Fay is the expert on that.

from chrono.

Yes, I've signed them now, are they OK?

from chrono.

Yes, that looks good now, thanks! Will be helpful if you establish reproducible builds with F-Droid (which they should not allow with debug keys).

Speaking of that listing: mind to include some screenshots with your fastlane structures? You know, first impression and all that 😉 Meanwhile, with the next sync around 7 pm UTC, your app will become available here.

from chrono.

@IzzySoft Thanks. Uploaded the screenshots.

But I am confused on what the next steps are since I have never uploaded to FDroid before. Should I create the merge request next? I have followed the merge request guide and written a metadata file. But I am facing some uses when I push it to my fork (CI is failing). I have created an issue here. Maybe you can help? 😄

And I am guessing after CI is passing, I compare the apks in my Github release to the one created by the CI using diffoscope? If there is no difference, that means the build is reproducible?

from chrono.

Uploaded the screenshots.

Thanks! Enabled them on my end, manually triggered a "fastlane pull" – they'll show up with the next sync then.

But I am confused on what the next steps are since I have never uploaded to FDroid before.

For a "quick guide", you can take a look at my snippet under Quick path to get your app into F-Droid. I'm currently not active at F-Droid, so I cannot help out at their end.

As for reproducible builds: yes, basically. If you need details on those:

• HOWTO: diff & fix APKs for Reproducible Builds
• Reproducible builds, signing keys, and binary repos

Concerning your versioning, I'm a bit confused about this line in your pubspec.yaml:

version: 0.2.5+1

That basically means you're still setting versionCode to 1 (and indeed, your arm64 build carries "2001"). This will need multiple adjustments: first, each release must have versionCode increased. Second, if you wish to ship multiple ABIs at F-Droid, you cannot use Flutter's defaults for that (which puts the ABI at the highest bit, e.g. adds 2000 for arm64) but need to have the ABI at the lowest bit, e.g. versionCode * 10 + ABI to add 1 for armeabi, 2 for arm64 – turning 0.2.5+1 into 21 and 22 respectively. I don't remember how that's done, I'm not an Android or Flutter developer – I just know it is possible. Some of the other Flutter apps at F-Droid might give you a clue at that.

from chrono.

Concerning your versioning, I'm a bit confused about this line in your pubspec.yaml:

version: 0.2.5+1

That basically means you're still setting versionCode to 1 (and indeed, your arm64 build carries "2001"). This will need multiple adjustments: first, each release must have versionCode increased. Second, if you wish to ship multiple ABIs at F-Droid, you cannot use Flutter's defaults for that (which puts the ABI at the highest bit, e.g. adds 2000 for arm64) but need to have the ABI at the lowest bit, e.g. versionCode * 10 + ABI to add 1 for armeabi, 2 for arm64 – turning 0.2.5+1 into 21 and 22 respectively. I don't remember how that's done, I'm not an Android or Flutter developer – I just know it is possible. Some of the other Flutter apps at F-Droid might give you a clue at that.

Thank you! I fixed the versioning issue to what you suggested as well.

Currently facing some issues in getting the builds to be reproducible but working on that.

from chrono.