When I created my application in the Google Play Console, I enabled App Signing by Google Play.
This was a huge mistake, but I didn’t realize it until now when I have started implementing Play services.
If I just build my apk and install it on my phone I am not allowed to connect to my google play services.
The apk must be signed by Google, so I am forced to build the apk, upload it to google play, and then download it on my phone.
This is absolute insanity.
I must be missing something.
I refuse to believe that I am supposed to go through this incredibly lengthy process every time I want to test the smallest of changes regarding the GPGS features.
The callback string from Social.localUser.Authenticate simply says “Authentication failed” or “Authentication cancelled” if I build the apk directly to my phone.
I contacted google play’s developer support and got it confirmed that I am indeed forced to upload my apk to google play and then download it again to my phone if I want access to the google play services.
I don’t know what to say.
My mind is completely blown by what a pain in the ass this is.
It takes F.O.R.E.V.E.R. to test simple changes to google play services…
I’m very disappointed.
Thanks for sharing your experience. I was struggling with the Authentication Cancelled issue which doesn’t inform error details. I just realized I have to upload apk everytime and I’m assured by your experience.
Hi, i dont know if there is an update about that so, we still need to build it apk (or aab) and test it in the phone. I mean we cant test it in the Unity Editor ?