That’s just how it is on Android. There’s a lot going on behind the scenes, and the developers figure those messages might be important to someone, so they left them in. This is why it’s so important to have a strategy like “cut off the log immediately after the error” or “filter based on pre-determined keywords.”
Filtering is nicer in theory, except when you get a false negative. For instance, filtering by “Google” should give you almost everything related to the Google Play Services, but what if there’s an important line that happens not to contain “Google”?
You’re supposed to paste the fingerprint into the developer console; it’s then used to generate the client ID. This client ID contains the application ID, a.k.a.
GOOGLE_PLAY_GAMES_ID. Actually, you’re supposed to do this twice: once for each of your certificates (debug and release).
Go through this list and double-check that you did everything right. We already dealt with #4, and #6 isn’t relevant yet, but check the others.