Building APK certificate error

[Evgene Karachevtsev]

Hello,

I am really sorry for delay with resolving this issue. To speed up the process, please share your app with a href="mailto:support@appery.io" rel="nofollow"support@appery.io/a again.

[technofab]

Done.

[Evgene Karachevtsev]

Technofab,

Please download the certificate file that you have attached to the project from https://appery.io/account/home - Certificates.
Check the certificate with the command
prekeytool -v -list -alias net.fabrixxxxxxx.telexxxxxxx -keystore path/to/autogenerated.crt -storepass xxxx/pre
where net.fabrixxxxxxx.telexxxxxxx is your Package name, take it from the project.
xxxx is the password.
And please tell us what do you get with this command.

[technofab]

It says that the alias "net.fabrixxxxxxx.telexxxxxxx" doesn't exist.

But it's normal.
For compiling with other systems (eclipse, android studio, basic4android...), I don't need to add every time an alias.

if otherwise instead using "net.fabrixxxxxxx.telexxxxxxx" I use the alias b4a like in picture, I obtain the correct information about my certificate.

[Evgene Karachevtsev]

Technofab,

You should specify in Package name the correct alias with which you get it working.

[technofab]

Why? Normally Is not necessary. This mean I need to do a new keyring file. So itsn't the solution.

[Evgene Karachevtsev]

Technofab,

In the Package name must be specified the correct alias - this is how the Appery.io builder works.

[technofab]

OK but this answer is not the solution.

I can't made a different keyring for any app I need to made.
So with your answer, this mean for me, appery.io can't be used in a production and professional environment to publish apps in Google Play.
It is not conceivable to think having (to do) different certificates for different applications.

You must accept every alias, just in case, setting it in the control panel, but I don't think you need to have that information, because you already had this information decoded in certificate details in the control panel.

And after this, you say this after some days I've posted the certfied info there where is the alias, that is unique in a keyring and cannot be changed afaik. So why wating 3 days?

Really I'm very surprised, disappointed, and sadly to listen this, but for me is KO for google play, quite good for making web apps.

[Illya Stepanov]

Hello,

You can always export as Eclipse project and sign your app the way you prefer.

[technofab]

OK but still not be a solution; is a workaround.
I choose this environment, and many people too, because in more situation a RAD solution is preferable that using other tools.
Sorry, but thinking to use different certificate for different apps is not a good idea. You need to modify your system to accept any keyring file / keystore with any alias.
Another suggestion: add in your documentation that we need for every app a keyring file / certificate with alias named like "unique identifier" of the app.
thanks for your cooperation but unfortunately I can not continue on this way