Google fit support #110
Google fit support #110
Conversation
|
Updated for the latest master. The check fail is weird - there seems to be a problem that occasionally pops up if you run the unit tests lots of times. |
|
Just rebased this against the current master and it seems the google fit API has changed a bit and it no longer works :( I'll fix it up.. |
|
Rebased again and still works, but uploaded activities still don't appear on the fit dashboard so it's of limited utility. If anyone can work out how to make them appear then please have a go :) |
|
Is this dead ? |
|
is help needed here? |
|
Feel free to pick it up and have a look. I couldn't work out how to make an activity that would appear in the Fit dashboard and app - although it does appear when queried back through the API. I kinda lost interest because I found Fit overall not very useful. |
cpfair
force-pushed
the
master
branch
2 times, most recently
from
da1b4e7 to
1081891
Compare
mduggan
force-pushed
the
google-fit-support
branch
from
e80036d to
6b6e57d
Compare
|
After letting this rot for a long time I went back and updated it. The commit history is now a lot cleaner and it should work. I haven't tested actual syncing after rebasing, because Dropbox is broken out of the box on Vagrant at the moment it seems, and I don't trust testing syncing against any of my real trackers. Connecting works fine though. |
|
So is this in the beta version? I see the main website hasn't been updated. With the massive market share that Google has you'd think this would be a priority. |
A first version of google fit support. Seems to work, but it's sometimes hard to tell - the APIs are still not very good - there are still lots of bugs in the web display and the app.
This includes and extends the OAuth2 changes I made in PR #103, so merging this gets those changes too.
Resolves #86.