Same issue here. When I start my app, the Google Play logo pops up, then disappears, and no functionality of the plugin is working any further.
I think it might have to do with the SHA1 signature. Here's the thing: The SHA1 signature created by the build-in APK signer of C3 is used as an upload key to Google Play, not the actual signing key. The 'real' signing is done by Google itself (unless you deactivate it).
I'll do some testing, maybe the project in Google Play Game Services must be provided with the C3 upload SHA1 signature, not the signing signature of Google.
Ashley I would like to reach out to Iain Shorter, but I can't reference him. Could you please forward this post to him? Thanks.
According to this Github post, I'm on the right track: https://github.com/Scirra/Construct-3-bugs/issues/1927
I think we have to replace the Google SHA1 signature with our own upload signature in order to make the Google Play plugin work, is that true?
Could we do it the other way round, too (downloading the Google certificate, which is of type .der, and use that to sign our apps before uploading)?
I'm being really careful with this as you need to contact the Google support team for a signature change (no matter if upload key or signature key), and you can only do that ONCE for an app.