Lines Matching full:application
20 <li><a href="#Signing">Application Signing</a></li>
34 <p>There are two ways to build your application using the Ant build script: one for
35 testing/debugging your application — <em>debug mode</em> — and one for building your
36 final package for release — <em>release mode</em>. Regardless of which way you build your application,
44 development device. You cannot distribute an application that is signed with a debug key.
50 you're ready to release your application and share it with end-users. That document describes the
71 <p>For immediate application testing and debugging, you can build your application in debug mode
73 application with a debug key and optimize the package with {@code zipalign}.</p>
93 the latest version of the application.</p>
95 <p>To install and run your application on an emulator, see the following section about <a href=
100 <p>When you're ready to release and distribute your application to end-users, you must build your
101 application in release mode. Once you have built in release mode, it's a good idea to perform
104 <p>Before you start building your application in release mode, be aware that you must sign the
105 resulting application package with your private key, and should then align it using the {@code
112 <p>If you build your application <em>unsigned</em>, then you will need to manually sign and align
127 <p>This creates your Android application .apk file inside the project <code>bin/</code>
144 your application package. To do so, you must provide the path to your keystore and the name of
147 mode and produce your final application package, which will be ready for distribution.</p>
152 application signing manually, via Jarsigner (or a similar tool). To instead perform the signing
182 <p>This creates your Android application .apk file inside the project <code>bin/</code>
189 <p>Once you have signed your application with a private key, you can install and run it on an
192 site, then load the .apk URL in your Android web browser to download the application and begin
198 <p>Before you can run your application on the Android Emulator, you must <a href=
201 <p>To run your application:</p>
217 <strong>Install your application</strong>
226 directory after you build your application.</p>
229 install the application, by its serial number, with the <code>-s</code> option. For
239 <p>If you don't see your application on the emulator, try closing the emulator and launching the
240 virtual device again from the AVD Manager. Sometimes when you install an application for the
241 first time, it won't show up in the application launcher or be accessible by other applications.
245 <p>Be certain to create multiple AVDs upon which to test your application. You should have one
246 AVD for each platform and screen type with which your application is compatible. For instance, if
247 your application compiles against the Android 4.0 (API Level 14) platform, you should create an
250 application on each one.</p>
253 build your application and install it on the emulator in one simple step. Navigate to the root of
255 install</code>. This will build your application, sign it with the debug key, and install it on
260 <p>Before you can run your application on a device, you must perform some basic setup for your
302 <h2 id="Signing">Application Signing</h2>
307 device) or with a <em>private key</em> (for application distribution).</p>
310 debug key at build time. This means that you can compile your application and install it on the
312 to publish your application, you <strong>must</strong> sign the application with your own private
317 run your application from Eclipse without having to generate your own private key. No specific
319 you intend to publish your application, you <strong>must</strong> sign the application with your
323 Applications</a>, which provides a thorough guide to application signing on Android and what it
324 means to you as an Android application developer. The document also includes a guide to exporting
325 and signing your application with the ADT's Export Wizard.</p>
334 application, library, and test projects and compiles
363 tested application. This fails if the <code>.apk</code> is not already built.</dd>
