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
Crash-Report Modal 404s with EU DSN #11813
Comments
I guess Sentry doesn't route the URL here properly. |
Shouldn't
|
Server fix getsentry/sentry#69815 |
ceddy4395
pushed a commit
to ceddy4395/sentry
that referenced
this issue
Apr 29, 2024
…ry#69815) The browser SDK is still creating URLs for the error-embed views using `sentry.io` for customers in all regions. Remove the error-embed view from the region pin list and create DSN based routing. I don't love this solution, but it should be robust enough to handle the scenarios that customers are having problems with. Refs HC-1182 Refs getsentry/sentry-javascript#11813
The fix for the server endpoints has been deployed, this scenario should be working now for EU organizations. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/nextjs
SDK Version
7.112.2
Framework Version
next 13
Link to Sentry event
No response
SDK Setup
No response
Steps to Reproduce
I tested in Nextjs, but the user who originally reported it is using Angular-ivy 112.2
showReportDialog()
Expected Result
Crash Report Modal to show
Actual Result
Changing the DSN back to a US DSN will work immediately.
The text was updated successfully, but these errors were encountered: