Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Events won't send from the console
See original GitHub issuehttps://github.com/getsentry/raven-js/pull/1080 updated captureMessage to check whitelistUrls before sending the event. However, events typed in from a browser console have a URL of <anonymous>, so the check fails.
This has affected all releases since 3.19:
In my experience it’s helpful to be able to trigger one-off events from the console to ensure that Raven is configured correctly (particularly when setting up Raven for the first time, or deploying a new version).
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
It seems to me that commands from the console should be properly associated with the site’s domain, instead of being marked as anonymous.
I’d expect to find that a lot of Sentry users rely on the old behavior. How are you supposed to be 100% sure that Sentry is working in production (w/ its usual production configuration) without being able to trigger an event from the console? Expecting users to always embed a call in their source code & then later remove it after testing is complete is too heavy-handed, IMO.
Closing due to inactivity. Feel free to reopen if still relevant.