Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge "Clarified how to regenerate debug.keystore" into mnc-mr-docs am: 1452c87

Browse Source 
am: 98a02c0

* commit '98a02c0b9a39bc1caba968520416e16e84f2b43b':
  Clarified how to regenerate debug.keystore

Change-Id: I6b61531f71b1b2ba4c8eef90f935e5d786e32b21
This commit is contained in:
Mary Yanchar
2016-04-26 07:50:42 +00:00
committed by android-build-merger
parent da62a9e12b 98a02c0b9a
commit 33b03aea27
1 changed files with 3 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/html/tools/publishing/app-signing.jd
View File

@@ -299,13 +299,9 @@ location is in <code>~/.android/</code> on OS X and Linux, in <code>C:\Documents
Settings\&lt;user&gt;\.android\</code> on Windows XP, and in
<code>C:\Users\&lt;user&gt;\.android\</code> on Windows Vista and Windows 7.</p>
<p>The next time you build, the build tools will regenerate a new keystore and debug key.</p>
<p>Note that, if your development machine is using a non-Gregorian locale, the build tools may
erroneously generate an already-expired debug certificate, so that you get an error when trying
to compile your application. For workaround information, see the troubleshooting topic
<a href="{@docRoot}resources/faq/troubleshooting.html#signingcalendar">I can't compile my app
because the build tools generated an expired debug certificate</a>.</p>
<p>The next time you build and run your app, the build tools will regenerate a
new keystore and debug key. Note that you must run your app, building alone
does not regenerate the keystore and debug key.</p>
<h2 id="signing-manually">Signing Your App Manually</h2>