|
I'm not really sure how the APK signing is supposed to work really, so I thought I'd ask here and see if others might be willing to impart some advice. When signing with Unity, I have a keystore setup (took me a bit of digging around on the web, but I got it). Should this keystore be used for everything or just for this one game? Also, there are the public and private keys that I need to sign with a particular password. Should these be the same, different, or is it mostly irrelevant? Also, does one or more of these need to change between projects? Sorry to be such a noob on this, but I'm mostly used to internal corporate development, where signing just doesn't ever take place. Thanks much in advance for any and all advice anyone can provide.
(comments are locked)
|
|
@kimstock thats not an answer, use comments or even better, ask your own question for help. @Nekoyoubi you use it for that particular game - most generally, and its VERY important you remember that password information later, TRUST ME! write that keystore password/username password down! now as for making a single game, you use a single signature (keystore, all that stuff) and when you make another unique game (or sequel or expansion pack...idk) then you use a different keystore and password and such...and again DO NOT FORGET THAT PASSWORD OR YOUR APP MUST BE RE-UPLOADED THUS LOSING ALL DOWNLOADS (atleast the figure of your downloads) AND FORCING YOU TO USE A NEW KEYSTORE!!! I cant stress this enough!
(comments are locked)
|
|
Hi, I would also like some info on this as i signed my apk using unity and uploaded it to the android market and when i try to download and install it, it says "Installation error: Package file was not signed correctly"
(comments are locked)
|
