No, just forget about it. When you update your app, you just update version numbers and that's it.
Thank you. I'll do this way so
The special case is if you already had an app that you were signing with jarsign, and some time later you want to publish it with XDK. But if you start with the XDK and stay with it, you shouldn't need to care about it.
Also to expand on what codah said i've seen people email intel to get their keystore for their app when moving from XDK to something else. But yeah if this is your first version just use XDK to sign it;s much easier
Develop games in your browser. Powerful, performant & highly capable.
codah , volkiller730
Thank you for the tips!
soooooo why are you signing manually?
If you check signed it's debug signed and you cannot upload it to the store as far as I know.
Learn from this
https://www.scirra.com/tutorials/1318/g ... ndroid-xdk
> soooooo why are you signing manually? > If you check signed it's debug signed and you cannot upload it to the store as far as I know.
> soooooo why are you signing manually?
>
No my apps are fine and I only do it this way.
Like codah say's my apps are fine too
I've uploaded my app a couple hours ago! Super cool
The check signed APK can be uploaded without any problems actually.
Congratulations