04-21-2015 11:45
04-21-2015 11:45
Seeking comments on how we handle transitioning from OAuth 1.0A to 2.0 in your .NET client code.
https://github.com/aarondcoleman/Fitbit.NET/issues/46
--Aaron
06-06-2015 10:28
Community Moderator Alumni are previous members of the Moderation Team, which ensures conversations are friendly, factual, and on-topic. Moderators are here to answer questions, escalate bugs, and make sure your voice is heard by the larger Fitbit team. Learn more
06-06-2015 10:28
Hello there @aarondcoleman! In order to better assist you, can you please clarify this! Looking forward to your reply!
Best Answer06-07-2015 04:25
06-07-2015 04:25
Pretty sure he is asking the dev community what they want for migrating from OAuth 1.0 to OAuth 2.0 in the Fitbit.Net framework he does...pretty straight forward.
Best Answer06-10-2015 09:30
06-10-2015 09:30
That's correct.
As an update, I have posted a video walkthrough of where we are with the new 2.0 version of the Fitbit.NET library and there's plenty of room for some constructive feedback. Again note, we're proposing some pretty big breaking changes for a 2.0, once finalized will become what is maintained going forward. The previous version will exist but not be further maintained.
Explination of new changes for OAuth 2.0 here:
Current branch:
https://github.com/aarondcoleman/Fitbit.NET/tree/async-portable
Best Answer07-07-2016 10:25
07-07-2016 10:25
Has anyone found an example of the Fitbit with OAuth 2.0 working in webforms. I was able to do this without any issues in the version with OAuth 1.0, however, the OAuth 2.0 version I'm having issues with.
If there is an example, can someone post it. I know there is an MVC example, but I need a Webforms example.
Best Answer05-02-2018 07:07
05-02-2018 07:07
Is this library still maintained? I’ve tried following the video and the sample projects but can’t get it to work for me
Best Answer