admin管理员组

文章数量:1292126

We launched a public sale of nfts. While buying the nfts, the transaction is done successfully and shown on etherscan but after the transaction we got this error message twice only yet.

Error message is as follows:

Request of type 'smartTransaction:showSmartTransactionStatusPage already pending for origin chrome extension://nkbihfbeogeaeaoehlefnkodbefgpgknn. Please wait."

Being a QA, I am unable to reproduce this error. Kindly Help.

On buying an nft, the transaction should be done successfully without any error message. 99% of the time we dont get an error and it works fine but we got this error twice only.

We launched a public sale of nfts. While buying the nfts, the transaction is done successfully and shown on etherscan but after the transaction we got this error message twice only yet.

Error message is as follows:

Request of type 'smartTransaction:showSmartTransactionStatusPage already pending for origin chrome extension://nkbihfbeogeaeaoehlefnkodbefgpgknn. Please wait."

Being a QA, I am unable to reproduce this error. Kindly Help.

On buying an nft, the transaction should be done successfully without any error message. 99% of the time we dont get an error and it works fine but we got this error twice only.

Share Improve this question edited Feb 13 at 11:15 DarkBee 15.6k8 gold badges72 silver badges116 bronze badges asked Feb 13 at 11:07 Murtaza NaqviMurtaza Naqvi 211 bronze badge 2
  • Is this an actual programming-related question? If so, please edit your question to specifically and clearly define the problem that you are trying to solve. Additional details — including all relevant code, error messages, and debugging logs — will help readers to better understand your problem and what you are asking. – DarkBee Commented Feb 13 at 11:16
  • Please clarify your specific problem or provide additional details to highlight exactly what you need. As it's currently written, it's hard to tell exactly what you're asking. – Community Bot Commented Feb 13 at 23:55
Add a comment  | 

1 Answer 1

Reset to default 2

The issue is related to the latest MetaMask extension version 12.11.0.

You may encounter this problem when executing multiple transactions sequentially—specifically when a second transaction is triggered immediately after the successful completion of the first transaction.

In this version, the first MetaMask pop-up functions correctly, but the second pop-up may indicate a failure, even though the transaction will eventually be confirmed on the blockchain.

My observation is that if you do not close the extension—something you might do after the first transaction by clicking the "Close Extension" button—the next transaction loads within the same pop-up. This causes it to use outdated values from the initial load, leading to a simulated failure. However, the transaction does not fail in reality, as the previous transaction on the blockchain has already been completed.

FYI, this issue does not occur if you close the extension after the first transaction and allow a new pop-up to open for the next transaction.

本文标签: