Skip to content
This repository has been archived by the owner on Sep 3, 2020. It is now read-only.

Google Fit Connector Issue #266

Open
Mike7154 opened this issue Oct 2, 2019 · 4 comments
Open

Google Fit Connector Issue #266

Mike7154 opened this issue Oct 2, 2019 · 4 comments

Comments

@Mike7154
Copy link

Mike7154 commented Oct 2, 2019

I'm not sure why this isn't working for me. I am following the guide. It says "unsafe" and I proceed anyways. Then when I try to get the data it throws an error.

I get to here just fine
image

but then I try to pull it into a report and I get this
image

I get the following issue when I try running the function fetchAggregateData
image

It may be obvious, but I'm not much of a programmer, just a little python.
Any ideas on how to get around this to use this connector?

@diminishedprime
Copy link
Contributor

diminishedprime commented Oct 8, 2019

Looks like part of the setup is missing from the instructions. I'll try to update the instructions when I have some time, but you'll need to also do the following:

  1. Switch your apps scripts project to a Standard GCP Project.
  2. Add the Google Fit API to the newly created cloud project.
  3. Make sure your manifest includes the OAuth scopes needed.

@falcaopetri
Copy link

@diminishedprime, any updates on how to set-up Google Fit Connector?

I tried to switch to a Standard GCP Project and enable the Fit API as you mentioned. The problem is that I then need to create credentials for the Fitness API, which requires an OAuth API Verification by Google (OAuth API Verification FAQ).

@skimdankish
Copy link

@falcaopetri Not sure I understand the problem? Are you unable to create credentials or do not want to create credentials? I had followed these steps and has been working from me. Though as I mentioned from #289 I rolled back, but it's been working great since then, no issues.

@falcaopetri
Copy link

The problem that I was refering to was that, after enabling the Fitness API and creating the OAuth credential, I was redirected to the Credentials view which stated:

image
Besides having to fill many configurations and having to wait for Google's approval, I stumbled upon a $15,000 fee, which didn't make any sense.

Because of all of that, I suppose I ended up not even trying to access the connector after enabling the Fitness API. Turns out that it is indeed working.

Knowing that you got it to work made it a lot easier, @skimdankish. Thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants