OPENSEA: setApprovalForAll via OpenSea website will trigger Metamask error

[zhangzhongnan928]

1. list a STTT on OpenSea
2. Opensea will ask you to setApprovalForAll
3. Metamask shows error https://youtu.be/rLfS3pNm-yc (reproducible with MM 11.11.4)

Message: Invalid data; should be 'approve' method, but instead is 'setApprovalForAll'

Code: Error

Stack:
Error: Invalid data; should be 'approve' method, but instead is 'setApprovalForAll'
  at a.getCustomTxParamsData (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/ui-7.js:1:182560)
  at Z (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/ui-8.js:1:60482)
  at ga (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/ui-1.js:33:246078)
  at Pl (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/ui-1.js:33:291005)
  at Iu (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/ui-1.js:33:276868)
  at Au (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/ui-1.js:33:276793)
  at Eu (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/ui-1.js:33:274133)
  at chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/ui-1.js:33:232483
  at n.unstable_runWithPriority (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/ui-2.js:1:221729)
  at Yi (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/ui-1.js:33:232192)
  at eo (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/ui-1.js:33:232428)
  at Zi (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/ui-1.js:33:232363)
  at bu (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/ui-1.js:33:270899)
  at Ia (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/ui-1.js:33:249735)
  at chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/ui-7.js:1:326789

Tried JoyID with STTT in Opensea, works fine.
Tried MM with Uniswpa V# NFT in Opensea, works fine.

[SmartLayer]

This issue is severe because it renders MetaMask unusable on Chrome—once triggered, MetaMask won't work, requiring reinstallation. Interestingly, Firefox is affected but doesn't cause MetaMask to fail in the same way.

To replicate, make sure you own some STTT tokens. Visit https://testnets.opensea.io/account, log in, click "List for sale," and follow the listing process. This bug can happen on both Firefox and Chrome, specifically with Metamask versions 11.11.4 (Chrome) and 11.10.1 (Firefox). The one I tried when reproducing, was one of the tokens of this collection in Sepolia https://testnets.opensea.io/collection/st404-testing-token-v3-4/

The core problem arises from MetaMask mistaking certain NFTs for ERC20 tokens due to their ERC20-like features. Consequently, when attempting to use setApprovalForAll for NFT approvals on platforms like OpenSea, MetaMask swaps it for approve, believing it's correcting an error. This misstep is despite OpenSea's correct usage of setApprovalForAll.

[Fast288]

hi, i still have this issue with forge token. ca: 0x73576a927cd93a578a9dfd61c75671d97c779da7
Can't list it on opensea.
how can i fix it?

[Fast288]

yes, its the token contract adress: 0x73576A927Cd93a578a9dFD61c75671D97c779da7
FORGE token

its ERC404.

I cant list it to on opensea, my metamask gives me the error.

[Fast288]

ok, any idea how i can fix the issue?
friends of me don't have this issue and they're also using Metamask

[Fast288]

Hi,
any update on this? how can i get around this problem?

[SmartLayer]

Hi, any update on this? how can i get around this problem?

You are using $FORGE token, which is not of this github repo:

0x73576A927Cd93a578a9dFD61c75671D97c779da7

I followed up your post when you posted to MetaMask, please discuss this issue there following my reply there MetaMask/metamask-extension#18507 (comment)