Lines Matching refs:debug
38 one for debugging your application — <em>debug</em> — and one for building your
41 …a debug key when building in debug mode and with your own private key when building in release mod…
43 <p>Whether you're building with the debug or release build type, you need to run
45 When you build using the debug build type, the .apk file is automatically signed by the SDK tools
46 …with a debug key based on the <code>debuggable true</code> setting in the module's gradle.build fi…
48 development device. You cannot distribute an application that is signed with a debug key.
58 development device by building in debug mode.</p>
76 <p>For immediate application testing and debugging, you can build your application in debug mode
77 and immediately install it on an emulator. In debug mode, the build tools automatically sign your
78 application with a debug key and optimize the package with {@code zipalign}.</p>
80 <p>To build in debug mode, open a command-line and navigate to the root of your project directory.
81 Use Gradle to build your project in debug mode, invoke the <code>assembleDebug</code> build task
84 <p>This creates your debug <code>.apk</code> file inside the module <code>build/</code>
85 directory, named <code><your_module_name>-debug.apk</code>. The file is already signed
86 with the debug key and has been aligned with
265 <p>Your .apk file (signed with either a release or debug key) is in your module {@code build/}
295 install</code>. This will build your application, sign it with the debug key, and install it on
346 to do this: with a <em>debug key</em> (for immediate testing on an emulator or development
350 debug key at build time. This means that you can build your application and install it on the
353 key, rather than the debug key generated by the SDK tools.</p>
355 <p>Android Studio helps you get started quickly by signing your .apk files with a debug key,
360 with your own private key, rather than the debug key generated by the SDK tools.</p>