You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I try to submit a transaction using the adapter for signature, the notification from walletconnect to the mobile app doesn't always come, and if it does, nothing happens after confirmation. In addition, the following error appears in the console:
{context: 'client'} 'No matching key. keychain: {someKeyChain}' at vt.get (index.es.js:1:16678) at It.getSymKey (index.es.js:1:19474) at It.decode (index.es.js:1:18740) at EventEmitter.<anonymous> (index.es.js:1:25051) at EventEmitter.emit (events.js:158:1) at Ot.onMessageEvent (index.es.js:1:37303)
Has anyone encountered this error? And how did you fix it?
Maybe there are other ways to confirm transaction via walletconnect for tron?
Any help would be greatly appreciated, thank you!
The text was updated successfully, but these errors were encountered:
Hello everyone!
I have a problem with transactionsigning when using walletConnect-TRON through the adapter from TronWeb
@tronweb3/walletconnect-tron
This is an example of code in which the provider is initialized and then used to sign the transaction:
When I try to submit a transaction using the adapter for signature, the notification from walletconnect to the mobile app doesn't always come, and if it does, nothing happens after confirmation. In addition, the following error appears in the console:
{context: 'client'} 'No matching key. keychain: {someKeyChain}' at vt.get (index.es.js:1:16678) at It.getSymKey (index.es.js:1:19474) at It.decode (index.es.js:1:18740) at EventEmitter.<anonymous> (index.es.js:1:25051) at EventEmitter.emit (events.js:158:1) at Ot.onMessageEvent (index.es.js:1:37303)
Has anyone encountered this error? And how did you fix it?
Maybe there are other ways to confirm transaction via walletconnect for tron?
Any help would be greatly appreciated, thank you!
The text was updated successfully, but these errors were encountered: