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

Crypto payment UI does not refresh after transaction is confirmed #1974

Closed
asnaith opened this issue Feb 23, 2022 · 0 comments · Fixed by #1976
Closed

Crypto payment UI does not refresh after transaction is confirmed #1974

asnaith opened this issue Feb 23, 2022 · 0 comments · Fixed by #1976
Assignees
Labels
Issue: Bug 🐛 Added to issues relating to a critical severity bugs. Product: Files

Comments

@asnaith
Copy link
Member

asnaith commented Feb 23, 2022

Description
On the crypto payment modal - after clicking the “pay via metamask” button and signing the transaction in the metamask extension the button became disabled and displayed a spinner on it until the payment had been confirmed.

Once the payment had been confirmed the spinner stopped and the button became enabled. The UI did not automatically update and I had to close the modal and refresh the browser in order to see the changes being reflected in the UI.

To Reproduce
Steps to reproduce the behavior:

  1. Go to settings > subscription tab
  2. Choose an annual plan and navigate through the payment flow, choosing crypto as the payment method
  3. Choose ethereum as the payment type
  4. Click "Pay with metamask" (or click "Connect Wallet" first if displayed)
  5. Sign the transaction in metamask and wait for the transaction confirmation

Expected behavior
It is expected that once the transaction has been confirmed in metamask that the UI updates, closing the crypto payment modal and showing the new plan details on the settings page.

Desktop (please complete the following information):

  • Not device / OS / browser specific
@asnaith asnaith added Issue: Bug 🐛 Added to issues relating to a critical severity bugs. Product: Files labels Feb 23, 2022
@FSM1 FSM1 self-assigned this Feb 24, 2022
@FSM1 FSM1 closed this as completed in #1976 Mar 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue: Bug 🐛 Added to issues relating to a critical severity bugs. Product: Files
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants