Program Files\Java\jdk1.8.0_45\bin\keytool.exe @roaminggamer
** JUST FIXED TYPO IN INSTRUCTIONS **
OK, let’s start simple. Please:
-
Open a command prompt
-
Copy and paste this (you didn’t include drive letter so I’ll assume C:), including the quotes:
“C:\Program Files\Java\jdk1.8.0_45\bin\keytool.exe”
-
Confirm that it ran.
If you get a message similar to this, continue:
Key and Certificate Management Tool Commands: -certreq Generates a certificate request -changealias Changes an entry's alias .... more lines after this
Now, let’s generate the keystore.
-
Run this command to generate a keystore called “myapp.keystore”:
“C:\Program Files\Java\jdk1.8.0_45\bin\keytool.exe -genkey -alias myapp -keyalg RSA -keystore myapp.keystore -validity 10000”
You’ll need to supply answers to the questions the tool asks on your own.
-
If you got this far, there should now be a file called “myapp.keystore” in your current directory (whereever the console says you are).
-
Do an android build and select that file as the keystore.
-
You’ll be prompted for a password twice. Supply the one you used when creating the keystore.
-
Done.
The APK that results from step 7 is ready for uploading to the Google Play Developers console.
I got that but keytool isnt a batch file or external command still
So i did the instructions you said it worked but when typing in the code for the release mode get that error above
I think you’re seeing posts out of order?
Whatever the case I hope you’ve got this worked out.
One last post for good measure.
In this video I sign an app w/ a Production Key:
https://www.youtube.com/watch?v=dg8dvXq8yzo&feature=youtu.be
In this video I correct a mistake I made in the last video (everybody makes mistakes) and then upload the new APK to my Google Developer Page:
https://www.youtube.com/watch?v=RQyU9qYf3do&feature=youtu.be
Hi. This is one of those things you pay someone to do, or struggle with the first time. I’m sure it is daunting, but let me suggest this:
-
Do read through the link above and look around on the web for more info.
-
Next week, once I get caught up on client work and responsibilities, I’ll check back. If you’ve still not resolved this I’ll add my 2-cents to this thread.
Why not now? Well, its really not easy to describe without stepping through it right now and enumerating the steps. I just don’t have time. I’ve got to leave shortly and then I’m booked solid through Tuesday.
Having said all that, do the following:
A. step #1 above
B. Learn to create android certificates. If you are running under Windows the command will look something like this:
keytool.exe -genkey -alias AAAA -keyalg RSA -keystore BBBB.keystore -validity 10000
Replace AAAA with a an alias (a single word; no spaces; usually the name of the app) BBBB can be anything. This will start a Q/A process where you answer questions. It will result in new certificate called BBBB.keystore (where BBBB is whatever you put in).
If I put in awesome_app for AAAA, the questions would look like this:
Enter keystore password: CCCC Re-enter new password: CCCC What is your first and last name? [Unknown]: 1111 What is the name of your organizational unit? [Unknown]: 2222 What is the name of your organization? [Unknown]: 3333 What is the name of your City or Locality? [Unknown]: 4444 What is the name of your State or Province? [Unknown]: 5555 What is the two-letter country code for this unit? [Unknown]: 66 Is CN="1111", OU="2222", O="3333", L=4444, ST=5555, C=66 correct? [no]: yes Enter key password for \<1111\> (RETURN if same as keystore password):
Obviously, you put in your own info for the password (CCCC), and replace 1111…66 w/ your data.
C. Create a Google Play Developer account.
D. Go to the developer console: https://play.google.com/apps/publish
E. Add and Fill in the details for a new app.
F. Build your app with the key you made above.
G. Submit it to the developer console.
Note: It is inappropriate to ‘hijack’ forums posts and to post questions not related to the original post just because you think the person you want to reach is reading that post.
People do this to me occasionally and it rubs me the wrong way. I’ll let it pass this time, but I won’t answer you again if you do this in the future.
To be clear, this diminishes the value of the other post a little because it now has an unrelated entry. It also opens the door for more unrelated posts and this behavior.
I read most new posts, but I don’t have time (or the knowledge) to answer them all. Also, others step in with great answers quite frequently.
Anyways, rant over… Good luck in the publishing.
@Roaminggamer ‘Keytool.exe’ is not recognized as an internal or external command operable program or batch file
We have guides for things like this under the Documentation link above:
https://docs.coronalabs.com/guide/distribution/androidBuild/index.html
If you don’t have keytool installed on your machine (which you probably do, but perhaps not in your path) you’ll have to install it. It comes as part of a toolkit.
Rob’s link will lead you in the right direction.
-Ed
Did you get through the publishing steps? I know it was probably a lot to deal with the first time, but as with anything, the more you do it the easier it will get.
Note: I usually keep notes in a (electronic) journal to remember the steps. I don’t keep it all in my head and I suggest you not try to either. i.e. I make a kind of personal cheat sheet to follow when I do it again.
Cheers,
Ed
What step did you get stuck on?
i.e. How much did you figure out and what did you get stuck on?
Well I got too the path and it was different i changed it like it said in the youtube tutorial yet same error @roaminggamer
Are you a Windows or OS X user? It sounds like… Windows?