-
Notifications
You must be signed in to change notification settings - Fork 6
Signing issues? #2
Comments
My bad ! The apk has been signed but i forgot to specify that the certificate has changed, uninstall the old version ;) |
Thanks for the fast response! But I didn't even have the previous version. The latest one doesn't seem to be signed at all (that error is thrown when I try to integrate the APK with my F-Droid repo). |
🤔 The apk has been signed however. |
Thanks! That one throws a lot of warnings, but no error anymore:
to get rid of those warnings you could probably just remove those files on build. I vaguely remember there was some gradle setting even. Btw: What license is the app using? |
Gooood ! I will investigate these warnings ! It seems that it can be adjusted thanks to that
Thanks ! |
I knew there was a way to fix that via gradle. Good you found it! Are you planning for a license at least? No license is … hm, well, maybe "dangerous" is a too hard word, but that direction. Might attract trouble. And makes some people nervous 😉 PS: Gladys is now available via my repo. Cannot further it to the official F-Droid repo to to the GMS component – but as long as you attach a working |
I know but I have not yet taken the time to think about the appropriate license! Awesome ! For me it's ok ^^ |
Just ping me please if you've decided on the license (so I can update that information in my repo). If you have a flavor without GMS, we could try to get your app into the official repo; feel free to ping me on that then as well. |
No problem ! |
With the latest APK from
releases/
I get:Did you incidentally not sign it, or just forgot to? In the latter case: could you please do sign the releases?
The text was updated successfully, but these errors were encountered: