RASHID_AB's Forum Posts

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

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

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

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

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

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

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

    What can be done?

    Are there people who have solved such issues?

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

  • > Hello.

    >

    > I will not give you a direct answer.

    >

    > It is impossible to answer this question quickly in a nutshell.

    >

    > Because interconnectedness follows from this.

    >

    > If you answer it, you will have to write an article.

    >

    > Wouldn't it be better for you to start learning with the built-in lessons of Construct 3 try it step by step

    It's impossible to answer? It's changing one animation for another m8

    You will not be able to explain it as you yourself understand, because there must be a basic understanding to understand what you are talking about.

    You need to have a basic knowledge of animation.

  • Hello.

    I will not give you a direct answer.

    It is impossible to answer this question quickly in a nutshell.

    Because interconnectedness follows from this.

    If you answer it, you will have to write an article.

    Wouldn't it be better for you to start learning with the built-in lessons of Construct 3 try it step by step

  • 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

  • You do not have permission to view this post

  • > Downscaling quality. The default medium tightly packs spritesheets, and generally works. However if there are issues with color fringing, the high mode will pad out spritesheets and avoid the problem - at the cost of increased memory use.

    The game already takes 40 MB and I want the game to be easy for different phones.

    Although I try not to use more than 512x512 textures, sometimes I have to.

    Not all smartphones are optimized for Html

  • > CAUSES OF THE PROBLEM

    > In practice, this is actually relatively rare. As noted you have to be unlucky enough to have all of the following happen:

    >

    > Resize an image considerably smaller than its source size

    by the looks of your sprite image, the source is 512x512 yet in your game is at around 30pixels ... resize the source to 30 pixels or the biggest size you use in the game.

    if the problem persists i would change the sprite.object to a tiledbackground object, if that doesn't solve it, ehm, i got nothing else.

    here is why i refer to tiledbackground object use, when you use the autocrop on tiledbackground object edges are cut perfect pixel, where if you do it for the sprite.object there will be added a 1px or 2x border radius transparent space around it. is annoying, but since C3 that problem never got fixed, and it will probably never will... not to mention the tiled-background object reder quality is far more superior than the sprite objects, where it ads edge blur where it shouldn't etc.... i know it might not sound as the perfect approach but is a workaround the current issue until is fixed.

    If you contacted me, I will tell you, the image on the screenshot is 128X128 And the sizes of objects were controlled using "Scale: from 0.5 to 1"