Does any one have ideas on why gradle could produce an unsigned apk? I do properly setup signing con...

# android

[dimsuz]

Does any one have ideas on why gradle could produce an unsigned apk? I do properly setup signing configs, I checked and rechecked. I even diffed my build.gradle with another project which has exaclty same signing configs and produces a signed apk, but this one isn't.

$ jarsigner -verify /path/to/apk

jar is unsigned

[dimsuz]

OK. Just found that downgrading minsdkversion to 23 (was 25) makes jar signed again

[jw]

this is not related to Kotlin so you should ask on StackOverflow

[jw]

you should be using apksigner to validate an apk, not jarsigner

[dimsuz]

OK, sorry.

[dimsuz]

I would, but it seems crashlytics uses jarsigner, because it rejects my apk

[jw]

you should reach out to their support and tell them that they're doing it wrong

[dimsuz]

This is the plan, now that I just found out what causes this 🙂

[jw]

There's more details at https://source.android.com/security/apksigning. v1 is only needed for old API levels and is not done by default for higher ones

[dimsuz]

I tried to enable it explicitly, but it still failed to upload for some reason, maybe I've messed up something