greymass / ual-anchor

Identity and session through ESR using EOSIO/universal-authenticator-library
MIT License
23 stars 16 forks source link

Problem with socket.io connection #32

Open Vilchynskyi opened 2 years ago

Vilchynskyi commented 2 years ago

Hello,

I have a problem with socket.io. After successfully signing a transaction via the button Sign manually and then clicking on the Launch Anchor button my socket connection just closes and I can't send any events. After several attempts to send events in my connection it just creates new socket connections. It can be replicated only if I'm clicking on the Sign manually button and then on the Launch Anchor button. Everything is okay when the Anchor Wallet app opens itself. I'm using the Chrome 96.0.4664.110 version and the latest package version. Could you help me please resolve the issue? Thank you!

orange1337 commented 2 years ago

Have the same problem

aaroncox commented 2 years ago

Do either of you have any code samples where you see this happening?

Another question would be do you see it happening in the UAL demo we have running here?

https://greymass.github.io/ual-reactjs-renderer-demo-multipass/?chainId=1064487b3cd1a897ce03ae5b6a865651747e2e152090f99c1d19d44e01aea5a4