After updating android studio to version 3.0 (windows), I am unable to generate a signed APK.
When build has completed, i get the message:
Clic
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.
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
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
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.
In my case I found apk file in folder {specified_destination}/{flavor_name}/release folder
Sahil Kapoor was almost on mark:
The generated file's path is your specified destination folder + {flavor}/{variant}/
{destination} / {flavor} / {variant} / {apkname}.apk