CODEWITHSUNDEEP
androidandroid-studioapk
JPJens
JPJens

Reputation: 1205

Android studio 3.0 does not generate signed apk

After updating android studio to version 3.0 (windows), I am unable to generate a signed APK.

enter image description here

When build has completed, i get the message:

enter image description here

Clicking "Locate" brings me to the APP folder, but there is no APK to be found.

What has been changed ?

Upvotes: 46

Views: 28929

Answers (9)

Vishv Shroff
Vishv Shroff

Reputation: 71

Okay for me this thing works :

  1. Check the folder in which the apk is going to generated. Normally it will be the Android Studio Project > app > release
  2. If this folder is having "app-release.apk" then remove the same and try to regenerate the signed apk.

Upvotes: 0

Soy César Mora
Soy César Mora

Reputation: 277

In my case all is correct but android studio is not generated the APK and i'm not getting an error message.

Previously i was update my package name com.test.package > com.final.name.package using refactor all works fine even create an not signed APK.

Finally i can see that my applicationId inside the gradle has the old package name, when change it for the new package name the signed APK is generated without problems.

Upvotes: 0

Shai Epstein
Shai Epstein

Reputation: 189

I had the exact issue after upgrading to Android studio 3.0 (windows)

After spending HOURS looking for the solution, I find out that, that simple action solved it for me:

changing the destination path apk to different path. (for me to C:) just solved it

Generate Signed APK dialog

Upvotes: 8

WallMobile
WallMobile

Reputation: 1959

Another thing is that Android Studio 3.0 will make it an .aab file which is an app bundle file. This enables you to have the code signing in google play, so you don't have to have the key locally. There is an answer here on how to do that. How to enable Google Play App Signing Seems to be a step in the right direction, even if it is not very clear when actually doing it.

Upvotes: 0

Niraj Sanghani
Niraj Sanghani

Reputation: 1493

Since Android Studio 3.0 update, the apk generated will be in

{project-folder}/app/release/app-release.apk

Also 1 more file is generated Output.json which holds the apk generation details.

Sample:

[  
   {  
      "outputType":{  
         "type":"APK"
      },
      "apkInfo":{  
         "type":"MAIN",
         "splits":[  

         ],
         "versionCode":1
      },
      "path":"app-debug.apk",
      "properties":{  
         "packageId":"njscommunity.xxxxx",
         "split":"",
         "minSdkVersion":"19"
      }
   }
]

All depends on Gradle build, so at the end it all depends on Gradle version you build with. i.e. Gradle Android plugin for Android Studio.

Upvotes: 68

Sahil Kapoor
Sahil Kapoor

Reputation: 614

Android Studio 3.0 Now creates a "release" folder inside the specified destination folder and places the release apk inside that.

{APK Destination Folder}\release\app-release.apk

OR as mentioned by @velis

{APK Destination Folder} \ {flavor} \ {variant} \ {apkname}.apk

For Example:- In your case: C:\apps\app\release\app-release.apk

Upvotes: 29

Oleksandr
Oleksandr

Reputation: 1502

In my case I found apk file in folder {specified_destination}/{flavor_name}/release folder

Upvotes: 12

velis
velis

Reputation: 10025

Sahil Kapoor was almost on mark:

The generated file's path is your specified destination folder + {flavor}/{variant}/

{destination} / {flavor} / {variant} / {apkname}.apk

Upvotes: 2

TonyL
TonyL

Reputation: 115

I have faced the same problem. After a few hours downgrading

classpath 'com.android.tools.build:gradle:3.0.0'

to

classpath 'com.android.tools.build:gradle:2.3.3'

solved the issue in the build.gradle file.

Upvotes: 2

Related Questions