Closed herfytoken closed 5 years ago
I have the same problem. Any idea what could be?
I also have this problem
Google updated the Fit API to prevent REST applications from sending a packageName (which only Android applications can do). Pull request #63 will fix this.
Should be resolved by #63
Hi -
This application has been fantastic for me. Thank you!
I've been able to use it to log Fitbit steps into Google Fit, and thus get a discount on my health insurance, which syncs with Google Fit, but not Fitbit. This is great!
I tried running the application today, and got this 403 error.
I've tried trouble-shooting this several ways, without success.
First, I deleted the google.json file in the auth folder, and re-ran the auth_google.py script. I was able to get the client ID & secret from the Google API console, which suggests the application was still recognized on their end. After re-creating the google.json file, I re-ran the app.py script, and the same error occurred.
Then I tried creating a new application on the Google side, following the instructions as before. I started by deleting google.json, then created the new application on Google's side, and then ran auth_google.py with the new application's client ID & secret. I re-ran app.py, and again got the same error.
How do I move forward from here?