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
I think when tackling this we should also fix #1330
My best guess is that we wait for the safeTxHash. We should detect that it is a safeTxHash and poll that tx or always poll the SafeInfo additionally.
I haven't tested it yet but I think with the changes implemented in #3778 the user would now simply wait on the status screen without a timeout until the safe has executed the creation. We use the same global hook to monitor the txHash as we do for counterfactual safes so we should become aware of the transaction being executed.
Just tested #1330 again on this PR and can confirm that it doesn't work when signing but not executing the transaction in the parent safe. The tx monitor is trying to poll for the txHash (which is actually the safeTxHash) which it can't find so it errors out after a while. We could detect this as @schmanu suggests and in that case poll for either the safe info or the safeTxHash through our services.
What is the feature about
The status screen when creating a safe has multiple UX issues as documented here and #1484, #1871, Slack
The list of requirements
Designs/sketches
Links
The text was updated successfully, but these errors were encountered: