Android Question Private key settings stay populated with new project

[Sifu]

Hello,
I see that the Private Key settings fields stay populated with info from a previous project.
Should that not be empty when starting a new project? and be filled again when the correct project is opened?
I noticed it at the point I wanted to do a small test with debug via B4a Bridge.

Thanks!

 

[Erel]

I recommend you to use a single key for all projects. The only reason to use a different key is if you are building a project for someone else.
In that case use the #SignKey... attributes to set a project specific key.

* another reason to use a different key is if you have an old key for old projects and it doesn't meet the Google requirements for new apps.

 

[Sifu]

Thank you.
I was under the impression that each project needed a new key.
But this is good.

 

[KMatle]

It identifies you as the developer. Later updates can only be done with the same key.

 

[Sifu]

It identifies you as the developer. Later updates can only be done with the same key.

Thank you, I understand that. I thought I've read on Google that each project should have it's own key. Well that's how I've been doing it before starting with b4x.
Because when you create a key, you mention the name of the app in the created keystore.
But if one key for a single developer or customer(who knows in the future) is good, then I'm of course ok with that. It simplifies stuff.