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
micahalcorn opened this issue
Jul 10, 2023
· 0 comments
Labels
bugSomething isn't workingdappRelating to OUSD.comfrontendWorks related to frontendOETHOETH related thingsP2Small number of users are affected, major cosmetic issueui/uxWorkd that requires design and product overview
I connected the iOS Safe app to our preview build and minted using ETH and the Zapper. The transaction worked fine on-chain and there were no console errors in the browser. However, the form state never changed and my transaction never appeared in the history.
While this wallet + browser combination is uncommon, anyone who mints or swaps from a Safe is likely a high-value user. We should solve this one so that these users don't accidentally submit duplicate transactions.
The text was updated successfully, but these errors were encountered:
micahalcorn
added
bug
Something isn't working
P2
Small number of users are affected, major cosmetic issue
dapp
Relating to OUSD.com
ui/ux
Workd that requires design and product overview
OETH
OETH related things
frontend
Works related to frontend
labels
Jul 10, 2023
bugSomething isn't workingdappRelating to OUSD.comfrontendWorks related to frontendOETHOETH related thingsP2Small number of users are affected, major cosmetic issueui/uxWorkd that requires design and product overview
I connected the iOS Safe app to our preview build and minted using ETH and the Zapper. The transaction worked fine on-chain and there were no console errors in the browser. However, the form state never changed and my transaction never appeared in the history.
While this wallet + browser combination is uncommon, anyone who mints or swaps from a Safe is likely a high-value user. We should solve this one so that these users don't accidentally submit duplicate transactions.
The text was updated successfully, but these errors were encountered: