User cannot execute/sign/replace pending transaction: 422 an error occurred

[la1234512345]

Issue Category

Safe loading issue, doesnt load on any interface

What happened?

User is trying to sign nonce 9 but is unable to

• Transaction is pending 2 of 3, with the last signer being 0x6a5b9f9C9849e730CFa340ede3103d4E58a4ed49 without gas
• Tried signing the transaction without executing, user gets 400 error in Safe mobile, 422 error in metamask inapp browser, and 422 error as well in dev console using a desktop
• Tried replacing the transaction with same nonce but is getting the same errors above
  
  

Date and time this happened or you first noticed this issue

13-11-2023

Network

Ethereum Mainnet

Safe Address

0x5fF0A0EAC8281C1067Eab5b0359DA6BB71E24CB2

Token Address

na

Token Type

None

Transactions

No response

[JagoFigueroa]

Good morning team! I have been checking this with the infra team but unfortunately we are not able to reproduce it on our end 😞

Although we can see the error logs we would need some extra info to debug this issue. Could we ask for the complete response body the user is getting on these failing requests?

Thank you 🙏

[Claire-serveth]

Hi @JagoFigueroa I also have users having this error. Users were trying to initiate transactions on the web app (desktop) but getting error 422 while confirming the transaction on metamask mobile app connected via walletconnect (polygon and BSC networks):

I was able to reproduce the error via goerli network as well. Already tried in multiple browsers using the latest version of the MetaMask mobile app: v7.10.0 (1187).

[liliya-soroka]

safe-global/safe-wallet-web#2818 - we will check and update the ticket on the web app board

[Claire-serveth]

safe-global/safe-wallet-web#2818 - we will check and update the ticket on the web app board

Thank you so much @liliya-soroka 🙏

[liliya-soroka]

as an update from the safe-wallet-web board. The issue was related to the MM mobile app issue - MetaMask/metamask-mobile#7792.
Please, ask the user to follow the MM issue update

[CindyLo0]

Thank you @liliya-soroka, closing this issue.