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

🐛 "Peer to Peer" page on website #22

Open
albertodamico opened this issue Jun 3, 2024 · 1 comment
Open

🐛 "Peer to Peer" page on website #22

albertodamico opened this issue Jun 3, 2024 · 1 comment

Comments

@albertodamico
Copy link

Describe the bug
Inability to proceed after reading the QRCode https://liquid-auth.onrender.com/ (QR Connect) and creating the credentials on the Android app.
The website remains stuck at STEP 1/2 and there is no way to proceed (the "Peer To Peer" part as described on https://github.com/algorandfoundation/liquid-auth?tab=readme-ov-file).

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'https://liquid-auth.onrender.com/' and click on "CONNECT" button on the website
  2. Open Android APP and scan the QRCode on 'https://liquid-auth.onrender.com/' : credentials are created on App.
  3. Website (https://liquid-auth.onrender.com/) is stuck on QRCode

Expected behavior
Expected to see "Peer to Peer" page on website, as showed in readme: https://github.com/algorandfoundation/liquid-auth?tab=readme-ov-file

Desktop (please complete the following information):

  • OS: Windows 10
  • Browser: Chrome
  • Version: 125.0.6422.141 (64 Bit)

Smartphone (please complete the following information):

  • Device: Pixel 7
  • OS: Android 14
@ehanoc
Copy link
Contributor

ehanoc commented Jun 3, 2024

@albertodamico Thanks for trying liquid auth.

Did you try the latest tagged release? v1.0.0beta3? Can be found here or did you build yourself manually?

Also are you using VPN's, firewalls or are you in any permissive networks? Liquid attempts to perform P2P handshake and to work through webRTC if it can negotiate a direct connection. When that's not possible, it uses a TURN server to forward messages and given the sample deployed app, sometimes there's delays. Can you try again if that's the case?

Thanks!

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

2 participants