You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 10, 2023. It is now read-only.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
initiate a transaction on web (Execute checkbox unchecked)
reject on mobile
before the fix: web app redirects to the tx with 0 signatures 🐞
Another bug this PR fixes:
make a Safe an owner of another Safe
connect the first Safe to the owned safe via WC and WC Safe App
create a tx (Execute unchecked)
before the fix: tx created with 0 signatures 🐞
After this fix, a tx will be signed correctly in both cases.
How this PR fixes it
When a created tx is rejected by the wallet, we throw an error and show an error snackbar. The tx is not created and the user is not redirected anywhere.
Also checks if the connected wallet is a smart contract and does an on-chain signature if yes.
katspaugh
changed the title
Fix: throw when WC rejects a created tx
Fix: throw when WC rejects a created tx + on-chain signing with a Safe signer via WC
Feb 21, 2022
@liliya-soroka I've just tested this, and I think the confusing part is that you need to separately execute the confirmation (on-chain signature) transaction on mobile. Until you do that, the queued tx won't have signatures.
Just for clarification: You need this notification (see snapshot) to show up in the "safe owner" before the tx stops showing the "0 out of x" signatures in the tx in the "safe own"
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What it solves
Dima noticed the following bug:
Another bug this PR fixes:
After this fix, a tx will be signed correctly in both cases.
How this PR fixes it
When a created tx is rejected by the wallet, we throw an error and show an error snackbar. The tx is not created and the user is not redirected anywhere.
Also checks if the connected wallet is a smart contract and does an on-chain signature if yes.