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

Handle API Errors Gracefully #127

Open
teddyjfpender opened this issue Jan 2, 2024 · 1 comment
Open

Handle API Errors Gracefully #127

teddyjfpender opened this issue Jan 2, 2024 · 1 comment
Labels
beta testing Arised during beta testing bug Something isn't working

Comments

@teddyjfpender
Copy link
Contributor

Handling Network Errors 🚨

Sometimes, when querying for a wallet's state from an API, the response might be an error, leaving the wallet unable to obtain the state it expects (e.g. AccountInfo). One known instance of this impacting users is in prevent users from progressing/completing the onboarding (either restoring or creating a new wallet).

Expected behaviour

Gracefully handle API errors that allow users to continue onboarding. Signifiers should communicate to the user issues/errors if they are relevant -- good interaction design is paramount.

Example Logs

When creating a new wallet and typing in the correct word to prove knowledge of the created mnemonic, users are left stuck at the onboarding screen with Next button highlighted but not progressing to the Overview page. Console's logs:
image

@teddyjfpender teddyjfpender added bug Something isn't working beta testing Arised during beta testing labels Jan 2, 2024
@FilipHarald
Copy link

I agree that allowing user to continue onboarding would be optimal. But a first step could be to just display that there is a connection error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
beta testing Arised during beta testing bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants