Lines Matching full:release
23 <li><a href="#releasemode">Signing for Public Release</a>
26 <li><a href="#releasecompile">Compile the application in release mode</a></li>
66 <li>When you are ready to release your application for end-users, you must sign it with a suitable private
85 and <em>release mode</em>.
94 <li>When your application is ready for release, you must compile in release mode
118 of your application, especially if you are planning to release multiple
126 <li>Application upgrade – As you release upgrades to your
191 <p>If you will release your application to the public, you will also need to have
220 <p class="caution"><strong>Caution:</strong> You <em>cannot</em> release your application
276 <h2 id="releasemode">Signing for Public Release</h2>
278 <p>When your application is ready for release to other users, you must:</p>
281 <li><a href="#releasecompile">Compile the application in release mode</li>
383 <pre>$ keytool -genkey -v -keystore my-release-key.keystore
389 <code>my-release-key.keystore</code>. The keystore and key are
401 <h3 id="releasecompile">2. Compile the application in release mode</h3>
403 <p>In order to release your application to users, you must compile it in release mode.
404 In release mode, the compiled application is not signed by default and you will need
408 You can not release your application unsigned, or signed with the debug key.</p>
423 <p>If you are using Ant, you can enable release mode by using the <code>release</code> option
427 <pre>ant release</pre>
438 <code>ant release</code>, it will sign the package and then align it. The final output
440 <code><em><your_project_name></em>-release.apk</code>. With these steps
444 IDEs: Building in release mode</a>.</p>
491 <pre>$ jarsigner -verbose -keystore my-release-key.keystore
516 signed with the debug key generated by the Android SDK. If you intend to release
