|
Artur Hefczyc opened 4 years ago
|
|
Actually, @wojtek was able to find crash report from the time when BeagleIM was in the background (unused) https://projects.tigase.net/issue/issue #324 so I'll look into that. As for wrong "unread messages" count, I suppose this is caused by not marking "closed" chats (ie. with spammers) as "read" - that results in counter presenting wrong (unexpected) value. |
|
|
The issue should be fixed in the next build |
| Type |
Bug
|
| Priority |
Normal
|
| Assignee | |
| Version |
5.0
|
| Spent time |
45m
|
Issue Votes (0)
Watchers (0)
None of the opened chats show any unread message count. And I just went through all of them to double check anyway. Still the app red badge in the system Dock, shows 11 counter, suggesting there are 11 unread messages. This problem started with BeagleIM 5 Beta.
A side not, as maybe this is somehow related. I leave the client open overnight as I never turn off my development computer. Every morning the client is not running/crashed overnight. I do not really have any more details on this except that this happens. But I guess maybe this unread counter has something to do with the crashes.