sdk: [UI]: How to catch the `TON_CONNECT_SDK_ERROR` error?
Your Question
My application is triggering tons of TON_CONNECT_SDK_ERROR errors with the message Operation aborted.
However, those are all uncaught promise exceptions. How can I catch them to handle them properly?
Here is the code of the application, note that I am handling errors in the status change:
this.tonConnectUI = new TonConnectUI({
manifestUrl: `${myUrl}/tonconnect-manifest.json`,
});
this.tonConnectUI.onStatusChange(
async (status: ConnectedWallet | null) => onStatusChange,
(error: TonConnectError) => {
trackError('WalletConnectError', {
name: error.name,
message: error.message,
});
},
Context
No response
What have you tried so far?
No response
Relevant Code or Commands
No response
Documentation Check
- Yes, I have checked the documentation.
About this issue
- Original URL
- State: open
- Created 2 years ago
- Comments: 20
the image in “this works” comment is unaccessible, the issue still persists
@uintptrs
layout.tsx
import { TonConnectUIProvider } from ‘@tonconnect/ui-react’;
<body> <TonConnectUIProvider manifestUrl="https://your site url/tonconnect-manifest.json"> ... </TonConnectUIProvider> </body>==================================================
And create tonconnect-manifest.json in the “public” folder.
Structure of tonconnect-manifest.json
Hi everyone,
I’m using the tonconnect/ui-react package to trigger wallet connections in my project. The wallet connection is established successfully, but after 5 to 10 minutes, I start seeing the following error:
[TON_CONNECT_SDK_ERROR] TonConnectError Operation aborted Error: Operation aborted at abortController.signal.addEventListener.once (http://localhost:3000/static/js/bundle.js:64575:14) at signal.addEventListener.once (http://localhost:3000/static/js/bundle.js:64414:108) …
Initially, everything works fine, but after some time, this error pops up. It seems to be related to the connection aborting after a certain amount of inactivity.
Has anyone encountered this issue or knows what could be causing the connection to abort after a delay? Please any one help me to resolve this?
@abhiyana
One possible way to catch it is by using the javascript
unhandledrejectionevent and identifying the ton connect sdk error:It’s not ideal though because it does not prevent third party dependencies from catching those unhandled promise errors as well (such as analytics or error aggregation components).