Community-edition: WhatsApp and Android Messages Unread Counter Not Working

[themagpieswarble]

Steps to reproduce

1. Open Rambox on Windows 10
2. Add WhatsApp service (along with other services if you want to replicate my issue exactly. Make WhatsApp the 3rd service in the line of tabs)
3. Ensure that Notifications are turned on for the service
4. Receive a Whatsapp Notification

Expected behavior

Whatsapp Unread Counter Badge appears on the WhatsApp tab in Rambox alerting user to unread message. (Same behavior when reproducing steps above using Google Messages)

Actual behavior

WhatsApp Unread Counter Badge does not appear on the Whatsapp tab in Rambox. (Same behavior when reproducing steps above using Google Messages)

ENVIRONMENT

Rambox: v0.6.7

OS: Windows 10

Arch: x64

COMMENTS

This does not happen with my two Slack services that I use. Only Whatsapp and Google Messages do not display the unread.

Attached a screenshot of my Services settings on the Rambox home page and also of the WhatsApp Web settings and Google Messages settings in case that affects it (the lighter colored one is Whatsapp the dark mode one is Google Messages.)

[welcome[bot]]

Thanks for opening your first issue here! Be sure to follow the issue template!

[Corchoneitor]

Hi @themagpieswarble

I notice this today, only in Whatsapp. Will be investigating this ASAP.

[themagpieswarble]

Thank you!

On Fri, May 31, 2019, 3:35 PM Juan Manuel Gonzalez Alama <
[email protected]> wrote:

Hi @themagpieswarble https://github.com/themagpieswarble

I notice this today, only in Whatsapp. Will be investigating this ASAP.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ramboxapp/community-edition/issues/2289?email_source=notifications&email_token=AKAXULDCPNASDIRYU7NRU2TPYGRZHA5CNFSM4HR6JJ7KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWWQ2JA#issuecomment-497880356,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKAXULBKMG5VQ7DZC26PFD3PYGRZHANCNFSM4HR6JJ7A
.

[Corchoneitor]

Try building with this fix until this is included in next release.

Or you can put this snippet as Custom Code for WhatsApp:
function checkUnread(){const elements = document.querySelectorAll(\'.P6z4j, .unread\');let count = 0;for (let i = 0; i < elements.length; i++) {if (elements[i].parentNode.parentNode.querySelectorAll(\'*[data-icon="muted"]\').length === 0) {count++;}}updateBadge(count);}function updateBadge(count){if(count && count>=1){rambox.setUnreadCount(count);}else{rambox.clearUnreadCount();}}setInterval(checkUnread, 1e3);(async()=>{try{const a=await window.navigator.serviceWorker.getRegistrations();for(const b of a)b.unregister()}catch(a){}})();

[yafp]

@Corchoneitor
thx - this seems to work.

[themagpieswarble]

Unfortunately the custom code didn't seem to work for me. Put it in, reloaded WhatsApp and still doesn't show unread badges. Restarted Rambox too and that didn't work either.

[Gaafgeel]

Unfortunately it didn't work for me neither.

[Dareiko]

Same for me, I have two account and both didn't work 👎

[themagpieswarble]

@Corchoneitor why was this issue closed? Has it been fixed? Sorry I'm unfamiliar with how GitHub works.

[maxerbox]

Yup, it means that is it fixed and will come in the next release

[themagpieswarble]

Thank you!

On Tue, Jun 4, 2019 at 12:33 PM Simon Sassi [e-mail]
wrote:

Yup, it means that is it fixed and will come in the next release

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ramboxapp/community-edition/issues/2289?email_source=notifications&email_token=AKAXULANARSOA2LS4TRNNQLPY27PDA5CNFSM4HR6JJ7KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODW5UB7Q#issuecomment-498811134,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKAXULGACW52X2JQOJDVRFDPY27PDANCNFSM4HR6JJ7A
.

[themagpieswarble]

Updated to the build from 2 days ago (0.6.9 win32 x64) and WhatsApp and Android Messages counters still aren't working.

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.