添加链接
link管理
链接快照平台
  • 输入网页链接,自动生成快照
  • 标签化管理网页链接

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 [bug] SecurityError: Blocked a frame with origin "http://localhost:3000" from accessing a cross-origin frame. #1840 [bug] SecurityError: Blocked a frame with origin "http://localhost:3000" from accessing a cross-origin frame. #1840 vietddude opened this issue Jan 26, 2024 · 17 comments

https://github.com/WalletConnect/web-examples

Summary

Got this error while click to button Open Connect Modal
clicking

List of related npm package versions

"@emotion/react": "^11.11.3",
"@emotion/styled": "^11.11.0",
"@fontsource/roboto": "^5.0.8",
"@mui/material": "^5.15.6",
"@tanstack/react-query": "^5.17.19",
"@wagmi/core": "^2.5.0",
"@web3modal/wagmi": "4.0.0-3a0b2d54",
"axios": "^1.6.5",
"next": "^14.1.0",
"react": "^18",
"react-dom": "^18",
"react-hook-form": "^7.49.3",
"viem": "^2.5.0",
"wagmi": "^2.5.0"

I believe I am seeing the same issue. I am trying to do a write operation on a smart contract and it looks like the browser is trying to open a modal. Not sure. Oddly, I did see a scenario where I got a popup on my mobile Metamask to confirm the transaction. That happened once, I am not seeing any response on my mobile Metamask. Looks like my desktop browser is trying to show a modal with a QR code but the transaction is just timing out. I have:

"@web3modal/wagmi": "4.1.1",
"wagmi": "^2.5.11",

I have the following error on my browser's console:

[Error] Blocked a frame with origin "https://XXX-XXX-XX-XX-XXX.ngrok-free.app" from accessing a frame with origin "https://verify.walletconnect.org". Protocols, domains, and ports must match.

This is Verify API and doesn't affect the functionality of the SDK, it is correct if the domain doesn't match with the verified one, but this error should go away on production. So for staging non-verified links this error is expected.

@glitch-txs this is happening to me on production. Can you provide more details on how to fix it? I have the metadata.domain matching my production domain

sorry, yeah, I meant I have the metadata.url matching my prod url.
this is what I have:

const ethersConfig = defaultConfig({
  metadata:  {
      name: 'Some Name',
      description: 'Some description',
      url: 'https://<mysubdomain>.<mydomain>.io/'
      icons: [''],
  rpcUrl: '<rpc>',
  defaultChainId: 1,