1
Ask a Question / What is your Keystore/Certificate Strategy?
« on: November 01, 2015, 04:34:31 pm »
Hey people,
Every time I create a new project, I go to the android certificate section of the mobile settings. At first, I used to create a new certificate for every project, which I finally realized was stupid because Stencyl was overwriting the certificate each time, and when I uploaded updates to the Play Store, Playstore told me my certificates didn't match (duh!)
However, now my problem is this:
I have ONE freaking certificate that I try to use, I use all the same name/password/etc.
However, it used to be that every time I'd switch to a new computer, I'd bring over the certificate file and place it where it needed to be, but Stencyl would never generate an apk. I USED to just create a new certificate to see if that was the problem and it most often was. I found that if I created an entire new certificate I could just create an apk no problem, but if I ever wanted to use the original certificate (again, on a different computer, at my office or something) it wouldn't work.
So, that has me thinking...am I doing it wrong? Other engines I've used don't seem to have such a wonky certificate process. What are other people's methods for producing multiple mobile applications on the same and other machines?
Thanks.
Every time I create a new project, I go to the android certificate section of the mobile settings. At first, I used to create a new certificate for every project, which I finally realized was stupid because Stencyl was overwriting the certificate each time, and when I uploaded updates to the Play Store, Playstore told me my certificates didn't match (duh!)
However, now my problem is this:
I have ONE freaking certificate that I try to use, I use all the same name/password/etc.
However, it used to be that every time I'd switch to a new computer, I'd bring over the certificate file and place it where it needed to be, but Stencyl would never generate an apk. I USED to just create a new certificate to see if that was the problem and it most often was. I found that if I created an entire new certificate I could just create an apk no problem, but if I ever wanted to use the original certificate (again, on a different computer, at my office or something) it wouldn't work.
So, that has me thinking...am I doing it wrong? Other engines I've used don't seem to have such a wonky certificate process. What are other people's methods for producing multiple mobile applications on the same and other machines?
Thanks.