Skip to content
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

Symbol Server sourcemaps not showing due to CORS issue? #191

Open
burnnat opened this issue Oct 16, 2023 · 3 comments
Open

Symbol Server sourcemaps not showing due to CORS issue? #191

burnnat opened this issue Oct 16, 2023 · 3 comments
Labels
bug Something isn't working tracked This issue is now tracked on our internal backlog

Comments

@burnnat
Copy link

burnnat commented Oct 16, 2023

Currently sourcemaps from Azure Artifacts symbol server are not loading for me, and looking in the "Source Maps Monitor" panel they all list the following error: "Unknown error requesting source map: Failed to fetch".

If I open the internal devtools console I see a lot of CORS errors that seem related:
console errors

I know this had been working for me previously but I haven't tried very recently so I'm not sure when that might have changed. If there are any other details I can provide, let me know!

Edge version: 118.0.2088.46 (Official build) (64-bit)

AB#47103421

@burnnat burnnat added the bug Something isn't working label Oct 16, 2023
@captainbrosset
Copy link
Contributor

Thanks so much for raising this. I'll make sure this is tracked by the team.

@captainbrosset captainbrosset added the tracked This issue is now tracked on our internal backlog label Oct 17, 2023
@burnnat
Copy link
Author

burnnat commented Sep 25, 2024

@captainbrosset Has anyone been able to look into this? I still see the same behavior despite following the setup article instructions exactly, and it doesn't seem to matter whether a PAT or Active Directory connection is used. If I launch the browser using .\msedge.exe --disable-web-security --user-data-dir="..." then the sourcemaps load great, but is there any possible solution that doesn't involve completely disabling the browser CORS policy?

@captainbrosset
Copy link
Contributor

@robpaveza for insights on the above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working tracked This issue is now tracked on our internal backlog
Projects
None yet
Development

No branches or pull requests

2 participants