walletconnect-monorepo: Unauthorized pairing update request
Describe the bug
I receive the error {"context":"client"}{"context":"client/pairing"} Error: Unauthorized pairing update request when initializing the wallet connect client on React Native. This error shows 16-250 times when present.
SDK Version (if relevant)
- Client: React Native
- Version:
"@walletconnect/client": "^2.0.0-beta.26"
To Reproduce Steps to reproduce the behavior: Initialize the client on React Native
client = await WalletConnectClient.init({
controller: true,
projectId: Config.WALLET_CONNECT_PROJECT_ID,
relayUrl: 'wss://relay.walletconnect.com',
metadata: {
name: 'Test',
description: 'Test',
url: Config.WALLET_CONNECT_METADATA_URL,
icons: ['https://walletconnect.com/walletconnect-logo.png'],
},
storageOptions: {
// eslint-disable-next-line @typescript-eslint/ban-ts-comment
// @ts-ignore
asyncStorage: AsyncStorage,
},
})
Expected behavior Initialize client without receiving errors
Screenshots

Smartphone (please complete the following information):
- Device: Any Android or iPhone
- OS: Any Android or iOS
Additional context It seems to work well outside of the error being present.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 1
- Comments: 16 (7 by maintainers)
@IljaDaderko I don’t call pair until
await WalletConnectClient.inithas resolved. The error doesn’t happen on the first app load, only on subsequent app loads. Every time I re-open the app the amount of errors grows.@LeeAlephium it’s standard json rpc id you get with requests. When you respond you need to use id of reuqets you are replying to. Also for further discussion, could you please join our discord https://discord.com/invite/cB54BwPGru so we can keep this issue related to its topic. Feel free to ping me there
@Aztec#0404events:[]was all I needed, awesome 🙂 Yep, I’m aware of the chain format, but thank you for confirming!@matthewcarlreetz @jasonzhouu we cut beta.50 canary release yesterday (jump from 26 to 50 is to signify api changes). We will be integrating it into our examples and documenting changes this week, once done, I’ll ping you guys here to check if your issue still remains on this version. beta.50 changes up quiet a lot of things around pairing / update methods.