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
After upgrading to the latest version of wagmi, we're encountering a 400 bad request error when the WalletConnect Explorer API is called. The issue appears to be that the projectId is not being passed in the request URL, even though it's specified in the codebase.
Expected Behavior
A GET request is made to the WalletConnect Explorer API with success ( 200 code )
Steps To Reproduce
Upgrade to the latest version of wagmi
Implement RainbowKit with a valid projectId
Observe network requests when interacting with wallet connect API.
Link to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
RainbowKit Version
2.1.7
wagmi Version
2.12.17
Current Behavior
After upgrading to the latest version of wagmi, we're encountering a 400 bad request error when the WalletConnect Explorer API is called. The issue appears to be that the
projectId
is not being passed in the request URL, even though it's specified in the codebase.Expected Behavior
A GET request is made to the WalletConnect Explorer API with success ( 200 code )
Steps To Reproduce
projectId
Link to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: