Where is android studio building my .apk file?

Question

I've been rebuilding my project from the ground up, so there's been a lot of problems with it. At the moment, everything's working great, except that when I try to run the app, I get the message 'Local path doesn't exist.', where the local path is pointing at the path: AndroidStudioProjects\MyProject\MyProject..\build\production\MyProject.apk, and true enough, there is no .apk file at that location, or indeed anywhere else in the project filesystem.

However, I can build the app with no problems, and running gradlew packageDebug gives me the message 'build successful', so .apks should be being generated. My question is, where are they going, or if they aren't being generated, why not?

Where is the build path of each module set? I'm somewhat confused because the Project Structure->Facets->Android->Compiler settings, Project Structure->Modules->Paths->Compiler Output, build.gradle, and MyProject.iml all seem to have something to do with the build path, but I don't quite understand how they relate

edit: I know where it should be, but it's not there so I want to know how to change the build path

edit 2: For some reason running gradlew build does create .apks, but not building or running from inside the program

edit 3: Here's my gradlew build output, note that it does build successfully:

Creating properties on demand (a.k.a. dynamic properties) has been deprecated and is scheduled to be removed in Gradle 2.0. Please read http://gradle.org/docs/current/dsl/org.gradle.api.plugins.ExtraPropertiesExtension.html for information on the replacement for dynamic properties.
Deprecated dynamic property: "target" on "com.android.build.gradle.LibraryExtension_Decorated@9e9aabc", value: "android-16".
:TwoWayLib:mergeReleaseProguardFiles UP-TO-DATE
:TwoWayLib:packageReleaseAidl UP-TO-DATE
:TwoWayLib:prepareReleaseDependencies
:TwoWayLib:compileReleaseAidl UP-TO-DATE
:TwoWayLib:generateReleaseBuildConfig UP-TO-DATE
:TwoWayLib:mergeReleaseAssets UP-TO-DATE
:TwoWayLib:compileReleaseRenderscript UP-TO-DATE
:TwoWayLib:mergeReleaseResources UP-TO-DATE
:TwoWayLib:processReleaseManifest UP-TO-DATE
:TwoWayLib:processReleaseResources UP-TO-DATE
:TwoWayLib:compileRelease UP-TO-DATE
:TwoWayLib:processReleaseJavaRes UP-TO-DATE
:TwoWayLib:packageReleaseJar UP-TO-DATE
:TwoWayLib:packageReleaseLocalJar UP-TO-DATE
:TwoWayLib:packageReleaseRenderscript UP-TO-DATE
:TwoWayLib:bundleRelease UP-TO-DATE
:Rogue:prepareRogueProjectTwoWayLibUnspecifiedLibrary UP-TO-DATE
:Rogue:prepareDebugDependencies
:Rogue:compileDebugAidl UP-TO-DATE
:Rogue:generateDebugBuildConfig UP-TO-DATE
:Rogue:mergeDebugAssets UP-TO-DATE
:Rogue:compileDebugRenderscript UP-TO-DATE
:Rogue:mergeDebugResources UP-TO-DATE
:Rogue:processDebugManifest UP-TO-DATE
:Rogue:processDebugResources UP-TO-DATE
:Rogue:compileDebug UP-TO-DATE
:Rogue:dexDebug UP-TO-DATE
:Rogue:processDebugJavaRes UP-TO-DATE
:Rogue:validateDebugSigning
:Rogue:packageDebug
:Rogue:assembleDebug
:Rogue:prepareReleaseDependencies
:Rogue:compileReleaseAidl UP-TO-DATE
:Rogue:generateReleaseBuildConfig UP-TO-DATE
:Rogue:mergeReleaseAssets UP-TO-DATE
:Rogue:compileReleaseRenderscript UP-TO-DATE
:Rogue:mergeReleaseResources UP-TO-DATE
:Rogue:processReleaseManifest UP-TO-DATE
:Rogue:processReleaseResources UP-TO-DATE
:Rogue:compileRelease UP-TO-DATE
:Rogue:dexRelease UP-TO-DATE
:Rogue:processReleaseJavaRes UP-TO-DATE
:Rogue:packageRelease
:Rogue:assembleRelease
:Rogue:assemble
:Rogue:check UP-TO-DATE
:Rogue:build
:TwoWayLib:mergeDebugProguardFiles UP-TO-DATE
:TwoWayLib:packageDebugAidl UP-TO-DATE
:TwoWayLib:prepareDebugDependencies
:TwoWayLib:compileDebugAidl UP-TO-DATE
:TwoWayLib:generateDebugBuildConfig UP-TO-DATE
:TwoWayLib:mergeDebugAssets UP-TO-DATE
:TwoWayLib:compileDebugRenderscript UP-TO-DATE
:TwoWayLib:mergeDebugResources UP-TO-DATE
:TwoWayLib:processDebugManifest UP-TO-DATE
:TwoWayLib:processDebugResources UP-TO-DATE
:TwoWayLib:compileDebug UP-TO-DATE
:TwoWayLib:processDebugJavaRes UP-TO-DATE
:TwoWayLib:packageDebugJar UP-TO-DATE
:TwoWayLib:packageDebugLocalJar UP-TO-DATE
:TwoWayLib:packageDebugRenderscript UP-TO-DATE
:TwoWayLib:bundleDebug UP-TO-DATE
:TwoWayLib:assembleDebug UP-TO-DATE
:TwoWayLib:assembleRelease UP-TO-DATE
:TwoWayLib:assemble UP-TO-DATE
:TwoWayLib:check UP-TO-DATE
:TwoWayLib:build UP-TO-DATE

BUILD SUCCESSFUL

Total time: 10.848 secs

possible duplicate of [Apk location in New Android Studio](http://stackoverflow.com/questions/16620366/apk-location-in-new-android-studio) — Gru, Jul 17 '13 at 14:42
it should be there as explained by Alex or else you can check above answer. — Gru, Jul 17 '13 at 14:43
http://stackoverflow.com/questions/16620366/apk-location-in-new-android-studio/29097183#29097183 — duggu, Mar 17 '15 at 10:51

score 205 · Answer 1 · answered Sep 29 '14 at 21:20

205

YourApplication\app\build\outputs\apk

answered Sep 29 '14 at 21:20

Mehdi Boukhechba

2,471
2
19
24

1

This is the new location. – Krylez Sep 29 '14 at 21:35
Thanks - I found it there for Android Studios 1.1 – Simon Apr 25 '15 at 16:46
in newer version, it is in YourApplication\app\build\outputs\apk\*.apk – Teerakiat Chitawattanarat Aug 17 '17 at 06:46
there is a folder named debug inside apk folder and in debug folder is an apk file named app-debug.apk along with a json file – sonu Dec 03 '18 at 17:37
don't forget to build the apk. – kelalaka Dec 28 '18 at 20:15
7

As of Jan '20: `YourApplication/android/app/build/outputs/apk/release/app-release.apk` – Ben Pritchard Jan 16 '20 at 01:32
is there any way to change it ? – Arda Kaplan Feb 24 '20 at 13:43
1

If you generated an Android App Bundle (AAB): YourApplication\app\release\app-release.aab – mystack Nov 13 '20 at 04:09

score 31 · Answer 2 · edited Mar 17 '19 at 17:32

31

You should Build your app instead of debugging process. Just follow this:

Build -> Build Bundles/APK(s) -> Build APK(s)

edited Mar 17 '19 at 17:32

Henry Woody

14,024
7
39
56

answered Jan 02 '19 at 06:26

Sajid khan

595
5
12

In case anyone wonders where the file winds up, as I did before I tried this, when the process is complete, there's a small dialog that comes up in the lower right corner of Android studio with a link you can click to open the folder in your file manager application (e.g., File Explorer in Windows). – hBrent Dec 06 '22 at 23:56

score 24 · Answer 3 · answered Mar 23 '15 at 03:49

24

Go to AndroidStudio projects File

Select the project name,
Select app
Select build
Select Outputs
Select Apk

You will find APK files of app here, if you have ran the app in AVD or even hardware device

answered Mar 23 '15 at 03:49

Manan Gupta

491
1
7
11

2

Strange, I am using Android Studio 3.2, in the build directory as you mentioned, there is only `intermediates` directory, the `Outputs` is missing. – Allan Ruin Dec 06 '18 at 11:46
@AllanRuin did you build the APK? – kelalaka Dec 28 '18 at 20:17
please be elaborative with the steps that you have mentioned. – Shubham Arya Dec 17 '19 at 17:00
1

@ShubhamArya and anyone else, make sure you are in Project view and not Android view in the project navigator then this will make more sense. – Panama Jack Nov 26 '22 at 10:41

score 24 · Answer 4 · answered Mar 13 '18 at 10:50

24

After compiling my code in Android Studio, I found it here:

~\MyApp_Name\app\build\outputs\apk\app-debug.apk

answered Mar 13 '18 at 10:50

Arsman Ahmad

2,000
1
26
34

score 11 · Answer 5 · answered Sep 05 '14 at 05:08

11

I was having the issue finding my debug apk. Android Studio 0.8.6 did not show the apk or even the output folder at project/project/build/. When I checked the same path project/project/build/ from windows folder explorer, I found the "output" folder there and the debug apk inside it.

answered Sep 05 '14 at 05:08

roshan213

243
1
5
13

Explorer crashes pretty hard if you have this location open and 'clean project' =) – J.G.Sebring Jan 21 '15 at 12:56
Can't believe I wasted so much time just because I forgot that just because Android Studio doesn't always show you all the directories... – Jon McClung Dec 19 '16 at 03:42

score 11 · Answer 6 · edited Sep 30 '22 at 11:33

11

For latest Android Studio Chipmunk|2021.2.1 Patch 2 the path to the Apk file is

MySampleAndroidApp\app\build\intermediates\apk\debug\app-debug.apk

edited Sep 30 '22 at 11:33

abdo Salm

1,678
4
12
22

answered Sep 23 '22 at 12:30

Jignesh Patel

189
2
8

giveJob · Answer 7 · 2019-02-15T14:13:13.767

10

in android 3.1.0 Above use below path to find signed version of APK

home/AndroidStudioProjects/<projedct name>/app/app-release.apk

and in windows

AndroidStudioProjects\{project name}\app\release\app-release.apk

edited Feb 15 '19 at 14:13

answered Aug 12 '18 at 07:09

giveJob

1,500
3
17
29

score 9 · Answer 8 · answered Feb 28 '16 at 01:04

9

For Android Studio:

If you haven't built the APK at least once, you might not find the /Outputs/APK folder. Go to Build in Android Studio and one of the last three options is Build APK, select that. It will then create that folder and you will find your APK file there.

answered Feb 28 '16 at 01:04

Jonathan

135
1
10

All the above didn't work for me and this one does. After `Build APK` it will also pop up a dialog telling you to `locate` your apk, how convenient! – Ng Sek Long Nov 14 '18 at 08:39

score 8 · Answer 9 · answered Jun 01 '20 at 13:24

8

You can find it in the

project -> app (or your main app module) -> build -> outputs -> apk

answered Jun 01 '20 at 13:24

Yvgen

2,036
2
23
27

This is the up-to-date one that actually works for me especially if you are looking for the release version. I am on Android Studio Dolphin | 2021.3.1 Canary 9. – Daniel Iroka Jun 21 '23 at 17:05

Alex Fu · Answer 10 · 2013-07-17T14:41:36.810

6

When Gradle builds your project, it puts all APKs in build/apk directory. You could also just do a simple recursive find command for *.apk in the top level directory of your project.

Here is a better description...

View full image at https://i.stack.imgur.com/XwjEZ.png

edited Jul 17 '13 at 14:41

answered Jul 17 '13 at 14:11

Alex Fu

5,509
3
31
40

Where is that directory defined? Because I can't find any apk files anywhere in my project filestsyem – Migwell Jul 17 '13 at 14:18
Like in my edit - I know where it *should be*, but it's not there, so maybe the output path is broken somehow? – Migwell Jul 17 '13 at 15:25
I've added it. The only dodgy thing is that my library TwoWayLib seems to be building twice. That doesn't explain why android studio can't build apks though – Migwell Jul 17 '13 at 15:40
I also have the same problem - neither Gradle nor Android Studio actually create an apk file. – Richard Russell Jul 30 '13 at 11:37

score 6 · Answer 11 · answered Feb 23 '18 at 11:07

6

Mine application's apk was at this location

C:\Users\haseeb_mir\AndroidStudioProjects\MyTestApp\app\build\outputs\apk\debug

answered Feb 23 '18 at 11:07

Haseeb Mir

928
1
13
22

score 4 · Answer 12 · answered Apr 26 '22 at 11:35

4

Android Studio BumbleBee 2021.1.1 Patch 3

Android Studio Bumblebee | 2021.1.1 Patch 3 Build #AI-211.7628.21.2111.8309675, built on March 16, 2022 Runtime version: 11.0.11+0-b60-7590822 x86_64

yourProject/build/intermediates/apk/debug/debug.apk

answered Apr 26 '22 at 11:35

Jonas Simonaitis

170
1
13

score 2 · Answer 13 · answered Oct 18 '18 at 07:54

In my case to get my debug build - I have to turn off Instant Run option :

File → Settings → Build, Execution, Deployment → Instant Run and uncheck Enable Instant Run.

Then after run project - I found my build into Application\app\build\outputs\appDebug\apk directory

score 1 · Answer 14 · edited May 23 '17 at 11:33

1

Take a look at this question.

TL;DR: clean, then build.

./gradlew clean packageDebug

edited May 23 '17 at 11:33

Community

1
1

answered Jul 17 '13 at 21:52

alikonda

1,186
9
7

1

Similar problem, but in my case running that command does cause it to build once, but it still doesn't work from inside android studio. – Migwell Jul 18 '13 at 04:06
1

It still doesn't create the .apk file? – alikonda Jul 18 '13 at 04:51

score 1 · Answer 15 · answered Mar 31 '14 at 01:51

When you have android studio make your signed apk file it uses

    <property name="ExportedApkPath" value="$PROJECT_DIR$/PROJNAME/APPNAME.apk" />

inside workspace.xml to find out where to place it. However, if you use ./gradlew assembleRelease it places it inside PROJNAME/build/apk. I have the same problem. For some reason my android studio will not show me anything inside the apk subdirectory so the apk is for all intents and purposes missing. But if you search with finder it's most definitely there.

path: /.idea/workspace.xml property: – davee44 Aug 31 '20 at 08:09 — davee44, Aug 31 '20 at 08:09

score 1 · Answer 16 · answered Apr 21 '22 at 10:27

Here is a small gradle script, which should help to find the output apk file. Probably it will work with aab:

applicationVariants.all { variant ->
    variant.getAssembleProvider().get().doLast { assemble ->
        def outputFile = variant.outputs*.outputFile
        println "\n\n\nOUTPUT FILE -> $outputFile\n\n\n"
    }
}

Put it insid the android body. Have a good coding

Where is android studio building my .apk file?

16 Answers16

Linked

Related