-
Notifications
You must be signed in to change notification settings - Fork 408
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
Fix: uncaught error in GeoblockingProvider #3938
Conversation
Branch preview✅ Deploy successful! Website: Storybook: |
ESLint Summary View Full Report
Report generated by eslint-plus-action |
📦 Next.js Bundle Analysis for safe-wallet-webThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
Coverage report
Test suite run success1433 tests passing in 198 suites. Report generated by 🧪jest coverage report action from ef85a98 |
@compojoom , could you help to test , please? |
Returned back - it's possible to use swap and the swap feature is not hidden as on prod |
Geoblocking is only configured in prod. |
What it solves
There are uncaught errors logged to Sentry coming from
GeoblockingProvider
.I've refactored the hook to use
useAsync
that catches async errors.