Closed D4koon closed 2 years ago
I also noticed some false positives when I quickly tested the new version last night.
Yes, just this morning I saw the icon number "climb" ... to 1, then 2 - but no messages arrived. Is it perhaps WhatsApp just refreshing the icon in some way, and this is being counted?
Would any logs help?
Thanks!
BTW, just a thought (and feel free to disagree!), but ... it seems like the code is just incrementing when it detects a new message, and clears when WhatsApp is opened - do I have that right? If that's the case, why worry about trying to count (as it can easily get out of sync), rather just change it icon color (same logic).
Of course, this all does depend on getting to the bottom of the false positives ... :-). Trying to find the recipe there, no luck yet.
TW, just a thought (and feel free to disagree!), but ... it seems like the code is just incrementing when it detects a new message, and clears when WhatsApp is opened - do I have that right? Yes you are right.
why worry about trying to count (as it can easily get out of sync), rather just change it icon color (same logic). Thanks for your suggestion. If it would hide all cases of false postive i would agree that it would be the way to go. But if there is no real message and then a false detection happens it would still be wrong. So it just a little bit better, which is not enough reason for me to change it.
Absolutely agreed - no issues here at all. As you say, first step is to solve the false detection. Yell if any logs (or something else) would help.
Thanks!
TW, just a thought (and feel free to disagree!), but ... it seems like the code is just incrementing when it detects a new message, and clears when WhatsApp is opened - do I have that right? Yes you are right.
why worry about trying to count (as it can easily get out of sync), rather just change it icon color (same logic). Thanks for your suggestion. If it would hide all cases of false postive i would agree that it would be the way to go. But if there is no real message and then a false detection happens it would still be wrong. So it just a little bit better, which is not enough reason for me to change it.
suggestion that when new message arrive the icon just blinks no message count needed
I think the key first step is understand the false positives. Then the indication mechanism can be whatever (@D4koon) decides - IMHO that's his call.
Thanks!
Seems like the code is counting messages from muted conversations too
I noticed I often have a "1" but in fact no messages are unread.
Yes is happening constantly for me too, not yet grasped where is coming from.
Looks like it's escalating. Maybe something has changed in the way WhatsApp works, but I'm now getting a false positive every 10-15 minutes, so my counter keeps going up, even when I'm not receiving messages.
I have the same problem. When I minimize to tray, I will get a false positive in 5-10 minutes, and then often second and third. I have no muted conversations, nothing. Please, help!
I suspect this is related to the whatsapp Stories.
I suspect this is related to the whatsapp Stories.
Yes and not, when I change my inet status through VPN, show me a show a new notification to.
Just a thought, but - would it be possible to get the taskbar icon from Whatsapp (directly), copy that over to WhatsappTray?
I've been having this problem since a week a week or so. A minute or two after closing Whatsapp to the tray, I'll get a nice ol' 1 on the tray icon. Since it was so consistent (hurray for reproduction!) I opened and closed the tray a few times and copied the log for that period.
The offending lines are identical each time, with the last two characters 113c1092bf479aa6.--10
appearing to increment:
WhatsAppApi::IndexedDbChanged() - Found recv: 'o"lineI–6"log"5-o_# 2019-11-16 11:06:07.535: recv: s1 [Conn, ...]" timestampNÍŒaÕ:çvB{'
WhatsAppApi::IndexedDbChanged() - Found recv: 'o"lineIš6"log"<-o_# 2019-11-16 11:06:07.536: recv: 113c1092bf479aa6.--10" timestampNš‘aÕ:çvB{'
WhatsAppApi::IndexedDbChanged() - Found match for receivedMessage.
WhatsAppApi::IndexedDbChanged() - Found recv: 'o"lineIö7"log"5-o_# 2019-11-16 11:09:07.073: recv: s1 [Conn, ...]" timestampN'
WhatsAppApi::IndexedDbChanged() - Found recv: 'o"lineIú7"log"<-o_# 2019-11-16 11:09:07.074: recv: 113c1092bf479aa6.--11" timestampNš©Ö'
WhatsAppApi::IndexedDbChanged() - Found match for receivedMessage.
WhatsAppApi::IndexedDbChanged() - Found recv: 'o"lineIÎ9"log"5-o_# 2019-11-16 11:10:33.002: recv: s1 [Conn, ...]" timestampNf–Õ;çvB{'
WhatsAppApi::IndexedDbChanged() - Found recv: 'o"lineIÒ9"log"<-o_# 2019-11-16 11:10:33.002: recv: 113c1092bf479aa6.--12" timestampNf–Õ;çvB{'
WhatsAppApi::IndexedDbChanged() - Found match for receivedMessage.
If I can provide more information, do let me know. I hope this helps!
Please try this beta-version https://github.com/D4koon/WhatsappTray/suites/4853728201/artifacts/137914918
Currently only tested on Windows 10. There might be problems with other Windows-versions.
It should look something like this:
Please give feedback with used Windows-version (I'm especially interested in other Windows versions than 10) Thank you
I installed the linked version, and while Whatsapp minimized to tray as expected, the tray icon did not show any indication for new messages at all.
I installed the linked version, and while Whatsapp minimized to tray as expected, the tray icon did not show any indication for new messages at all.
Thank you for your feedback. I noticed i still had a fixed path in this build and fixed it now.
Please try this version: https://github.com/D4koon/WhatsappTray/suites/4864576678/artifacts/138575078
That did it for me, thanks!
It is not 100% correct. Im not sure if it is possible to differentiated between messages and whatever causes the false postives with the current method of detection.