- Home /
Android app signing confusion
A few months ago I built and released my first Unity game on Android. I always found it strange that I didn't have to deal with app signing as I have had to when building Android apps with other tools. I assumed, foolishly, that Unity was somehow handling this signing for me in the background.
Today I opened the project on my Macbook to make some updates, and when I tried to upload my apk to the play store I got an error saying that it was a debug apk and needed to be signed. I created a new key and signed it, but then I was told it was signed with the wrong key (as you would expect).
I went back to the Windows 10 PC that I used originally, made my app updates there, and built the app again. This time the play store accepted the unsigned apk. Strange right?
Can anyone explain to me why the play store will take the unsigned app when I create it on my Windows 10 PC, and not on the Macbook? Both machines are running Unity version 5.5.0f3.