-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[blazor] [wasm] Unable to debug after redirect to oidc #60613
Comments
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsDescribe the bugWhen on Visual Studio you start with "F5" it starts the project enter debug and it hits all breakpoints. To ReproduceStart Debug and redirect to any external URI Exceptions
Further technical details
dotnet --info Output
|
cc @thaystg |
@LeandroPT, could you please attach/paste here the dotnet[version].js that is being used by your application? I just want to make sure that we are not hitting something that is already fixed. You can click on the dotnet[version].js file and then copy and paste the content here. Also sending me the full name of dotnet.js file would also help me. |
Oh, I don't need this information anymore, I could reproduce. |
Então @thaystg está do vosso lado certo? |
hahahah!! |
Describe the bug
When on Visual Studio you start with "F5" it starts the project enter debug and it hits all breakpoints.
However, as soon there is a redirect to an external login URL (oidc) the browser closes because de Visual Studio Debugger reports a fail message and cancels debug.
To Reproduce
Start Debug and redirect to any external URI
Exceptions
Further technical details
dotnet --info Output
The text was updated successfully, but these errors were encountered: