Child Item

oauth fails in vs2022 in debug mode

oauth fails in Razor project when started in debug mode. When started without debugging everything is ok and I get my tokens.

When the dropbox page is loaded the debug output window shows all kinds off js code and html, takes a long time and then stops working.

this is the url I'm sending:

https://www.dropbox.com/oauth2/authorize?response_type=token&client_id=9xel3hm56djft05&redirect_uri=https://localhost:7280/DBXauth2

Find more posts tagged with

API

Abuse

Accepted answers

Greg-DB

Thanks for sharing that. From the screenshot, I see you're loading HTML from the Dropbox web site in your IDE output window itself. The Dropbox web site should only be loaded in the system web browser. I can't offer support for your platform or IDE themselves as those aren't made by Dropbox, so you may need to refer to the documentation or support resources for those for information on how to use them, e.g., how to open a URL in the system browser only.

All comments

Greg-DB

Can you share the name and version number of the web browser you're using to open the https://www.dropbox.com/oauth2/authorize... page when this fails?

A screenshot of the issue you're seeing may also be helpful for context. Thanks!

brtdvrs

browser is Edge version 112.0.1722.46, the default browser Visual Studio 22 uses for debugging. In the screenshot you see the debug output generated.

Greg-DB

brtdvrs

So how can i debug it vs 2022 ?

Greg-DB

@brtdvrs I'm not sure I understand your latest question. If you need help using Visual Studio, you'll need to refer to the documentation/support materials for that. Dropbox doesn't make Visual Studio itself so we can't offer support or guidance on how to use it in particular.

In your first post in this thread you shared the /oauth2/authorize URL that you constructed, and it sounds like that worked correctly when loaded into the system web browser (Edge, in this case). Note that whether you're running a debug version or a release version of your app, that is the proper procedure; you should only load that page in the system web browser.

If something with the Dropbox API or an official Dropbox SDK specifically isn't working as expected though, please share the details of that and we'll help however we can.