Swagger UI hits nonexistant breakpoint in Edge (with debugging) when returning from oauth2 authentication while any breakpoint is set in the project.

[HunterAhlquist]

Q&A (please complete the following information)

• OS: Windows 10
• Browser: Edge (debugging enabled)
• Version: 7.2.0
• Method of installation: NuGet
• Swagger-UI version: 7.2.0
• Swagger/OpenAPI version: 7.2.0

Content & configuration

Example Swagger/OpenAPI definition:
N/A

Swagger-UI configuration options:

SwaggerUI({
  c.SwaggerEndpoint("/swagger/v1/swagger.json", "[REDACTED] v1");
  c.OAuthClientId(ad["ClientId"]);
  c.OAuthScopes(ad["Scopes"]);
  c.OAuthUsePkce();
  c.OAuthScopeSeparator(" ");
  c.ConfigObject.AdditionalItems.Add("requestSnippetsEnabled", true);
})

Describe the bug you're encountering

In my API project that uses Microsoft/Azure oauth2 authentication, whenever I set a breakpoint anywhere in my project to debug endpoints before logging in, upon returning from the auth page, the browser appears as if a browser breakpoint was hit.

To reproduce...

Steps to reproduce the behavior:

1. Create an API that utilizes oauth2
2. Set a breakpoint anywhere in the project (an authorized controller for example)
3. Attempt to log into oauth2
4. Upon returning with authentication, SwaggerUI will show the above screen, unable to proceed

Expected behavior

The UI continues to operate as no breakpoint should have been hit after returning from authentication.

Screenshots

My IDE shows no breakpoint hit, no other tabs are open.

Additional context or thoughts

There are a lot of different interactions going on here, not 100% sure where this could actually be happening, SwaggerUI is my best guess. I want to use edge due to Microsoft automatically logging in to speed up debugging

[robert-hebel-sb]

We are doing some housekeeping on our issue tracker. This issue has been inactive for over a year and we have not been able to tackle it yet.

Is this still important to you? If so, please leave a comment – we'd love to know if you're still affected. If we don't hear back in 7 days, we'll close this issue to tidy up the tracker.

Thank you for your understanding!

[robert-hebel-sb]

No response received after 7 days. Closing this issue to keep the tracker tidy. If you're still affected, please reopen or create a new issue with updated details.