04-08-2016 11:42
04-08-2016 11:42
I have tried to set expires_in to 2592000 as mentioned in the docs. After authenticating, I get the callback url and the parameter expires_in is always set to 86400.
Is it possible to set a longer expires_in for implicit grant?
04-08-2016 13:30
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
04-08-2016 13:30
This is working for me. Here is my example Authorization Page URL:
Best Answer04-08-2016 14:13
04-08-2016 14:13
once i include prompt=login consent, then it doesn't respect the expires_in?
Can you see if that applies to you too? Is there a work around?
Best Answer04-08-2016 15:56 - edited 04-08-2016 16:00
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
04-08-2016 15:56 - edited 04-08-2016 16:00
@slingkid: I was able to reproduce this issue. We hope to have a fix for it within the next two weeks.
As an interim solution, `prompt=consent` without the `login` works, ex: https://www.fitbit.com/oauth2/authorize?response_type=token&client_id=228YX6&redirect_uri=https%3A%2...
Best Answer