My dears, thank you very much for your answers and for your examples))) But still, you don't think it would be cool to create an excellent function with tools like in Photoshop?

Personally, it seems to me that construct 3 would become known outside galaxies if new tools were added there, because there would be more space for creating new things that are even more interesting, don't you think so?)

How could this happen?

Last saved project 11/15/2020

How can you fix it?

Is it due to updates?

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

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

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