Skip to content
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

session_request doesn't get triggered #14

Open
pedrouid opened this issue Jul 16, 2019 · 6 comments
Open

session_request doesn't get triggered #14

pedrouid opened this issue Jul 16, 2019 · 6 comments
Assignees

Comments

@pedrouid
Copy link
Contributor

When using either Trust Wallet or WallETH on Android to connect to the Example Dapp (example.walletconnect.org). After scanning the QR Code, the wallet continues loading indefinitely.

On the Bridge server, the logs show that the Wallet receives the wc_sessionRequest payload and it also subscribes to it's own clientId. However no peerMeta is displayed for session_request event.

My guess is that either the payload fails to decrypt or the session_request event doesn't get triggered. Most likely the latter

@ligi
Copy link
Collaborator

ligi commented Jul 16, 2019

try opening the example wallet in a incognito window and see if it works
I guess the key is already set for this session - but WallETH does not know it for some reason (other wallet has it, ..)
That said - this case needs to be handled better
quick workaround can also be that the example refreshes the session more

@pedrouid
Copy link
Contributor Author

I had already cleared cache on both cases but I just tried it again and the issue persists on both Trust Wallet and WallETH.

For reference, I'm using Trust Wallet v1.7.010 and WallETh v0.45.9

@rmeissner
Copy link
Collaborator

So recently I had multiple similar issues when testing with the Safe app:
(very recent - yesterday) the ping message kills the websocket connection because the client errors
(last weeks - not always) I get an invalid EOF, this needs to be debugged, but it also closes the websocket to be closed.

#13 should make it more stable and allow the mobile app to react to error better

@rmeissner
Copy link
Collaborator

rmeissner commented Jul 16, 2019

Currently the error is the new silent field ... the app expects a map of string to string, but silent is a boolean.

Edit: will create a PR to make this more flexible.

@ghost
Copy link

ghost commented Nov 14, 2021

Hello,
I am stuck on the same issue for the last few days. No permission popup in release mode of flutter.

@zzyakenzz
Copy link

Hello, I am stuck on the same issue for the last few days. No permission popup in release mode of flutter.

Hi @abhi94548 , Do you have the answer for this?? I had the same issue on flutter

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants