question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Unauthorized pairing update request

See original GitHub issue

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

image000000

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.

Issue Analytics

  • State:open
  • Created a year ago
  • Reactions:1
  • Comments:15 (6 by maintainers)

github_iconTop GitHub Comments

2reactions
matthewcarlreetzcommented, May 4, 2022

@IljaDaderko I don’t call pair until await WalletConnectClient.init has 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.

1reaction
0xAsimetriqcommented, Jun 14, 2022

@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#0404

Read more comments on GitHub >

github_iconTop Results From Across the Web

401 Error: 5 Ways to Troubleshoot and Fix It - Hostinger
The 401 Unauthorized error is triggered by unauthenticated requests made to a WordPress web server. Learn how to identify and fix the issue....
Read more >
If an app would like to use Bluetooth on your device
With iOS 13, iPadOS 13, watchOS 6, and tvOS 13, an app must ask permission to use Bluetooth functions except to play audio...
Read more >
How do I stop random Bluetooth pairing requests?
There are several steps you can take to stop random Bluetooth pairing requests. First, disable Bluetooth when you're not using it. This will...
Read more >
BLE - SWIFT App doesn't display pairing request for writing ...
Have you cleared the pairing you established with LightBlue before running your app? What output do you get from your app? Is it...
Read more >
How To Prevent Unauthorized Access To Bluetooth Speakers?
How to do this: Many Bluetooth speakers do not have a menu that you can navigate to remove unauthorized pairings. So, the only...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found