Skip to content
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

[Bug]: Metamask stuck after clicking confirm #18234

Closed
AdamB2023 opened this issue Mar 20, 2023 · 11 comments
Closed

[Bug]: Metamask stuck after clicking confirm #18234

AdamB2023 opened this issue Mar 20, 2023 · 11 comments
Labels
needs-information Needs additional information from the user who reported the issue Sev2-normal Normal severity; minor loss of service or inconvenience. team-confirmations-secure-ux DEPRECATED: please use "team-confirmations" label instead type-bug

Comments

@AdamB2023
Copy link

AdamB2023 commented Mar 20, 2023

Describe the bug

image

Steps to reproduce

  1. Confirm the transaction

Version

10.26.1

Build type

Chrome Web Store

Browser

Chrome

Operating system

Windows

Additional context

The TX is confirmed, however the window stuck like this, need to close and reopen from extension.

@bschorchit bschorchit added team-confirmations-secure-ux DEPRECATED: please use "team-confirmations" label instead needs-reproduction Sev2-normal Normal severity; minor loss of service or inconvenience. labels Mar 20, 2023
@bschorchit
Copy link

cc: @seaona for visibility

@danjm
Copy link
Contributor

danjm commented Mar 20, 2023

@AdamB2023

Three questions:

  1. what version are you on?
  2. any errors if you open the dev console?
  3. does this happen with every type of transaction? or only when you attempt a specific type (e.g. simple ETH send vs. erc20 token transfer vs. contract interaction prompted by a dapp vs. NFT approval vs. something else?)

@AdamB2023
Copy link
Author

AdamB2023 commented Mar 20, 2023

@danjm
Version 10.26.1

Yes, there were some errors, if i will get it once again, i will post here.

It happens randomly, and doesn't depend on the network / RPC.
I'm doing mostly trades on DEXes, or transfers, no NFTs involved.
Right now, it happened for Arbitrum swap confirmation on 1INCH.

@gregors
Copy link

gregors commented Mar 23, 2023

seeing this in OSX as well

@gregors
Copy link

gregors commented Mar 24, 2023

I'm able to reproduce the bug more consistently with the browser in Full Screen

@AdamB2023
Copy link
Author

AdamB2023 commented Mar 24, 2023

@danjm below you can see warnings and errors i got today when it stuck.

Warnings:

runtime-lavamoat.js:8914 Removing intrinsics.%ArrayPrototype%.toReversed
visitProperties @ runtime-lavamoat.js:8914
runtime-lavamoat.js:8914 Removing intrinsics.%ArrayPrototype%.toSorted
visitProperties @ runtime-lavamoat.js:8914
runtime-lavamoat.js:8914 Removing intrinsics.%ArrayPrototype%.toSpliced
visitProperties @ runtime-lavamoat.js:8914
runtime-lavamoat.js:8914 Removing intrinsics.%ArrayPrototype%.with
visitProperties @ runtime-lavamoat.js:8914
runtime-lavamoat.js:8914 Removing intrinsics.%ArrayPrototype%.@@unscopables.toReversed
visitProperties @ runtime-lavamoat.js:8914
runtime-lavamoat.js:8914 Removing intrinsics.%ArrayPrototype%.@@unscopables.toSorted
visitProperties @ runtime-lavamoat.js:8914
runtime-lavamoat.js:8914 Removing intrinsics.%ArrayPrototype%.@@unscopables.toSpliced
visitProperties @ runtime-lavamoat.js:8914
runtime-lavamoat.js:8914 Removing intrinsics.%StringPrototype%.isWellFormed
visitProperties @ runtime-lavamoat.js:8914
runtime-lavamoat.js:8914 Removing intrinsics.%StringPrototype%.toWellFormed
visitProperties @ runtime-lavamoat.js:8914
runtime-lavamoat.js:8914 Removing intrinsics.%FunctionPrototype%.apply.prototype
visitProperties @ runtime-lavamoat.js:8914
runtime-lavamoat.js:8924 Tolerating undeletable intrinsics.%FunctionPrototype%.apply.prototype === undefined
visitProperties @ runtime-lavamoat.js:8924
runtime-lavamoat.js:8914 Removing intrinsics.%FunctionPrototype%.bind.prototype
visitProperties @ runtime-lavamoat.js:8914
runtime-lavamoat.js:8924 Tolerating undeletable intrinsics.%FunctionPrototype%.bind.prototype === undefined
visitProperties @ runtime-lavamoat.js:8924
runtime-lavamoat.js:8914 Removing intrinsics.%TypedArrayPrototype%.toReversed
visitProperties @ runtime-lavamoat.js:8914
runtime-lavamoat.js:8914 Removing intrinsics.%TypedArrayPrototype%.toSorted
visitProperties @ runtime-lavamoat.js:8914
runtime-lavamoat.js:8914 Removing intrinsics.%TypedArrayPrototype%.with
visitProperties @ runtime-lavamoat.js:8914
 Property eval will not be hardened because it is scuttled by LavaMoat protection. Visit https://github.com/LavaMoat/LavaMoat/pull/360 to learn more.
(anonymous) @ lockdown-more.js:74
runtime-lavamoat.js:11626 missing dep: ethjs>number-to-bn>bn.js requested buffer
getRelativeModuleId @ runtime-lavamoat.js:11626
runtime-lavamoat.js:11626 missing dep: ethjs-contract>ethjs-abi>bn.js requested buffer
getRelativeModuleId @ runtime-lavamoat.js:11626
runtime-lavamoat.js:11626 missing dep: ethjs>bn.js requested buffer
getRelativeModuleId @ runtime-lavamoat.js:11626
runtime-lavamoat.js:11626 missing dep: ethjs>ethjs-unit>bn.js requested buffer
getRelativeModuleId @ runtime-lavamoat.js:11626
sentry-install.js:1 WARNING: Missing strong random number source
runtime-lavamoat.js:11626 missing dep: @metamask/eth-token-tracker>ethjs>bn.js requested buffer
getRelativeModuleId @ runtime-lavamoat.js:11626
notification.html#confirm-transaction/3243385637544598/approve:1

Errors

Error in event handler: Error: StreamProvider - Unknown response id for response: [object Object]
  at a._onResponse (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/ui-3.js:1:489340)
  at a._write (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/ui-3.js:1:489565)
  at _ (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-3.js:1:34397)
  at chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-3.js:1:37581
  at y.write (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-3.js:1:37608)
  at t.m (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-3.js:1:26357)
  at d (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-0.js:99:215887)
  at o.emit (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-0.js:99:218882)
  at w (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-3.js:1:21157)
  at v (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-3.js:1:20972)
  at _.push (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-3.js:1:21786)
  at a.exports._write (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-2.js:8:959973)
  at _ (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-3.js:1:34397)
  at chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-3.js:1:37581
  at y.write (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-3.js:1:37608)
  at t.exports.m (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-3.js:1:26357)
  at d (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-0.js:99:215887)
  at o.emit (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-0.js:99:218882)
  at w (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-3.js:1:21157)
  at v (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-3.js:1:20972)
  at _.push (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-3.js:1:21786)
  at t.exports._onMessage (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-1.js:12:255693)
  at chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-1.js:12:255540

@seaona
Copy link
Contributor

seaona commented Apr 5, 2023

Thank you all for your comments and apologies for the inconvenience. This issue is fixed on the upcoming release 10.28.1. You should be able to see it in the following days

@bschorchit
Copy link

Hey @AdamB2023 and @gregors, are you still experiencing this on versions 10.28.1 or 10.28.2?

@bschorchit bschorchit added needs-information Needs additional information from the user who reported the issue and removed needs-reproduction labels Apr 10, 2023
@AdamB2023
Copy link
Author

Didn't happen for me so far. Will reply if happens again.

@bschorchit
Copy link

Closing this for now as it seems to have been solved. Let us know if anyone comes across this issue again!

@Abbasjafri-syed
Copy link

@bschorchit look at this metamask is not popping up when try to conduct a txn else opening like when have to connect to a site
almost for every site

image

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-information Needs additional information from the user who reported the issue Sev2-normal Normal severity; minor loss of service or inconvenience. team-confirmations-secure-ux DEPRECATED: please use "team-confirmations" label instead type-bug
Projects
None yet
Development

No branches or pull requests

6 participants