05-14-2018 06:53
05-14-2018 06:53
Hello y'all,
I have been seeing "invalid client request" from a third party server when I use OAuth component to authorize. In trying to debug and give them URL I am sending, I am unable to see any http requests captured by a packet sniffer tool. So, I am stuck trying to convince that the issue is with server side or give them more details to help debugging. It works perfectly with Google OAuth. Pls help.
My details:
OS: MAC osx
Env: Fitbit studio & Simulator
Component: OAuth
<Oauth
settingsKey="oauth"
title="Authorize"
label="Login"
authorizeUrl="< authorize url >"
response_type="code"
redirect_uri="https://app-settings.fitbitdevelopercontent.com/simple-redirect.html"
clientId="< client id>"
nonce="39a4fdb7-0652-408b-9ec1-9ca81e044e39"
scope="offline_access"
onReturn = { async (data) => {
console.log("on return");
console.log(JSON.stringify(data));
}}
/>
05-30-2018 15:11
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.
05-30-2018 15:11
Are you trying to access your Fitbit data using the Web APIs or another set of APIs?
Best Answer