Application signature (key issues)

Post reply
0 favourites
From the Asset Store
Drawing Continuous Line
$10 USD
solution for games like "fruit ninja" and drawing applications
paradine's avatar
paradine

  • Hello

    I have always signed my apps with "APK Signer Tool 1.8.5"

    https://shatter-box.com/knowledgebase/android-apk-signing-tool-apk-signer/

    https://workupload.com/file/6zMGTZbZ

    But after adding 30 to Construct + Target SDK, it urgently became necessary to sign applications with a v2 signature signature scheme

    In general, I decided to sign the application using the same key that was created in that program only in Construct 3 by entering all these passwords, there are no errors, there is no deep understanding of what is happening.

    Tried different methods, changed passwords with "Alias"

    Couldn't solve anything at the moment.

    Need help from knowledgeable people.

    To update applications, you need to sign the applications with the same keys so that the certification of the applications is consistent.

    Question: Is it possible to solve this issue, can the old key that was created in "APK Signer Tool 1.8.5"

    How to put it through Construct 3

    I tried different methods, created new keys in that program in order to understand what is the reason for the refusal.

    But there is no solution to the issue.

    In Construct 3 itself, the generated key is signed.

    Unfortunately, apps cannot be updated without the original original key.

    ----------------------

    Error information

    ----------------------

    Input data

  • Had the same problem today, ended up changing target sdk to 29. It works for now, but I'm guessing Google Play will soon stop accepting this version, so I'll need a proper solution.

  • Had the same problem today, ended up changing target sdk to 29. It works for now, but I'm guessing Google Play will soon stop accepting this version, so I'll need a proper solution.

    I tried different things, created new keys, deleted and experimented.

    In general, even the key created in Android sdk does not work in Construct 3

    What should we do now?

    This is a very stupid situation, because of which many can suffer.

  • Developers of Construct 3 What are your suggestions for solving this issue?

    What can be done?

    Are there people who have solved such issues?

  • Are there still people who faced this problem but could not solve or have already solved it.

    Please do not stand aside, this problem affects and affects everyone who has applications on Google Play.

    In the end, we will find a solution to this issue in any case.

  • 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?

  • 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 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.

  • Problem

    It turns out

    The key created in Construct 3 uses the same password in two places!

    Because of this, the signature does not work!

    I just signed the application in APK Signer 1.8.5 using the key that was generated in Construct 3.

    And you know what?

    The password must be written in two places.

    Whereas before, the Alias ​​password was different when I signed it with Apk Signer 1.8.5!

    This is a mistake what is this?

    it should be?

  • This is probably why my old key is not signed in the Construct 3 compilation environment when I write the password there.

    What can developers do about it?

  • 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.

  • 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.

  • 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.

    But this will not solve the very problem of signing an application in the middle of Construct 3.

    Yes, changing to edit a key is one thing, but the key that I have is linked to Google play.

    I just need to sign my application with a key using the v2 scheme, unless, of course, I understood correctly, the signature scheme is not inside the key itself, that is, the key may be the same, but I understand the signature scheme for target 30 correctly?

    I write through a translator, which is probably why my text expressions are a bit incorrect.

    I mean that Construct 3, when creating a key, uses a password where you need to write a password and where Alias ​​password is.

    That is, the password is written in two places at once.

    Perhaps therefore also, the password that was created in Android Studio is not signed when it is used in Construct 3 /

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • I did not understood the doubt itself. I have very less knowledge regarding apps development.

    What is the role of APK signer here? I mean what I do:-

    1.) Do what I want to create in construct 3

    2.) Then go to export option and select "android"

    3.) Then upload key and password whatever is required

    4.) Project gets upload and after few minutes I get my game

    dop2000 can you please explain what the doubt is about? Seems very important

  • As ever I think your best course of action here is to raise this as a bug, link below.

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

    I refer you to these previous related issues.

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

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

Post reply
Return to board index
Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)