-
Notifications
You must be signed in to change notification settings - Fork 2
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
iOS Error: Failed to create transaction. Network request failed with an unexpected error. Please try again later. (Error 422422) #330
Comments
checking |
Thank you. 🙏 Also, additional context - when user initiated the tx from the Web app, it's successful and it shows in the queue tab, but when checking the Transactions tab in the safe mobile app, it gives error "Failed to load transaction", a similar issue reported here #327 |
@inahlikenoother we checked and saw that we could open the tx details now. Is this issue still persists? |
Let me check with the user 🙏 |
User responded and said that he can open the tx details now on the Safe mobile app, however, he's unable to sign it as it gives the same error " Failed to load tx details " |
Please, take into account that if the MM mobile app is used for the tx creation, signing , there is an issue with signature from the MM mobile app - MetaMask/metamask-mobile#7792 |
Issue Category
Other
What happened?
When user tries to initiate a send transaction in the iOS Safe mobile app, it gives an error
User's safe mobile app is not in Read only mode and they already imported owner keys. User said this was working previously, and they updated their Safe mobile app 2 days ago, and now they're experiencing this issue. Another owner also tried to initiate the tx using his own device (iOS as well) and also get this error.
User tried on Web app and it works fine, they were able to initiate the send transaction. Tx was successfully submitted on the web app and it shows in Queue tab, but checking the transaction in the Safe mobile app gives another error "Failed to load transaction" a similar issue reported in #327
IOS version 16.6.1
Safe mobile app version 3.24.2
Date and time this happened or you first noticed this issue
20-11-2023 10:58
Network
Ethereum Mainnet
Safe Address
0x001d2D93B3758FBe792E329cca5Cd579a105EE96
Token Address
No response
Token Type
None
Transactions
No response
The text was updated successfully, but these errors were encountered: