Installation Steps Incomplete (Expo installation)

[patrick1011]

Hi,

Thanks for your work on the library. I'm trying to get it working on my expokit (ejected expo application) but am having some difficulties. GoogleFit.authorize() is rejected with message...

{
  "message": "Authorization cancelled",
  "success": false,
}

when I tap my e-mail address in the auth flow.

I've read through issues in the repo, one of which (#90) mentions that

the client_secrets.json file generated after the https://developers.google.com/fit/android/get-api-key process should be store exactly at this location

The installation steps make no mention of this fact however. And neither does https://developers.google.com/fit/android/get-api-key as of June 25th 2019. There is also a discussion in (#47) about the location of a client_secrets.json file.

Any ideas what we may have missed? If there is something I'm happy to add to the README with the complete steps necessary.

[thowthoww]

Same issue here.

[wuodland]

Go here and setup your correct sha1 key. Follow steps as mentioned on Stack Overflow: https://stackoverflow.com/questions/15727912/sha-1-fingerprint-of-keystore-certificate

[jguix]

I had to perform some additional steps:

• Create OAuth2 credentials using your debugging keystore. Follow this link and click on Create credentials → OAuth Client ID to do that. https://console.developers.google.com/apis/credentials

1. select Android as application type.
2. enter your SHA-1 certificate's fingerprint. To get the SHA1 execute in a shell terminal:
   keytool -list -v -keystore ~/.android/debug.keystore -alias androiddebugkey -storepass android -keypass android
3. enter your app package name.

• Install the Google Fit app on the device / emulator.
• Synchronize data in the Google Fit application (eg see all activities of the last month). Even if your data is in the cloud, you installed Google Fit and logged in, this step is necessary for the data to come through the library.

[fega]

Same Issue Here :/

[fega]

Hello again!, after some hours looking for a solution I got the problem.

Expo Ejected Apps have their own debug.keystore located in the root of the generated android folder.

so you can use this command to get the SHA1 key:

keytool -list -v -keystore ./debug.keystore -alias androiddebugkey -storepass android -keypass android

@StasDoskalenko I think this info worth it to add it in the install instructions and maybe renaming this thread as "Expo Installation" also could make easier for anyone looking for help :)

[JoelOnGithub]

Hi,

I am also getting { success: false, message: 'Authorization cancelled' } as a response, after I sign in with my google account in the android app. I have followed all the necessary steps to create a client id. However, I did not do anything with the client id. Is that supposed to be the case?

Thanks for the help

[akiladevinda]

@JoelOnGithub I have still facing the same issue. If any solutions ?

[antoinedelp]

Hi, I was experiencing the same issue. In my case, everything was working fine in development, but I could not make it work in production. The problem was that I was using Signed Bundle, which made my SHA different from the one in my keystore.

If you are also using app signing, make sure to add the correct signing to your Google API Credentials!
Find more info about this issue here

[ibrag474]

I have the same problem, adding SHA-1 to credentials at Google Cloud console does not help.