Lines Matching refs:debug
58 <li>To test and debug your application, the build tools sign your application with a special debug
61 private key. You cannot publish an application that is signed with the debug key generated
77 run it or debug it on an emulator or device.</p>
82 use to build your application. There are two build modes: <em>debug mode</em> and <em>release
83 mode</em>. You use debug mode when you are developing and testing your application. You use
87 <p>When you build in <em>debug mode</em> the Android SDK build tools use the Keytool utility
88 (included in the JDK) to create a debug key. Because the SDK build tools created the debug key,
89 they know the debug key's alias and password. Each time you compile your application in debug mode,
90 the build tools use the debug key along with the Jarsigner utility (also included in the JDK) to
92 build tools, the tools don't need to prompt you for the debug key's alias and password each time
102 <p>The debug signing process happens automatically when you run or debug your application using
104 script with the <code>debug</code> option. You can automate the release signing process by using the
187 <p>The Android build tools provide a debug signing mode that makes it easier for you
188 to develop and debug your application, while still meeting the Android system
190 When using debug mode to build your app, the SDK tools invoke Keytool to automatically create
191 a debug keystore and key. This debug key is then used to automatically sign the .apk, so
194 <p>The SDK tools create the debug keystore/key with predetermined names/passwords:</p>
196 <li>Keystore name: "debug.keystore"</li>
203 <p>If necessary, you can change the location/name of the debug keystore/key or
204 supply a custom debug keystore/key to use. However, any custom debug
206 debug key (as described above). (To do so in Eclipse/ADT, go to
211 to the public when signed with the debug certificate.</p>
217 signing in debug mode is enabled by default. When you run or debug your
218 application, ADT signs the .apk with the debug certificate, runs {@code zipalign} on the
225 <p>If you are using Ant to build your .apk files, debug signing mode
226 is enabled by using the <code>debug</code> option with the <code>ant</code> command
228 <code>android</code> tool). When you run <code>ant debug</code> to
238 <p>The self-signed certificate used to sign your application in debug mode (the default on
244 <pre>debug:
245 [echo] Packaging bin/samples-debug.apk, and signing it with a debug key...
250 <p>To fix this problem, simply delete the <code>debug.keystore</code> file.
256 <p>The next time you build, the build tools will regenerate a new keystore and debug key.</p>
259 tools may erroneously generate an already-expired debug certificate, so that you get an
262 I can't compile my app because the build tools generated an expired debug
299 <li>Is not the debug key generated by the Android SDK tools. </li>
398 You can not release your application unsigned, or signed with the debug key.</p>
506 signed with the debug key generated by the Android SDK. If you intend to release
507 your application, you must sign it with your private key instead of the debug