Skip to content

Improve Error Handling #44

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.

Sign up for GitHub

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

Jump to bottom
Open
adonesky1 opened this issue Jan 8, 2025 · 1 comment
Open

Improve Error Handling #44

adonesky1 opened this issue Jan 8, 2025 · 1 comment
Labels
team-wallet-api-platform

Comments

@adonesky1
Copy link
Collaborator

  • Probably worth adding a specific catch for if chrome.runtime.connect doesn't exist and throw a more helpful error
  • Other instances of bad error handling I'm sure!
@adonesky1
Copy link
Collaborator Author

adonesky1 commented Jan 9, 2025 •
edited
Loading

Image
Example of an error that we currently throw when there is not a valid multichain enabled instance of metamask presence

In this case, we should probably show an message on the page itself saying we aren't seeing any valid multichain enabled instances of metamask to connect to. If you're seeing this error make sure you have the right wallet/build enabled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
team-wallet-api-platform
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@adonesky1