fredriksthlm
So C3 will be able to use any keystore file. When you do a build via the build service it will ask you for a keystore file along with it's alias/key password/store password. We're avoiding storing the keystore itself within the editor. The hope being it will encourage users to put the file somewhere safe/secure and not just leave it in C3, trusting it will always be there. So no "import" is required.
If you want to the editor will also be able to generate new keystores for you. One limitation is that you will not be able to sign an existing APK, it will only work with builds.
Nepeo
Sounds really nice! Really good solution!
Just a side note, I think it would be good to write a manual of the few steps in Google developer, what is needed to set up to get the plugin to work, with leaderboards and stuff. Even if Google console is not really your product.
Currently many people are writing threads stating errors and bugs here and there, but I guess it is only because they do not know how to set it up in google console.
(same goes for Facebook plugin..)
For me all plugins seems perfect and works fine. (I am just waiting for a Audience Network plugin, then I am all happy!)