UWPX / UWPX-Client

A WIP secure XMPP client for UWP (Windows 10) devices.
https://uwpx.org
Mozilla Public License 2.0
115 stars 17 forks source link

Contact appeared in contacts list twice #145

Closed o--- closed 3 years ago

o--- commented 3 years ago

Bevor you create a new issue:

- [X] I searched for similar issues and did not find one
- [X] I'm using the latest version available in the [Windows Store](https://www.microsoft.com/store/apps/9NW16X9JB5WV)

I'm submitting a...:

Current behavior:

I have received an unencrypted message from a contact which I did not have on the left side in the contact list. However the contact appeared not once, but twice. obrázok

Expected behavior:

The contact appears only once.

Minimal reproduction of the problem with instructions:

Environment:

App Version(s): 
v.0.30.0.0 

Windows 10 Version Number: <!-- https://en.wikipedia.org/wiki/Windows_10_version_history -->
- [X] 1809
- [ ] 1809
- [ ] 1803
- [ ] 1709
- [ ] 1703
- [ ] 1607
- [ ] 1511
- [ ] 1507
- [ ] Insider Build (build number: )
- [ ] Misc:

Device form factor:
- [X] Desktop
- [ ] Mobile
- [ ] Xbox
- [ ] Surface Hub

Where did you got the APP from?
- [X] [Windows Store](https://www.microsoft.com/store/apps/9NW16X9JB5WV)
- [ ] Self-build, using a provided release source
- [ ] Self-build, repo cloned at [dd.mm.yyy] <!-- When did you clone the repo! -->
- [ ] Misc, got it from... <!-- Please tell us your source! -->
COM8 commented 3 years ago

Thanks for reporting this. I'm sad to say, but I'm aware of this. I also noticed this behavior, especially when a lot of new chats get added at once like on initial connect with a new account.

This is probably a synchronization issue since the chat list it self is maintained by an other thread, than the one, that runs the UI.

I tried to fix this a bit of time ago, but I was not able to find a reliable way to reproduce this. Looks like I have to have a look at this again.

As always I really appreciate the time you take to repot those issues. This really helps!

COM8 commented 3 years ago

Should be fixed with the DB backend #146 . Feel free to reopen, in case it still occurs.