I have always signed my apps with "APK Signer Tool 1.8.5"
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.