Hey, Rob, thank you for the tip. If I can’t get the new client ID after all, I’ll try that route.
Thanks again.
Naomi
So, the root of this problem was SHA1 being pre-filled along with other items when I linked an app to the Game Services.
Pre-filled items are all valid except for SHA1, and because the example SHA1 and pre-filled SHA1 are different, it’s so easy to automatically think that Google system retrieved the correct SHA1 for the app.
Pre-filling it with an invalid SHA1 is a bug that Google will be fixing (per the Google contact I communicated with.) Once it’s fixed, this whole SHA1 trap should be gone.
Naomi
Yes, them pre-filling the SHA1 value with a bogus key is wrong on so many levels. It burned me. It’s going to burn more people before it’s said and done. I wish I could stick an image of Admiral Ackbar from Star Wars in the Guide to bring people’s attention to that block saying “Its a TRAP!”