Android Question [SOLVED...] Problem with signing

[Vinians2006]

When I try to compile my app I am getting the following error:

Signing package file (private key) Error

jarsigner: Certificate chain not found for: b4a. b4a must reference a valid KeyStore key entry containing a private key and corresponding public key certificate chain.

I have correctly loaded my ever used key, what can be wrong? Everytime I start a new project I need to create another key ?? Why I cant use the same key to all my project?
Thanks!

 

[DonManfred]

you can use ONE keystore for all your projects. I use one and never change that one... You must do something wrong i believe

Where do you save the keychain?

 

[Vinians2006]

I dont know what Im doing wrong, I use a file stored in a folder, so I started my new project and loaded that key file successfully, but when I try to run my app I got this message... I really dont know what can be wrong...
Thanks for reply

 

[DonManfred]

I dont know what Im doing wrong, I use a file stored in a folder, so I started my new project and loaded that key file successfully

Why you change the keystore already configured in b4a when you start a new project?
Where do you store the Keystore? Exact path please

 

[Vinians2006]

Ok, the path of my private key is C:\Dropbox\Criacoes\KeysBackup\xcreator.keystore, but what is the use of this information ?
I need to configure b4a to my key so I can be able to send my app to android store, I cannot use default debug key...

Thank you for trying to help-me.

 

[Peter Simpson]

B4a automatically remembers your previously created keystroke. Just create 1 new keystroke and use it with all your projects. Also you should not share your keystroke with anybody, it's yours and yours alone. If you have a keystroke error, remove the installed app from the device and run your project again...

 

[NJDude]

B4a automatically remembers your previously created keystroke. Just create 1 new keystroke and use it with all your projects. Also you should not share your keystroke with anybody, it's yours and yours alone. If you have a keystroke error, remove the installed app from the device and run your project again...

I think you mean KEYSTORE.

 

[Peter Simpson]

Oops sorry and thank you Mr Dude, I'm Ill and typing on my tablet, even though that's not even a good excuse

 

[Vinians2006]

The problem is how B4A create its key. If you use another tool, or whatever to create your b4re using B4A it refuse to accept that key. I use a key created with Game Maker Studio which is not compatible with that one generated by B4A. See the thread bellow to understand:
https://www.b4x.com/android/forum/threads/support-for-sha256-rsa-sign-keys.45478/
Thanks for all replies !

 

[Erel]

During development use the default debug key. When you are ready to distribute your app (assuming that you must use the previous key) then compile without signing and sign it yourself.