You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
After confirming the scopes in the sign in flow of Dropbox, I get the "Authorization error: Nonce mismatch" error when letting AppAuth perform the token exchange automatically (see next section). When tapping on "Manual" instead of "Auto", logging in and then tapping on "Code Exchange" everything seems to work fine.
To Reproduce
Steps to reproduce the behavior:
After not getting it to work with my own application, I tried the Example-iOS_Swift-Carthage. I will describe the steps to reproduce based on this example.
Tap on "Auto"
Allow the sign in to dropbox
Login to Dropbox and Confirm the access scopes of the application
Expected behavior
The sign in should be completed successfully.
Additional Context
As explained above, I took the original example. I tried retrieving the token with and without specifying the client secret. What's really weird is that I can see a response from https://api.dropboxapi.com/oauth2/token containing an access token and an id token when inspecting the network traffic using Proxyman.
The text was updated successfully, but these errors were encountered:
Describe the bug
After confirming the scopes in the sign in flow of Dropbox, I get the "Authorization error: Nonce mismatch" error when letting AppAuth perform the token exchange automatically (see next section). When tapping on "Manual" instead of "Auto", logging in and then tapping on "Code Exchange" everything seems to work fine.
To Reproduce
Steps to reproduce the behavior:
After not getting it to work with my own application, I tried the Example-iOS_Swift-Carthage. I will describe the steps to reproduce based on this example.
Expected behavior
The sign in should be completed successfully.
Screenshots (I will provide logs instead)
Environment
Additional Context
As explained above, I took the original example. I tried retrieving the token with and without specifying the client secret. What's really weird is that I can see a response from
https://api.dropboxapi.com/oauth2/token
containing an access token and an id token when inspecting the network traffic using Proxyman.The text was updated successfully, but these errors were encountered: