Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid/expired user token #3

Open
gotnull opened this issue Jan 15, 2015 · 2 comments
Open

Invalid/expired user token #3

gotnull opened this issue Jan 15, 2015 · 2 comments

Comments

@gotnull
Copy link

gotnull commented Jan 15, 2015

No matter what I try, I'm always getting an invalid/expired user token in my widget.

I've executed the fitbit_authorizer.rb and can successfully generate a PIN every time, but it always returns as invalid/expired in the widget when I access http://localhost:3030/sampletv

@gotnull
Copy link
Author

gotnull commented Jan 15, 2015

Clean installation:

Rails 4.1.6
Ruby 2.1.2p95 (2014-05-08 revision 45877) [x86_64-darwin13.0]

Listening on 0.0.0.0:3030, CTRL+C to stop

scheduler caught exception:
undefined method []' for nil:NilClass /Users/fulvio/Projects/dashing-fitbit/lib/fitbit.rb:23:indevice'
/Users/fulvio/Projects/dashing-fitbit/jobs/fitbit.rb:13:in block in <top (required)>' /Users/fulvio/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/rufus-scheduler-2.0.24/lib/rufus/sc/jobs.rb:230:incall'
/Users/fulvio/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/rufus-scheduler-2.0.24/lib/rufus/sc/jobs.rb:230:in trigger_block' /Users/fulvio/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/rufus-scheduler-2.0.24/lib/rufus/sc/jobs.rb:204:inblock in trigger'
/Users/fulvio/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/rufus-scheduler-2.0.24/lib/rufus/sc/scheduler.rb:430:in call' /Users/fulvio/.rbenv/versions/2.1.2/lib/ruby/gems/2.1.0/gems/rufus-scheduler-2.0.24/lib/rufus/sc/scheduler.rb:430:inblock in trigger_job'

@bcongdon
Copy link

This is because Fitbit has switched entirely from OAuth to OAuth2. The gem used to authenticate with Fitbit, Fitgem is incompatible with Oauth2, so this widget will no longer function.

You can check out my fork - which adds OAuth2 support - if you're still interested.

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

No branches or pull requests

2 participants