From 3164a7264fb73dfb89513a885c57e86f4fc3a0c6 Mon Sep 17 00:00:00 2001 From: Mary Yanchar Date: Fri, 8 Apr 2016 14:52:14 -0700 Subject: [PATCH] Clarified how to regenerate debug.keystore Clarified that you must both build and run to regenerate a missing/expired debug.keystore file (have tested that this fix works on Linux and Mac), removed information about troubleshooting for non-Gregorian calendars because the original issue has been marked as outdated and is no longer a problem. (https://code.google.com/p/android/issues/detail?id=834) Bug: 18064192 Change-Id: I1235fa14044e388ccf578beebfc77349eb6205cf --- docs/html/tools/publishing/app-signing.jd | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git a/docs/html/tools/publishing/app-signing.jd b/docs/html/tools/publishing/app-signing.jd index 4b74f5ff81393..21067c6ea7cb9 100644 --- a/docs/html/tools/publishing/app-signing.jd +++ b/docs/html/tools/publishing/app-signing.jd @@ -299,13 +299,9 @@ location is in ~/.android/ on OS X and Linux, in C:\Documents Settings\<user>\.android\ on Windows XP, and in C:\Users\<user>\.android\ on Windows Vista and Windows 7.

-

The next time you build, the build tools will regenerate a new keystore and debug key.

- -

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 -I can't compile my app -because the build tools generated an expired debug certificate.

+

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.

Signing Your App Manually