-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Alternative Source #7
Comments
Thanks! Unfortunately
If you could fix that, I'd offer you to serve your app in my repo until you feel ready for the official one (being one of the F-Droid maintainers, I gladly help you with the RFP as well). |
The release is updated with JAR signatures.
Sure, Go for it! |
Thanks, added! Should show up here with the next sync (probably tomorrow 8pm). Hope you like the description then: your repo had none, so I needed to make one up 😄 From what my scanner said, your app should be eligible for the official repo. So just let me know if you want it listed there. |
I like the description; seems quite fitting.
Yes, for sure! |
Thanks! Here you go. Tonight the bot should check your repo and give a thumbs up (at least I hope so) – and then I'll mark it ready-to-build. Once it got picked up and merged, it should show up in the catalogue within a few days – which is when I'll remove it from my repo again (to avoid confusion, as the signatures won't match). |
PS: our bot found a security issue with your gradle you might wish to fix. Doesn't affect F-Droid, but your own builds. |
I see you already attach APKs to your releases, which is great – but unfortunately they are only debug builds. Would you mind using release builds instead? Or even have your app listed at F-Droid?
The text was updated successfully, but these errors were encountered: