-
Notifications
You must be signed in to change notification settings - Fork 63
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.
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
RelayClient, onSubscribe error. #132
Comments
Another code path where Metamask is sending nulls? Related to #118 since that mentions pairing as well? |
@bobwith2bees this happens before the actual connection with Metamask |
I call initSession and get mentioned error `class EthereumWallectConnectTransactionV2 { Future initSession() async { Future initWalletConnect() async { Future connect() async {
} |
Just released 2.0.13 which might resolve this. Please test and let me know! |
There is a problem with v2.0.13. |
Tried to fix dependencies and use 2.0.13, have this error now: |
@rkovrigin Please make a separate issue for this http information. I completely lost it in here, and this issue has nothing to do with an http error. |
I get the same error. |
When trying to connect using example provided:
https://github.com/WalletConnect/WalletConnectFlutterV2#dapp-flow
https://docs.walletconnect.com/2.0/flutter/dapps/dapp-sign-usage
I am getting the following error, and after scanning the connection URI with metamask it does not connect.
flutter: ┌───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────⚠️ RelayClient, onSubscribe error. Topic: d76177fb912ebd9bead4633152c10b7b2af2e927b398014edd22afcb899036d4, Error: Null check operator used on a null value
flutter: │ #0 RelayClient._onSubscribe (package:walletconnect_flutter_v2/apis/core/relay_client/relay_client.dart:418:19)
flutter: │ #1
flutter: ├┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄
flutter: │
flutter: └───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
The text was updated successfully, but these errors were encountered: