RASHID_AB's Forum Posts

  • How could this happen?

    Last saved project 11/15/2020

    How can you fix it?

    Is it due to updates?

  • You can do this with a tiled background and a blending mode "mask".

    "Mesh" doesn't fit a bit.

  • Photoshop has a function "Straight Lasso"

    Information is recorded here too

    You can select different areas in the image using this function and "define the pattern", that is, you can fill a seamless texture inside the selected area, and make a lot of things very conveniently, quickly and beautifully.

    For example, as in the screenshots, you can clearly see it.

    I suggest developers add a similar plugin to Construct 3.

    A similar feature can be seen in Construct 3 as "Mesh" but "Mesh" is too tight.

    We need a more flexible and costly tool to create our maps.

    Dear friends, if you work with the design of your cards, then you know that "TeliMap" or something else is extremely not dynamic and too inconvenient for revolutionary games.

    Have you played "Angry Birds" games?

    Have you seen how beautiful the levels look?

    All this can also be implemented using Construct 3 by adding the "Straight Lasso" function

    Tagged:

  • Dear friends, a solution has been found!

    It turns out that for the beginning you generally need to understand what tools are intended for what, to study the structure of work and functions.

    That is, just to study the relationships of objects.

    https://www.construct.net/en/tutorials/manually-signing-android-apps-29

    I used: 1) PowerShell 2) Android SDK (More precisely, their insides.) 3) keytool (commands and how the command is written) 4) zipalign

    First you need to understand how to write the commands themselves correctly, I personally did not know some small nuances from the beginning.

    The best way to understand the solution is to study the documentation without being lazy))

  • Just for the heads up google are going to change to this.

    Starting in August 2021, new apps will need to:

    Publish with the Android App Bundle format.

    Use Play Asset Delivery or Play Feature Delivery to deliver assets or features that exceed download size of 150MB. Expansion files (OBBs) will no longer be supported for new apps.

    Target API level 30 (Android 11) or above and adjust for behavioral changes.

    Starting in November 2021, app updates will be required to target API level 30 or above and adjust for behavioral changes in Android 11. Existing apps that are not receiving updates are unaffected and can continue to be downloaded from the Play Store.

    The switch to Android App Bundle delivery will also impact instant experiences using the legacy Instant app ZIP format. From August 2021, new instant experiences and updates to existing instant experiences will be required to publish instant-enabled app bundles.

    https://developer.android.com/distribute/best-practices/develop/target-sdk

    As far as I can see it only applies to new apps only, For now

    Yes, and this is inevitable, but we need to find an urgent solution to this issue.

    Thank you for the information that will greatly help those who did not yet know what lies ahead in the future and those who know and help working on solving this issue.

    Will you yourself support the initiative to create step-by-step instructions here on the forum?

    Best regards, thank you)

  • I personally really really want, I personally support and would like to get step by step instructions on how to sign applications using the Android SDK.

    I think this is very reliable, I think that everyone understands how important this is, given the upcoming changes, this is very important.

    Just like me and other people, there are applications in the Google Play market, and we are aware of the upcoming changes and increased requirements for applications when publishing and signing them.

  • Ashley, could any of your programmers, or yourself, do a short step-by-step tutorial for us on how to sign an application using the Android SDK?

    That is, signing an application that was compiled in Construct 3 is possible as an android project or an unsigned APK file.

    +

    Guys, do you agree that a lesson on signing an application using Android Studio will be just right for us?)

    Would you support this idea that the developers and the Construct 3 system can do such a step-by-step forum tutorial for us?

  • I did a signed release build in Construct and ran the following command on it:

    .\apksigner.bat verify --verbose .\test-signed.apk

    It produced the following output:

    > Verifies

    > Verified using v1 scheme (JAR signing): true

    > Verified using v2 scheme (APK Signature Scheme v2): true

    > Verified using v3 scheme (APK Signature Scheme v3): false

    > Verified using v4 scheme (APK Signature Scheme v4): false

    > Verified for SourceStamp: false

    > Number of signers: 1

    The line "Verified using v2 scheme (APK Signature Scheme v2): true" appears to indicate the APK is already signed with the APK Signature Scheme v2.

    So I don't know why the Play Store would show an error. Perhaps if you are using your own key it is that key which does not support the v2 scheme? It seems to be valid if you use Construct to both create the key and sign with it. The build server uses apksigner, which is the official Android build tool for signing APKs, and according to the documentation, it appears to automatically detect the signing schemes to use, and according to my test it appears to indeed be correctly adding the v2 scheme. Maybe you could run a similar apksigner command to identify the schemes being added to your own APKs.

    If I speculate, perhaps the v2 scheme can only be added if you use the same password for the keystore and the key - after all, the official keytool program no longer supports different passwords (hence the headache about having separate passwords last year), so maybe the v2 scheme doesn't support different passwords either. 🤷‍♂️

    Android APK Signing Tool (APK Signer)

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

    Here you go, this is the application that many people used to sign applications with.

    Now the key that was created with it must be used in the Construct 3 system.

    And signing the application in Construct 3 using the old key (what was created at the beginning outside of Construct 3) which is associated with the Google Play market gives an error.

    Is it possible to somehow expand the signing functionality in order to experiment with the activation checkboxes with v1 v2 v3 and so on?

    I understand that you can talk about this forever, but how exactly to solve this issue.

    Study the ANDROID SDK? Well, you can, well, you have to study)))

  • Thank you, I am very glad that the information about this has further raised the priority of necessity.

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

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • 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

  • 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

    Thank you for your participation in this matter. Your knowledge helps in solving this issue for everyone.

    We hope that Scirra will also invest in efforts to resolve this serious issue.

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