Android Studio doesn't generate signed apk after update to 2.3

Question

I have faced some troubles with uploading release version to fabric(crashlytics) after generating release build in Build->Generate Signed Apk. After moving app-release.apk into Fabric window I see following error: "The provided APK can't be distributed because it is unsigned."

Fabric error

What I'm doing wrong? Keystore and its password didn't change.

Have you zip-aligned the apk? Also disable Instant Run before signing your apk — Eenvincible, Mar 13 '17 at 13:55

score 20 · Accepted Answer · answered Mar 13 '17 at 13:56

20

I had the same problem yesterday.

I had to make sure the checkboxes for signature versions where both checked. These both are unchecked by default.

answered Mar 13 '17 at 13:56

Ruben Aalders

624
6
20

Yes, surprisingly, I had this too happen after upgrade; – Eenvincible Mar 13 '17 at 13:57
Thank you very much, Ruben. You saved my day. – trueangle Mar 13 '17 at 14:04
You are welcome. Please accept my answer when possible :) – Ruben Aalders Mar 13 '17 at 14:04
I have the same problem, but even after checking two check boxes for signature version, signed apk doesn't appear. :( – Lucky_girl Mar 14 '17 at 20:54
just app-release.apk and and app-debug.apk – Lucky_girl Mar 14 '17 at 21:01
Okay, I realized, that it's possible to zipalign app-release.apk, and then Google play it accepts. – Lucky_girl Mar 14 '17 at 22:11
I cannot select it :/ – Mladen Rakonjac Apr 05 '17 at 09:39

score 0 · Answer 2 · answered Jul 24 '17 at 13:50

Just try to add this:-v2SigningEnabled false in your build.gradle.

android {
    ...
    defaultConfig { ... }
    signingConfigs {
      release {
        storeFile file("myreleasekey.keystore")
        storePassword "password"
        keyAlias "MyReleaseKey"
        keyPassword "password"
        v2SigningEnabled false
      }
    }
  }

After then select

Android Studio doesn't generate signed apk after update to 2.3

2 Answers2