Signing for Release Build on a Mac

Getting Started Newbie Questions
#1

This is my first project and I was not able to find a complete answer for this so I apologize in advance is this is answered somewhere else.

I completed my app and prepped it for the Google market place. It would not upload because it said it was signed for debug build. I got my license key installed in the file and followed the instructions on this page for Release Build:

http://docs.coronalabs.com/guide/distribution/androidBuild/index.html#signrelease

I went into Terminal and followed the steps. I completed all of the Name, Company, etc.

Now what?..

I went back to Corona and the only option I still have is Debug for Keystore. Was a file supposed to download? Was I supposed to do something else? I feel like Im overlooking something obvious here but can’t figure it out.

So close. Any help would be greatly appreciated.

#2

If you followed the steps in that guide using the command:

sudo keytool -genkey -v -keystore mykeystore.keystore -alias aliasname -keyalg RSA -validity 999999

then there should have been a file called:  mykeystore.keystore created in the **directory/folder** where you ran the command (likely /Users/yourname/). 

Now hopefully you changed mykeystore.keystore to  something more practical for your use (like release.keystore) and you changed aliasname to something more realistic like (releasealias).  Regardless, from the Corona SDK build screen there should be a Browse… button that will let you navigate to wherever you saved  your keystore file. 

Then you type in the name you used for the alias.  If you just copied and pasted the line, it will be “aliasname”.  Put in the password  you used for it and you should be good to go (You may have to enter the password a couple of times).

Rob

#3

You are the man Rob! Thank you very much. That worked perfect.

#4

If you followed the steps in that guide using the command:

sudo keytool -genkey -v -keystore mykeystore.keystore -alias aliasname -keyalg RSA -validity 999999

then there should have been a file called:  mykeystore.keystore created in the **directory/folder** where you ran the command (likely /Users/yourname/). 

Now hopefully you changed mykeystore.keystore to  something more practical for your use (like release.keystore) and you changed aliasname to something more realistic like (releasealias).  Regardless, from the Corona SDK build screen there should be a Browse… button that will let you navigate to wherever you saved  your keystore file. 

Then you type in the name you used for the alias.  If you just copied and pasted the line, it will be “aliasname”.  Put in the password  you used for it and you should be good to go (You may have to enter the password a couple of times).

Rob

#5

You are the man Rob! Thank you very much. That worked perfect.