MetaMask / MetaMask/metamask-extension
sentry CORS error in loop when installing freshly built from source or stable v9.8.4
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
**Describe the bug**
I have just built thies extension and installed into Chrome from folder
Chrome shows errors, and it is annoying to analyze as it happen every 2 seconds,
better view is on Network tab, where it is clear it is from sentry.js

So I guess this extensions is using https://github.com/getsentry/sentry-javascript somewhere
and it is not configured properly
Some searches give https://github.com/getsentry/sentry-javascript/issues/2518 -> https://blog.sentry.io/2016/05/17/what-is-script-error#the-fix-cors-attributes-and-headers
However, I don't know where exactly it should be applied.
In short, current version in GitHub some this issue unresolved.
**Steps to reproduce (REQUIRED)**
Steps to reproduce the behavior, libraries used with version number, and/or any setup information to easily reproduce:
1. Build `yarn dist` (follow https://github.com/MetaMask/metamask-extension#building-locally)
2. In Chrome `chrome://extensions` install uppacked and point to dist/chrome folder
3. See MetaMask with Errors red button in Chrome extension list `chrome://extensions`
**Expected behavior**
Should be no errors on load/init.
**Screenshots**
above
**Browser details (please complete the following information):**
- OS: MacOS 10.15
- Hardware Wallet: no
- Browser: Chrome 92.0.4515.107
- MetaMask Version: develop 81f274303 (current 9.8.4+)
**Additional context (Error Messages, etc.)**
```
git branch -v
* develop 81f274303 EIP-1559 - Only show advanced form toggle when radio buttons are present (#11713)
```
Contributor guide
Research direction
Start by running `yarn dist` and installing `dist/chrome` in Chrome, then inspect the Network errors from `sentry.js`. The fix is complete when the freshly built extension loads without recurring CORS errors or the red error indicator.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100