Where is Android studio located for my .apk file?

Question

I rebuilt my project from scratch, so there were a lot of problems with it. At the moment, everything is working fine, except that when I try to start the application, I get the message "The local path does not exist." where the local path points to the path: AndroidStudioProjects \ MyProject \ MyProject .. \ build \ production \ MyProject.apk, and it really is, there is no .apk file in this place or even anywhere else in the project file system.

However, I can create the application without any problems, and running gradlew packageDebug gives me a “ build successful ” message, so I need to create .apks. My question is: where do they go, or if they are not generated, why not?

Where is the build path of each module? I am somewhat confused because the parameters of Project Structure-> Facets-> Android-> Compiler, Project Structure-> Modules-> Paths-> Compiler Output, build.gradle and MyProject.iml seem to have something to do with building the path but I don’t quite understand how they are connected

edit: I know where this should be, but it is not, so I want to know how to change the build path

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

edit 3: Here is my output from the gradlew assembly, note that it works successfully:

Creating properties on demand (aka 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 

Answer 1

YourApplication \ application \ builds \ outputs \ APK

Answer 2

I am having trouble finding my debug apk. Android Studio 0.8.6 did not show apk or even the output folder in the project / project / assembly /. When I checked the same project / project / build / path from the Windows folder explorer, I found there the "output" folder and debugged apk inside.

Answer 3

Go to the AndroidStudio project. File

• Select a project name,
• Choose application
• Choose assembly
• Select outputs
• Choose Apk

Here you will find the application’s APK files if you run the application in AVD or even a hardware device

Answer 4

For Android Studio:

If you have not created the APK at least once, you cannot find the / Outputs / APK folder. Go to Build in Android Studio, and one of the last three options is Build APK, select this. He will then create this folder and you will find the APK file there.

Answer 5

Apk application was in this place

C: \ Users \ haseeb_mir \ AndroidStudioProjects \ MyTestApp \ application \ assemblies \ outputs \ APK \ debug

Answer 6

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

~ \ MyApp_Name \ application \ builds \ outputs \ APK \ application-debug.apk

Answer 7

When Gradle creates your project, it puts all the APKs in the build / apk directory. You can also simply execute the simple recursive find command for * .apk in the top level directory of your project.

Here is the best description ...

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

Answer 8

Take a look at this question .

TL; DR: clean, then build.

 ./gradlew clean packageDebug 

Answer 9

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 puts it in PROJNAME / build / apk. I have the same problem. For some reason, my android studio won't show me anything inside the apk subdirectory, so apk still doesn't make sense. But if you are looking for a search engine, it definitely exists.

Answer 10

in android 3.1.0 The above path to search for a signed version of the APK

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