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 has been archived by the owner on Mar 28, 2023. It is now read-only.
The dApp does not catch the new transaction when speeding up in MetaMask. The page does not progress to step 2 or move to the URL of the deposit contract address. When refreshing the page there is no contract address to refresh to and the minter is brought back to step 1 to create a new deposit.
When the transaction completes, the page should progress to step 2 and request transaction approval to get public key.
Environment details:
OS: OS X Mojave
Web Browser: Brave Version 1.14.84 Chromium: 85.0.4183.121 (Official Build) (64-bit)
Wallet: Metamask (Chrome extension), Version 8.0.10
The text was updated successfully, but these errors were encountered:
canceling the Ethereum tx request on MM to initiate a deposit is not handled, the Error should be caught and probs a notification shown + a Button shown to cancel the process or retry 😄 a similar result is to be expected if MM is connected with a hardware wallet and there is a timeout on the signature
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description:
The dApp does not catch the new transaction when speeding up in MetaMask. The page does not progress to step 2 or move to the URL of the deposit contract address. When refreshing the page there is no contract address to refresh to and the minter is brought back to step 1 to create a new deposit.
Steps to reproduce the behavior:
Expected behavior:
When the transaction completes, the page should progress to step 2 and request transaction approval to get public key.
Environment details:
OS: OS X Mojave
Web Browser: Brave Version 1.14.84 Chromium: 85.0.4183.121 (Official Build) (64-bit)
Wallet: Metamask (Chrome extension), Version 8.0.10
The text was updated successfully, but these errors were encountered: