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

Double connected bug #1147

Open
JeremyMahieu opened this issue Jul 20, 2020 · 2 comments
Open

Double connected bug #1147

JeremyMahieu opened this issue Jul 20, 2020 · 2 comments

Comments

@JeremyMahieu
Copy link
Contributor

Had this bug a lot where somehow there were two websocket connections open to the same glowing bear instance. Never found a way to reproduce it until now.

  1. Be connected
  2. Get disconnected by for example closing your internet connection
  3. Red "reconnecting" alert appears
  4. Press the "power" icon to bring back to the connection screen, the blue button is now "Connect" instead of "Connecting"
  5. Connect using the button
  6. Manually press the "click to reconnect now"

Now the app should be connected twice every bufferline you send or receive appears twice.

I've had this happen several times on accident, usually when the app was open in the background, and I lost internet connection and then I open the app again, it starts at the start screen, but it's already connecting, then upon hitting the connect button I get two connections.

Solutions probably are: Have a global socket object to no two can exist at the same time. Or interlock the automatic reconnect wiht the manual pressing of the connect button.

@lorenzhs
Copy link
Member

Holy crap, thanks! The old issue referencing this is #610 (and #740, #741, #770), btw. I hope to look into this further soon(-ish) but unfortunately I can't offer any promises atm :/

@Strykar
Copy link

Strykar commented Aug 10, 2020

Confirming the same issue for me today.

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

3 participants