[bug] Bybit wallet integration not working
hernan-clich opened this issue · comments
Is there an existing issue for this?
- I have searched the existing issues
RainbowKit Version
2.0.6
wagmi Version
2.8.1
Current Behavior
Bybit wallet appears as one of the installed wallets but when attempting to connect it, and endless loading state appears that says the following:
Opening Bybit Wallet...
Confirm connection in the extension
However, the wallet never prompts user interaction.
Expected Behavior
The wallet should prompt user confirmation to connect to the requesting dapp.
Steps To Reproduce
I was able to reproduce in the live production site, https://www.rainbowkit.com/
.
- Download Bybit Google Chrome extension (currently v2.4.25): https://chromewebstore.google.com/detail/bybit-wallet/pdliaogehgdbhbnmkklieghmmjkpigpa
- Click on Connect wallet
- Bybit will appear in the "Installed" section
- Click on Bybit
- The loading state starts and nothing else happens
Link to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)
Anything else?
I was able to reproduce in the live production site, https://www.rainbowkit.com/
.
![image](https://private-user-images.githubusercontent.com/62221379/331654480-d91bc055-38b4-4cef-941e-c1e5c3066e14.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQ2NjI2NzksIm5iZiI6MTcyNDY2MjM3OSwicGF0aCI6Ii82MjIyMTM3OS8zMzE2NTQ0ODAtZDkxYmMwNTUtMzhiNC00Y2VmLTk0MWUtYzFlNWMzMDY2ZTE0LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MjYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODI2VDA4NTI1OVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTBhNTU3ZmM2YWJmMTc0ZGQ0MTQ2NjU3NzY5OTk3MjY1MTYzNzYzOGMzYWMwYmZhMjhkZmI0NTBiZmFkNDdhMGYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.4EK9rYhtoYfJv6hkTGSBkPdzGeHnZ3yR2YZb_KSoBJs)
This seems to be an issue with Bybit extension not working properly. Those wallets are responsible for these kind of behaviors since we don't have control over what actions they do. In this case it's a bug and i would suggest reporting this to their support team.