Token undefined about fitbit-js

[smurthas]

is there anything returned in the first parameter (the error params)?

[felicia0]

Hi, I am receiving the exact same error. Have you been able to solve it?

[smurthas]

When you first started up the test app, did you navigate straight to /getStuff? That would definitely result in that error since there isn't a token yet. There should probably be a redirect to / if token is undefined.

[felicia0]

No, when I start up the test app, I navigate to /. However, the callback:
fitbitClient.getAccessToken(req, res, function (error, newToken) {
console.log('never get here, but sure we should');
if(newToken) {
token = newToken;
res.writeHead(200, {'Content-Type':'text/html'});
res.end('Now get stuff');
}
});
doesn't seem to get called

[smurthas]

After you get redirected back from fitbit.com, where do you end up?

[felicia0]

If I put callback as /getStuff, then I end up at /getStuff with the error "TypeError: Cannot read property 'oauth_token_secret' of undefined." Since I am never getting to the callback of fitbitClient.getAccessToken(...

If I leave callback blank I get redirected to a fitbit page with "You have successfully authorized access to [app], Please return to [app] and enter the following PIN when requested:
9oetrufr52c1het7d0l1v8693j." However, my app is a browser app in dev.fitbit.com.

Any ideas?

[smurthas]

the callback needs to be /

[ryanburgess]

When the callback is set to / I get stuck in a loop on the Fitibit site giving the application access.

[smurthas]

@ryanburgess are you still seeing this issue? (also, see #14)