Uncaught TypeError: can't access property "TYPED_ARRAY_SUPPORT", e is undefined
Describe the bug
After installing MetaMask (from the Mozilla Addon Page), it cannot be opened through the corresponding button. The "home" page of MetaMask which opens after installations throws errors in the console (see below screenshot).
The main culprit seems to be
Uncaught TypeError: can't access property "TYPED_ARRAY_SUPPORT", e is undefined
Steps to reproduce (REQUIRED) Steps to reproduce the behavior, libraries used with version number, and/or any setup information to easily reproduce:
- Install Firefox Developer Edition
- Install MetaMask
- Wait until the "home" page opens
- Open console to see error
Expected behavior A working MetaMask version
Screenshots

Browser details (please complete the following information):
- OS: Windows 10
- Hardware Wallet: none
- Browser: Firefox Developer Edition 96.0b10 (64-Bit)
- MetaMask Version: 10.8.1
Stacktrace
Setting up Sentry Remote Error Reporting for 'production': SENTRY_DSN sentry-install.js:1:951
Removing intrinsics.Object.hasOwn sentry-install.js:1:102731
Removing intrinsics.%StringPrototype%.at sentry-install.js:1:102731
unreachable code after return statement ui-4.js:1:213222
unreachable code after return statement ui-4.js:1:214100
unreachable code after return statement ui-4.js:1:217103
unreachable code after return statement ui-5.js:10:643718
unreachable code after return statement ui-5.js:10:644208
unreachable code after return statement ui-5.js:10:644701
Uncaught TypeError: can't access property "TYPED_ARRAY_SUPPORT", e is undefined
ui-2.js:1:78669
t moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/ui-2.js:1
t moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/ui-2.js:1
e moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/ui-2.js:1
t moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/ui-2.js:1
e moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/ui-2.js:1
t moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/ui-2.js:1
e moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/ui-2.js:1
o moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/ui-2.js:1
<anonym> moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/ui-2.js:1
runModule moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/runtime-cjs.js:59
requireRelative moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/runtime-cjs.js:65
requireRelative self-hosted:1282
<anonym> moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/ui-1.js:1
runModule moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/runtime-cjs.js:59
requireRelative moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/runtime-cjs.js:65
requireRelative self-hosted:1282
<anonym> moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/ui-1.js:1
runModule moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/runtime-cjs.js:59
requireRelative moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/runtime-cjs.js:65
requireRelative self-hosted:1282
<anonym> moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/ui-0.js:7
runModule moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/runtime-cjs.js:59
requireRelative moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/runtime-cjs.js:65
requireRelative self-hosted:1282
<anonym> moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/ui-0.js:1
runModule moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/runtime-cjs.js:59
requireRelative moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/runtime-cjs.js:65
requireRelative self-hosted:1282
<anonym> moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/ui-0.js:1
runModule moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/runtime-cjs.js:59
requireRelative moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/runtime-cjs.js:65
requireRelative self-hosted:1282
<anonym> moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/ui-0.js:1
runModule moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/runtime-cjs.js:59
requireRelative moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/runtime-cjs.js:65
requireRelative self-hosted:1282
<anonym> moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/ui-0.js:1
runModule moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/runtime-cjs.js:59
requireRelative moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/runtime-cjs.js:65
requireRelative self-hosted:1282
<anonym> moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/ui-0.js:1
runModule moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/runtime-cjs.js:59
requireRelative moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/runtime-cjs.js:65
requireRelative self-hosted:1282
<anonym> moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/ui-10.js:1
runModule moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/runtime-cjs.js:59
entryExports moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/runtime-cjs.js:36
map self-hosted:224
loadBundle moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/runtime-cjs.js:35
<anonym> moz-extension://16d743df-dd7d-448e-92a0-419e01970db1/ui-10.js:1
Related: #10918 #9196 etc.
Hello @manniL ! Would it be possible to get the entire error stack?
Sure! Added it to the original issue 👍
How to solve this type of F problem on Chrome?**
Content Security Policy of your site blocks the use of 'eval' in JavaScript` The Content Security Policy (CSP) prevents the evaluation of arbitrary strings as JavaScript to make it more difficult for an attacker to inject unathorized code on your site. To solve this issue, avoid using eval(), new Function(), setTimeout([string], ...) and setInterval([string], ...) for evaluating strings. If you absolutely must: you can enable string evaluation by adding unsafe-eval as an allowed source in a script-src directive. ⚠️ Allowing string evaluation comes at the risk of inline script injection. 2 directives Source Location Directive Status lockdown-install.js:1 script-src blocked lockdown-install.js:1 script-src blocked Learn more: Content Security Policy - Eval
This issue has been automatically marked as stale because it has not had recent activity in the last 30 days. It will be closed in 60 days. Thank you for your contributions.
This issue was closed because there has been no follow activity in 90 days. If you feel this was closed in error please provide evidence on the current production app in a new issue or comment in the existing issue to a maintainer. Thank you for your contributions.