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

Disconnecting a desktop client still shows conversation list #437

Closed
skulumani opened this issue Dec 2, 2015 · 3 comments · May be fixed by sudoWright/Signal-Desktop#1
Closed

Disconnecting a desktop client still shows conversation list #437

skulumani opened this issue Dec 2, 2015 · 3 comments · May be fixed by sudoWright/Signal-Desktop#1

Comments

@skulumani
Copy link

When disconnecting the desktop client (from the Android phone) the user is presented with a weird situation.

The old conversations are still displayed but there's a disconnected symbol in the top right.

At the same time the registration windows and steps appear as well.

I'm not sure if there's a difference between being disconnected (internet issues) vs. being de-registered from the client phone. It might be more clear to give some detail (such as you've been unlinked from the Android Phone?) and totally remove all past conversations?

Steps to reproduce

  1. Link Android to Signal Desktop
  2. Send some messages (might not be needed)
  3. Disconnect the desktop from the phone
  4. Open up Signal on Desktop

signal

Great work on the app! It's working great and looks very nice. Keep up all the amazing work!

@McLoo
Copy link
Contributor

McLoo commented Dec 2, 2015

also (still) some parts of #323

@skulumani skulumani changed the title Disconnecting a desktop instance leads to Disconnecting a desktop client still shows conversation list Dec 2, 2015
@McLoo
Copy link
Contributor

McLoo commented Dec 2, 2015

If you have this unlinked situation, then the barcode window pops up every somewhat time (1 min?) Even if only Chrome is opened and the Signal window not (noticed on dev/github version)

@liliakai
Copy link
Contributor

Pretty sure this is all covered by #323.

@McLoo's last comment has been resolved for some time now.

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

Successfully merging a pull request may close this issue.

3 participants