Hi folks,
does anybody also has issues with 3rd party Oauth Buttons in the settings component?
I always get this error: Uncaught (in promise) #<Object> and absolutely have no glue where it
comes from, thus it doesn't appear regularly. As todoist uses a 3 step authorization, the code for the token generation is passed in the onReturn method, which causes an build error (cannot find global value 'Promise'). @JonFitbit Is there a possibility to handle an invalid callback
url issue, when the permission is not granted by the user? It should redirect to https://app-settings.fitbitdevelopercontent.com/simple-redirect.html (?error=access_denied), but particularly for todoist (3-step Oauth authorization) it misses the state parameter with the redirection to the app settings. Furthermore todoist keeps the token, as it never expires. Thats why it never asks for credentials anymore, which was a reason why my app couldn't be approved for publication. It's getting a little bit depressing... ;-(
<Oauth
settingsKey="oauth"
title="todoist Authentication"
label="Approve Access to todoist"
status= {getDisplayWebAPIStatus(props)}
authorizeUrl="https://todoist.com/oauth/authorize"
requestTokenUrl="https://todoist.com/oauth/access_token"
clientId= { CLIENT_ID }
clientSecret= { CLIENT_SECRET }
scope="data:read,data:delete,data:read_write,task:add,project:delete"
pkce="true"
state= "jd7383kandnjw762"//{utils.randomStr(10)}
onReturn = { async (data) => {
props.settingsStorage.setItem("excode", data.code);
}}
/>
