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.

Sign up for GitHub

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

Jump to bottom

Refreshing a connection that is already connected leads to a bad state #1598

Open
Zambrella opened this issue Dec 6, 2024 · 1 comment
Open

Refreshing a connection that is already connected leads to a bad state #1598

Zambrella opened this issue Dec 6, 2024 · 1 comment
Assignees
@XavierChanth @CurtlyCritchlow
Labels
bug Something isn't working

Comments

@Zambrella
Copy link

Describe the bug

When clicking to "Refresh" a connected profile it changes to Disconnected and when trying to connect again throws an error: SocketException: Failed to create server socket (OS Error: The shared flag to bind() needs to be true if binding multiple times on the same (address, port) combination.)

Steps to reproduce

  1. Connect to a profile
  2. Click on the menu ... for the profile
  3. Select Refresh
  4. Reconnect

Expected behavior

I would expect that refreshing an already connected profile would maintain the connection

Screenshots

No response

Smartphones

No response

Were you using an atApplication when the bug was found?

NoPorts

Additional context

Does the refresh do anything? Should it be removed?
@Zambrella Zambrella added the bug Something isn't working label Dec 6, 2024
@XavierChanth
Copy link
Member

We may consider removing the button

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@XavierChanth XavierChanth

@CurtlyCritchlow CurtlyCritchlow

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@XavierChanth @CurtlyCritchlow @Zambrella