sizcoz You probably found most of this out already but to sign an APK you need a developer private key, the unsigned apk, the apksigner tool and the zipalign tool. If you don't have a keystore file you need keytool from the JDK to create one. Both apksigner and zipalign are part of the androidSDK. I can't remember exactly but I expect even a signed release build must go via the play store to install, so debug APK's are the way to go unless your publishing.
Nepeo
First I would like to say thank you for your response.
It's nice and reassuring to know someone is working on this.
Background
I have several Apps/Games of which I need to maintain, bring new versions enhancements to.
These games were wrapped into an APK from Intel XDK.
Ok I have my .keystore file from these games, from XDK.
Problem
I need to sign these future versions, with whatever will work.?
I signed the release version with jarsigner and zipaligned it with Java SDK, Android SDK, Signed ok, and Aligned ok, from the command line, but was unrecognised on my mobile, I must be doing something wrong somewhere, as this is a tedious process, involving application permissions, incompatable Java versions, Etc, as you are probably aware.
Retro signing an APK with a Keystore is not possible in Android studio as far as I am aware, which means, as you say exporting your project into android studio and building and signing from there, a bit complex.
So essentially what I was asking is there a cohesive roadmap of intent, to try and bring an APK signing process to C3 when you have already have a valid .Keystore file, as you need this .Keystore signed to be able to update your existing apps/games.
Also is there intent to provide a service for maybe any new apps/games created in C3 to get a new .keystore, auto signed, with maybe using our login details from C3 for our Alias, and Keystore file Passwords, using these details would probably make this process less complicated.
Anyway, Thank you again for your earlier response.
EDIT
To be fair I don't mind doing this myself if Scirra provided a comprehensive tutorial, and I am sure most would go with that too.
Cheers
This is exactly my feeling towards CS3. I need up to date comprehensive tutorials so I don't have to search around just to properly make my games work on different appstore. I already know what CS3 can offer, but I need assurance that I can publish to the Appstore and/or Google Play without a hitch. That's why I don't want to dive yet paying $99 for C3 without knowledge of how I can incorporate it to my current and (future) games. My main concern really is publishing... to different app stores. Hope I Construct can solve this soon.