OK, I solved this, so for the record …
If you are using the Meteor user accounts built in then you make no changes to your Meteor code. This is what I suspected. The only thing you have to do is set more things up in Google developer console.
The below is as documented in the cordova google plus plugin, but as it’s not Meteor specific there is a lot of wood around the trees you are looking for, so the below distills the specific thing that I needed to do.
Assuming you had google login working successfully in the web app, then you would have set up a project in Google APIs and created an OAuth 2.0 Client ID for Web application in the Credentials section. There you will have to set up authorised JS origins and redirect URIs.
In order for your google login button to work in an android build, you need to set up another OAuth 2.0 Client ID, this time for Android. Here you don’t specify redirect URIs and the like, but instead you must supply two things in common with your Meteor Android build:
- The Package name that is a reversed domain path that you must also set as your app Id in the
App.info()details yourmobile-config.jsfile, as exampled here:
App.info({
id: 'com.<your domain>.<sub domain>'
// etc
});
- The SHA-1 certificate finger print taken from the certificate that you used to sign your APK.
That’s all - easy when you know how!