LiveCode Forums.

I entered a return at the second password request also and it worked. I created my key on a Mac though and I'm not sure how things might differ on Windows.

I wanted to mention that you should guard your key file and password closely. Once created, you should backup the file to a secure location and never disclose any information about it. The password(s) you use for the key should follow the same security rules as passwords you use for your bank access -- they should be long, a mix of punctuation and letters, and not include any dictionary words. The key is what identifies you as a specific developer and verifies the authenticity of your app, and you want to keep it secret. Anyone who knows its password or gains access to your key file can release software that appears to come from you, the most common being malware that is disguised as your harmless app. Once the malware is linked to your identiy, it will be the end of your legitimacy as a developer (and likely will be the shutdown of your Google and Amazon priveleges.) Even if no one attaches malware to your key, you probably don't want anyone else representing themselves as you.

If you are only using the key to test locally on your own device, it doesn't much matter what you use (and that's why there's a generic "development key" option in standalone builder.) But if you distribute the app to anyone at all then there's at least some risk, though it may be slight.

Thank you Simon and Jacqueline.

Put the flags out, as at last I now have my release.keystore file. After trawling Google for what seemed like hours I found someone with the same problem as me and the advice was to keep doing it continuously, but change the Alias name and so this I did and after a great many attempts I was finally successful.

Regards,

Ruth

Oh my, Oh my I'm still not there.
I can't Save as Standalone Application because I get an error and whilst I was convinced I had entered the correct password and as it failed each time I ran the 'Save as Standalone Application ' I deleted the release.keystore and created another one (just as before taking multiple attempts) paying particular attention to the password and I'm yet again getting the error below.

I feel totally exhausted and after sobbing my eyes out like a baby, I'm at a loss to understand what the problem is.

Regards,

Ruth

Hi Ruth,
Don't give up!
When I first made one, I over thought it and made mistakes.
liveCode will ask for, if I recall, 3 passwords, make sure you use the correct ones for each. They do match what keytool asked but the wording is subtly different.

Ok I admit I thought I knew better and rushed to building an .apk.
Carefully read the dialogs from LC.

Hey, for practice just make each the same see if it works!

Simon

Hello Simon,

In the cold light of day and feeling a fool I did not realise the publicly known original CMD android password was being asked for again. So in theory I have an app with a private key to upload onto Google Play.

Regards,

Ruth

YEAH!!!!
WAHOOOOO!!!!!!

Oh good. You will have to verify your identity and password every time you do a build. That's why it is handy to build and test "for development only", which doesn't require any input, and then just use your protected key when doing the final build for distribution.

Really glad you got it working.