Help with Android Debug Password Reset

Getting Started Newbie Questions
#1

I messed up.  I was doing the steps below and I set the password incorrectly.  How can I change the password to Android as required below.  

Signing for Debug Build

For debug builds, Corona includes a debug.keystore for testing your app on devices. To use it, follow these steps:

Select Debug from the Keystore menu.

Directly to the right, Browse… to the keystore file in the Corona SDK application folder:

CoronaSDK / Resource Library / Android / debug.keystore

Select the file and enter android as the password.

In the Key Alias menu, select androiddebugkey.

 

Thanks,

Lori

#2

I uploaded a new build and therefore had to set a password for that build.   Problem solved

#3

Don’t use the debug.keystore for production releases.  You need to generate a new keystore and sign with that.  

One production keystore per app.

https://coronalabs.com/blog/2014/08/26/tutorial-understanding-android-app-signing/

PS - Don’t even upload binaries to your Google Developer account using the debug.keystore.  Once you upload a binary for a specific app, it is a pain to upload a new binary signed with a different keystore.

You must:

  1. Generate a production keystore.

  2. Sign your app with it.

  3. Upload that binary (from #2).

  4. Keep track of you keystore and password(s) for the keystore.  If you lose it or forget the password(s), you’ll have a heck of a time building and uploading new releases later.

#4

Thanks for the advice - much appreciated.

Lori

#5

I uploaded a new build and therefore had to set a password for that build.   Problem solved

#6

Don’t use the debug.keystore for production releases.  You need to generate a new keystore and sign with that.  

One production keystore per app.

https://coronalabs.com/blog/2014/08/26/tutorial-understanding-android-app-signing/

PS - Don’t even upload binaries to your Google Developer account using the debug.keystore.  Once you upload a binary for a specific app, it is a pain to upload a new binary signed with a different keystore.

You must:

  1. Generate a production keystore.

  2. Sign your app with it.

  3. Upload that binary (from #2).

  4. Keep track of you keystore and password(s) for the keystore.  If you lose it or forget the password(s), you’ll have a heck of a time building and uploading new releases later.

#7

Thanks for the advice - much appreciated.

Lori