You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the issues tracker for a bug report similar to mine, in vain
Ferdium Version
6.2.0
What Operating System are you using?
macOS
Operating System Version
13.0 (22A380)
What arch are you using?
arm64 (including Apple Silicon)
Last Known Working Ferdium version
No response
Expected Behavior
Show the correct number of unread messages. In my case it should be 0 unread and therefore there should be no red badge icon.
Actual Behavior
Unread badge Icon is showing 607. I'm not sure what this number is referring to.
Steps to reproduce
Add WhatsApp to Ferdium and setup your account. This just starting occurring one day so not sure of any other steps.
Debug link
No response
Screenshots
Interesting I noticed that if you actually filter unread messages (which in my case shows no messages correctly) then the badge actually does update to correctly show no unread.
Avoid duplicates
Ferdium Version
6.2.0
What Operating System are you using?
macOS
Operating System Version
13.0 (22A380)
What arch are you using?
arm64 (including Apple Silicon)
Last Known Working Ferdium version
No response
Expected Behavior
Show the correct number of unread messages. In my case it should be 0 unread and therefore there should be no red badge icon.
Actual Behavior
Unread badge Icon is showing 607. I'm not sure what this number is referring to.
Steps to reproduce
Add WhatsApp to Ferdium and setup your account. This just starting occurring one day so not sure of any other steps.
Debug link
No response
Screenshots
Interesting I noticed that if you actually filter unread messages (which in my case shows no messages correctly) then the badge actually does update to correctly show no unread.
Additional information
https://debug.ferdium.org/d1dadc19-82b6-47d6-8f1e-4ec9db160918
The text was updated successfully, but these errors were encountered: