keep getting SIGN_IN_FAILED when requesting history data in my own app.

Question

keep getting SIGN_IN_FAILED when requesting history data in my own app.

eggman87 opened this issue 9 years ago · comments

Matthew Harris commented 9 years ago

Do we need to include the api key? If so what is the name of it in the meta data tag.

RyDev · Answer 1 · Tue Dec 15 2015 04:01:59 GMT+0800 (China Standard Time)

I am seeing this same issue. What did you do to resolve this issue? @eggman87
❓

Matthew Harris · Answer 2 · Tue Dec 15 2015 04:45:37 GMT+0800 (China Standard Time)

@RyanNewsom I honestly can not remember. I closed it because it was something obvious but not well documented.

Make sure you have oauth credentials setup in the api console.
Make sure you also have enabled fitness api.

https://support.google.com/cloud/answer/6158857?hl=en

RyDev · Answer 3 · Tue Dec 15 2015 07:07:24 GMT+0800 (China Standard Time)

Thanks, I actually got it working right after I asked you.
👍

Paul Rashidi · Answer 4 · Tue Dec 15 2015 09:19:58 GMT+0800 (China Standard Time)

Make sure your Consent Screen is also configured within your Cloud project as well as the packageName and SHA1 for the cert you're using are also registered (even if just building a debug build). I don't believe the API key needs to be specified for FIT, but it is used for Maps.

RyDev · Answer 5 · Tue Dec 15 2015 11:43:39 GMT+0800 (China Standard Time)

I said I had it working, but thank you!

Paul Rashidi · Answer 6 · Wed Dec 16 2015 00:12:40 GMT+0800 (China Standard Time)

Yep, saw that @RyanNewsom Just wanted to log some resolution steps for others that stumbled upon this issue (like you did).