There is no ''client_email" in Google Play Android Developer-*.json about supply HOT 9 CLOSED

Hi @dkornev that definitely shouldn't be happening. Can you confirm the name of your .json file as it was downloaded from the console, does it start with "Google Play Android Developer" or "client_secret"?

from supply.

Hi @asfalcone ! It starts from "Google Play Android Developer". The instructions look simple and I'm almost sure that I'm doing everything as described... But anyway, is it wrong *.json file?

from supply.

I'm able to find 2 different .json files file the console. The "Google Play Android Developer" one does include the client_email expected by the google auth parser but the "client_secret" one does not.

One thing you can try is putting client_email field into the .json file. The value for this is the email address that can be found under Settings -> Api Access -> Service accounts and looks like "[email protected]".

Can you also try walking through the process of creating a brand new service account and creating the service account key as well?

from supply.

@asfalcone Could you please describe a json structure for me? I'll try to create one by myself.
My json file just contains a plain set of characters:
http://screencast.com/t/76Cy7MrPJx5
It doesn't even look like JSON )

from supply.

That seems very wrong! That looks like the private_key if I had to guess.

The json file provided by the google play developer console should have this format:
{
"type": "service_account",
"project_id": "",
"private_key_id": "",
"private_key": "",
"client_email": "",
"client_id": "",
"auth_uri": "https://accounts.google.com/o/oauth2/auth",
"token_uri": "https://accounts.google.com/o/oauth2/token",
"auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
"client_x509_cert_url": "https://www.googleapis.com/robot/v1/metadata/x509/xx%40api-project-xx.iam.gserviceaccount.com"
}

from supply.

Ok, I got it. Will try more tomorrow.
Thank you very much, @asfalcone !

from supply.

@asfalcone
I click on 'Create Service Account' button from API Access tab
http://screencast.com/t/O2fjmbPH2
then I create Service account key
http://screencast.com/t/XLJqCVmPn
I select JSON key type as on a picture below
http://screencast.com/t/KFLyvQ5jkb
and I get a json with no 'client_email' there
http://www.screencast.com/t/76Cy7MrPJx5

If I create OAuth client ID credentials
the result JSON looks better
http://screencast.com/t/80FerHXPK0LZ
but still there is no 'client_email' attribute there, because it's not for service account credentials, I guess.

Could you tell me what I"m doing wrong?
Thanks

from supply.

@dkornev 😩 This is definitely not what I expect to be happening (and I see different behavior in the developer console)

2 more suggestions:

1. Create a brand new service account. When selecting the account here, http://screencast.com/t/KFLyvQ5jkb, the last option should be something like "Create new account" instead of selecting the existing one your have.
2. Use the deprecated .p12 format and manually specify the issuer param

from supply.

This issue was migrated to fastlane/fastlane#1961. Please post all further comments there.

fastlane is now a mono repo, you can read more about the change in our blog post. All tools are now available in the fastlane main repo 🚀

from supply.