8000 [bug] Mobile connect options do not handle user rejection · Issue #2383 · rainbow-me/rainbowkit · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[bug] Mobile connect options do not handle user rejection #2383

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
1 task done
r4vn opened this issue May 4, 2025 · 1 comment
Open
1 task done

[bug] Mobile connect options do not handle user rejection #2383

r4vn opened this issue May 4, 2025 · 1 comment

Comments

@r4vn
Copy link
r4vn commented May 4, 2025

Is there an existing issue for this?

  • I have searched the existing issues

RainbowKit Version

2.2.4

wagmi Version

2.15.2

Current Behavior

RainbowKit crashes the integrating app on mobile due to an uncaught UserRejectedRequestError.

Expected Behavior

RainbowKit does not crash the app on mobile.

Steps To Reproduce

Have the example app on a mobile viewport with a wallet that allows rejection of the connect action.

  1. Try to connect to the wallet
  2. Reject the connection in the wallet
  3. See error in the example app
Image

Link to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)

No response

Anything else?

The connect options for desktop handle this just fine.

It seems like catching such errors was missed for the connect options on mobile.

I am happy to submit a pull request to align the mobile behavior with the desktop one.
@linear Linear
Copy link
linear bot commented May 4, 2025

RK-154 [bug] Mobile connect options do not handle user rejection

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@r4vn
0