-
Notifications
You must be signed in to change notification settings - Fork 265
Google Fit Connector Issue #266
Comments
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:
|
@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). |
@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. |
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:
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! |
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
but then I try to pull it into a report and I get this
I get the following issue when I try running the function fetchAggregateData
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?
The text was updated successfully, but these errors were encountered: