Having issues with export panel signing interface...

I've just updated to the latest stable release (r204) and I'm trying to export for Android.

I do the usual Menu > Project > Export > Android (Cordova) > Choose Signed Release APK...

Then further down the interface I get to choose My Keystore and input Keystore Alias, Keystore Password but there's no box to input Keystore Key and so the build fails...

Am I missing something? Is this a new feature of r204 that I need to check/uncheck something previously down the line or is it an error?

The build tool was actually ignoring the key password field, which was causing problems. So we removed it.

Can you create a new key store?

I guess you need to use always the same keystore for google play since it's a live game (already published with the key)...

Yeah I thought you always had to use the same keystore otherwise you can’t update your live game.

The problem we have is the build tool was (it seems) updated to ignore the key password when creating keystores. So people kept entering a key password when creating a keystore, which was ignored, then re-entered it when signing the app, and then getting "wrong password" errors. This change was in the beta release for about a month before it came to a stable release, which gave the impression the change was OK.

If we add back a key password field just for signing, we'll be asking people to enter a password they never previously specified, which would probably cause further confusion.

So it's not clear to me what to do here, it seems this change to the build tool has thrown a spanner in the works. AFAIK whether or not you can change the keystore depends on the precise method you use for publishing, and in some cases I think you can change it. Otherwise you can try downloading the Java keytool and changing the key password on the keystore - it needs to match the keystore password, since the build tool now only supports both the keystore and key passwords being the same.

Sounds to me like you’ve fixed one problem to create another that will affect the whole community.

Before taking any action, it would be useful to establish if you can indeed use a new keystore, since that would be a straightforward workaround and not require any further (and potentially confusing) changes to Construct.

Hey,

I found this from Google:

"Note: Using app signing by Google Play is optional. You can still upload an APK and manage your own keys instead of using an app bundle. However, if you lose your keystore or it becomes compromised, you won’t be able to update your app without publishing a new app with a new package name."

Here the link:

support.google.com/googleplay/android-developer/answer/7384423

So I think it's not possible for everyone to generate a new key. But I don't know how many users will face this issue. Atm. I'm trying to sign the app by another service, but with C3 I can't.

When I was learning how to build my first app with Construct I learnt that I’d you lose your keystore then you couldn’t paste your app once live - so don’t lose your keystore a otherwise you’re screwed.

Seems odd that Scirra wouldn’t know this And would create an update that blocks any current live from ever being updated.

Is there any chance to add an additional description, so if someone can't build then he just should try to enter the keystore-password in the key-password field or how this actually works?

I have several games and really don't want to change keys for all of my live games if that's even possible.

Atm everything seems to be working by using another signing service, but of course it's more to do so... (exporting, then uploading to another software and signing)