Yes! That solves the issue, thanks a lot!

As for your questions:

description says Android 5 or higher. v2 was IMHO introduced with MM.
I didn't install it – as I wrote, it was apksigner which complained.

So why apksigner? Well, I check apps from "unknown sources" against different sources. And as your Readme writes "F-Droid: soon™", I thought I'd help that a little and get it into "staging"; so in less than 22h it should turn up here – where it can be installed (and kept up-to-date) with the F-Droid app directly from the Android device. Congrats: Grocy is app number 500 there and thus made the repo break a new record 😄

Disclosure: I'm also one of the F-Droid maintainers. When you want to bring your app to f-droid.org I gladly assist. My scanners all approved – but they admittedly didn't check for "blobs" or "untrusted Maven" etc. in your repo.

I'm closing this issue as it is solved (updates will be fetched automatically within 24h whenever you create a new tag and attach an APK to it). Feel free to ping me from another issue should you need help getting the app to f-droid.org – or simply go straight to open an RFP, which will ping me automatically (that's where I'm "maintaining").

Thanks again!

PS: If you wish to link to your app in my repo, here's a badge for that 😃

Sign release APK with signature v1 and v2 #4

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions