> Of course, you need to invest effort in solving this issue, I think everyone wants to understand this and solve it as needed)

I meant you should try investigating it :) And then explain us how to fix it.

I am looking for

RASHID_AB It's obvious now that nobody on the forum knows how to solve this. If you think that Construct creates a key in the wrong format, which is no longer supported by Google Play, you need to log a bug report:

https://github.com/Scirra/Construct-3-bugs/issues

Otherwise you can try researching this issue in the internet how to generate a proper v2 key. And if you find the solution, post it here for the benefit of others.

My workaround was to change the target version to 29. Export as Cordova project, extract files and change target version from 30 to 29 in config.json and config.xml

Then package back to zip and build with C3 through Export Manager.

This is only a temporary workaround, I'm afraid Google Play will soon no longer accept SDK 29.

I agree with you, just reducing the Target SDK is just a temporary solution.

Of course, you need to invest effort in solving this issue, I think everyone wants to understand this and solve it as needed)

RASHID_AB - it is generally accepted that you can bump a post after 24 hours, especially as this is a global forum. If you need to add something to an existing post, please use the edit post button.

Hello. Thank you for writing.

Now, the question of how to sign an APK application using the built-in Construct 3 tool has become very acute.

As you can see from what is happening now, there is a problem related to the fact that the application signing tool APK when creating a key and also when signing with a key, the key password and alias password are automatically inserted into the same field (as I understand it) inside the key.jks, and then the key that is created has an invisible error. This error does not allow signing applications with another key that was created outside the Construct boundary. That is, I can no longer sign the application with a key that was created in another application.

Could you intensify your search for a solution to this issue, which, as I understand it, has been present for a long time?

I repeat, the Construct 3 game creation tool is simply gorgeous and irreplaceable, for me personally, the tool is an ideal tool for creating games or something else.

Especially when you are so diligently supplementing it with new features with new examples of new behavior plugins.

Apart from small mistakes and problems that you diligently solve almost every day, the tool is simply gorgeous.

But now the problem that is present in my opinion is very much stopping me and other developers. In general, I personally do not know much about deep programming, it may be very difficult for you, but still, you really need to solve this))

UP post

From what I can remember you can change you alias password like this

Download Java

When downloaded got to C:\Program Files\Java\jdk1.8.0_121\bin

You must be powershell user.

Use the keytool to change like in this tutorial https://blog.blundellapps.co.uk/tut-change-alias-passwords-of-your-android-keystore/

Hope this helps, but how to do this might have changed, since its a while ago I used this.

Thank you very much, I am sincerely glad for your help.

I will work on it.

Dear developers, please forgive your concern.

I am not claiming that I am doing everything right, that is why I am here and food, because I am looking for a solution.

Could you extend the functionality of the app signing tools?

Construct 3 is a great tool, I am very happy, I am very satisfied!

But there are such stupid situations that greatly upset us.

Please check it yourself, if you don't trust me, it is impossible to sign the application using my key, which I have always used with APK signer 1.8.5 in the Construct 3 environment

That is, you can create new keys, you can do whatever you want, but if it is not created in Construct 3 then this key is not valid.

Dear Construct 3 Developers

Could you come here now to answer a couple of questions?

Please, I ask you to pay attention to this situation.

Question: why can't you sign the application using the old ready-made key that always worked before target sdk 30 appeared?

I poked a lot everywhere in the middle of Construct 3. Why does Construct 3 standard signature not work when used?

Is it generally possible to use the old key in order to use it to sign applications using the V2 signature scheme

Is there a difference between the previously created key and the new one, that is, the signature scheme v1 and v2 is a secondary signature that uses the standard key?