I notice if I try and test my app through the editor and Launch onto my phone it uses the debug.keystore based on the Cert SHA1 fingerprint. I believe this is what is happening as I checked the fingerprint of debug.keystore in C:\Users<my user>.android\debug.keystore and the fingerprint matched with the fingerprint that was listed in the error below from the log from ADB. My app in the Pklay Store uses a keystore I created and hence has a different fingerprint.
My question does anyone know if you can only do a test of the services such as leaderboard by uploading an APK to the console and then wait for it to be copied to the Play Store so the fingerprints match with what I specifiy in the UE4 build of the APK and what was setup in the Play Console when I first created the app in Google?
08-18 10:15:52.852 17061 18720 E PlayGamesServices[SignInAuthenticator]: ****
08-18 10:15:52.852 17061 18720 E PlayGamesServices[SignInAuthenticator]: **** APP NOT CORRECTLY CONFIGURED TO USE GOOGLE PLAY GAME SERVICES
08-18 10:15:52.852 17061 18720 E PlayGamesServices[SignInAuthenticator]: **** This is usually caused by one of these reasons:
08-18 10:15:52.852 17061 18720 E PlayGamesServices[SignInAuthenticator]: **** (1) Your package name and certificate fingerprint do not match
08-18 10:15:52.852 17061 18720 E PlayGamesServices[SignInAuthenticator]: **** the client ID you registered in Developer Console.
08-18 10:15:52.852 17061 18720 E PlayGamesServices[SignInAuthenticator]: **** (2) Your App ID was incorrectly entered.
08-18 10:15:52.852 17061 18720 E PlayGamesServices[SignInAuthenticator]: **** (3) Your game settings have not been published and you are
08-18 10:15:52.852 17061 18720 E PlayGamesServices[SignInAuthenticator]: **** trying to log in with an account that is not listed as
08-18 10:15:52.852 17061 18720 E PlayGamesServices[SignInAuthenticator]: **** a test account.
08-18 10:15:52.852 17061 18720 E PlayGamesServices[SignInAuthenticator]: ****
08-18 10:15:52.852 17061 18720 E PlayGamesServices[SignInAuthenticator]: **** To help you debug, here is the information about this app
08-18 10:15:52.852 17061 18720 E PlayGamesServices[SignInAuthenticator]: **** Package name : com.xxxx.xxxxx
08-18 10:15:52.852 17061 18720 E PlayGamesServices[SignInAuthenticator]: **** Cert SHA1 fingerprint: 27:14:57 … etc
08-18 10:15:52.852 17061 18720 E PlayGamesServices[SignInAuthenticator]: **** App ID from manifest : xxxxxxxx
08-18 10:15:52.852 17061 18720 E PlayGamesServices[SignInAuthenticator]: **** Check that the above information matches your setup in
08-18 10:15:52.852 17061 18720 E PlayGamesServices[SignInAuthenticator]: **** Developer Console. Also, check that you’re logging in with the
08-18 10:15:52.852 17061 18720 E PlayGamesServices[SignInAuthenticator]: **** right account (it should be listed in the Testers section if
08-18 10:15:52.852 17061 18720 E PlayGamesServices[SignInAuthenticator]: **** your project is not yet published).
08-18 10:15:52.852 17061 18720 E PlayGamesServices[SignInAuthenticator]: ****
08-18 10:15:52.852 17061 18720 E PlayGamesServices[SignInAuthenticator]: **** For more information, refer to the troubleshooting guide:
08-18 10:15:52.852 17061 18720 E PlayGamesServices[SignInAuthenticator]: **** http://developers.google.com/games/s…roubleshooting
08-18 10:15:52.852 17061 18720 E PlayGamesServices[SignInAuthenticator]: ****