Lines Matching full:sign
11 <li>You can sign with a self-signed key</li>
12 <li>How you sign your apps is critical — read this document carefully</li>
27 <li><a href="#signapp">Sign your application with your private key</a></li>
29 <li><a href="#ExportWizard">Compile and sign with Eclipse ADT</a></li>
58 <li>To test and debug your application, the build tools sign your application with a special debug
60 <li>When you are ready to release your application for end-users, you must sign it with a suitable
63 <li>You can use self-signed certificates to sign your applications. No certificate authority is
69 sign your application {@code .apk} files.</li>
70 <li>After you sign your application for release, we recommend that you use the
91 sign your application's <code>.apk</code> file. Because the alias and password are known to the SDK
95 <p>When you build in <em>release mode</em> you use your own private key to sign your application. If
98 Jarsigner utility to sign your application's <code>.apk</code> file. Because the certificate and
113 <p>In general, the recommended strategy for all developers is to sign
119 must continue to sign the updates with the same certificate or set of certificates,
124 the system allows the update. If you sign the new version without using matching
145 how to set the validity period of the key that you will use to sign your
155 <li>If you will sign multiple distinct applications with the same key,
161 key you use to sign the application(s) must have a validity period
168 use a <a href="#cert">suitable certificate</a> to sign your applications. </p>
190 a debug keystore and key. This debug key is then used to automatically sign the APK, so
191 you do not need to sign the package with your own key.</p>
237 <p>The self-signed certificate used to sign your application in debug mode (the default on
271 <li><a href="#signapp">Sign your application with your private key</a></li>
276 to perform the compile, sign, and align procedures. The Export Wizard even allows you to
278 skip to <a href="#ExportWizard">Compile and sign with Eclipse ADT</a>.</p>
285 you have a suitable private key with which to sign. A suitable private
317 in a safe, secure place. You must use the same key to sign future versions of your application. If
401 to sign it with your private key.</p>
427 Because the application APK is still unsigned, you must manually sign it with your private
434 <code>ant release</code>, it will sign the package and then align it. The final output
444 <h3 id="signapp">3. Sign your application with your private key</h3>
446 <p>When you have an application package that is ready to be signed, you can do sign it
451 <p>To sign your application, you run Jarsigner, referencing both the
453 sign the APK. The table below shows the options you could use. </p>
491 <p>Here's how you would use Jarsigner to sign an application package called
500 in-place, meaning the APK is now signed. Note that you can sign an
505 -digestalg}) when you sign an APK.</p>
525 your application, you must sign it with your private key instead of the debug
556 If you sign it after using {@code zipalign}, it will undo the alignment.</p>
562 <h3 id="ExportWizard">Compile and sign with Eclipse ADT</h3>
567 the Keytool and Jarsigner for you, which allows you to sign the package using a GUI
568 instead of performing the manual procedures to compile, sign,
584 including steps for selecting the private key with which to sign the APK
601 permission, that person could sign and distribute applications that maliciously
603 sign and distribute applications under your identity that attack other
