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

[ETH] Getting "Something went wrong, please try again" error when executing transaction via nest safes #481

Closed
Claire-serveth opened this issue Jul 10, 2024 · 3 comments

Comments

@Claire-serveth
Copy link
Collaborator

Claire-serveth commented Jul 10, 2024

Issue Category

Transaction execution issue

What happened?

User was trying to execute a transfer transaction using another safe wallet as an owner but getting this error instead:
image

Steps to reproduce:

  1. Client safe with 2/2 threshold (EOA and safe wallet) where EOA initiated and sign the transaction
  2. Connect Owner safe wallet to confirm
  3. Clicked execute button
  4. Getting the error on the screenshot

User was using Safari and Brave browsers for each safe wallet (Client and owner safes).

I tried reproducing the error on my end via Sepolia network (with owner safe wallet having no balance, same with the user), but I'm not getting the same error (transaction succeeded). Might be isolated to ETH network only?

Client safe: https://app.safe.global/transactions/history?safe=eth:0x3C5142F28567E6a0F172fd0BaaF1f2847f49D02F

Owner safe: https://app.safe.global/transactions/history?safe=eth:0x88B3e82A55c5215d0499Da4bBd63fc3e43F26232

Provided a workaround to only sign/confirm using the owner safe and execute using the other EOA owner (or non-owner). The transaction succeeded but the second transaction was stuck again, and the owner safe wallet was not able to sign/confirm (not until after some time). [Is this related to the delay issue on ETH network?]

Intercom link: https://app.eu.intercom.com/a/inbox/pynbtguw/inbox/shared/all/conversation/212174700009245?view=List

Date and time this happened or you first noticed this issue

10-07-2024

Network

Ethereum Mainnet

Safe Address

No response

Token Address

No response

Token Type

None

Transactions

No response

@liliya-soroka
Copy link
Member

safe-global/safe-wallet-web#3940 - please, follow the issue

@liliya-soroka
Copy link
Member

please, check if the issue is still relevant

@CindyLo0
Copy link
Collaborator

CindyLo0 commented Aug 2, 2024

Ticket has been marked resolved. Closing this. Thank you

@CindyLo0 CindyLo0 closed this as completed Aug 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants