Always a new notification for a new message chat received

Question

Always a new notification for a new message chat received

wizard86pz opened this issue 3 years ago · 18 comments

Every time I access to web app (last version on Google Chrome 90.0.4430.93 and Safari 14.1 (16611.1.21.161.6)), I always see the new message notification on the left column side.

The chat is synced in the web app and no problem using it. But this keeps occurring even if I simply read the chat from the web, the notification icon correctly disappear and i log out: at the next log in, I'll continue to see that notification for the same chat.

Answer 1 · 2021-05-04T12:21:02.000Z

Hi there,
Thanks for helping us making the MEGA's webclient better, by reporting this :)

Few questions to help us replicate this:

What type are the messages shown as unread? (normal text, call related, attachment, etc)
Are they in the same chat room?
Are there any errors in the console after you open the chats and mark the messages as read again? If yes, can you send those to https://mega.nz/support with a reference to this issue please

Thanks!
Lyubomir

Answer 2 · 2021-05-04T13:58:22.000Z

I see the amount of unread messages always only in a single chat. I have a total of 3 chats, and it happens ONLY in a single chat. The chat does not receive new messages, so I cannot tell you exactly which type of messages are wrongly generating the notification icon on the chat icon shown in the report.
yes, the unread messages are only from a single chat.
I see some error in che Chrome console switching from a chat, to another. I collected the logs once I open the chat to clear the unread amount of messages and switch to another one. Gonna be sent to by the link you gave me, mentioning #79

Thanks for help.

Answer 3 · 2021-05-04T14:03:24.000Z

@lpetrov, I've just sent the report, via https://mega.nz/support

Answer 4 · 2021-05-04T21:22:00.000Z

Log received.
But not it didn't contained much ideas for me to figure out the issue.

Can you do the following:

Log out
Write in the console:

localStorage.d = 1; localStorage.chatdLogger = 1;

Refresh the page
Log in
Go to that chat that says there are unread messages and open it (that would clear the unread counter)
Right click in the console -> Save as, save the file and email it support@mega.nz (since the file may be too big to paste in the form I provided earlier)

Thanks! :)

Answer 5 · 2021-05-04T21:33:52.000Z

@lpetrov, email just sent.

Answer 6 · 2021-05-04T22:00:05.000Z

Sorry, but can you redo the same steps with all from the screenshot checked.
E.g. In the console window, click "All levels" dropdown and mark all except "Default" - Verbose, Info, Warnings and Errors
And resend the new log as a reply to the support email.

A potential fixes are:

Try "Menu -> Reload your account"
I saw you are using the extension...disabling the extension or removing it and reinstalling it may help

But those won't guarantee it won't happen again. I will log it as a bug and try to dig more, but still, a log would speed things up a bit :)

Thanks!

Answer 7 · 2021-05-05T07:43:03.000Z

Hi, I've tried the suggested potential fixes but not any change: - reloading the account, the unread amount is still there, all the times - I've used an anonymous Chrome window with no MEGA extension running. I've tried from Firefox too, with MEGA extension, from a different build of MEGA web app: 3.117.14: but still same issue. I've enabled all the levels of the console log, except the "Default". You can find the log attached. Il giorno mer 5 mag 2021 alle ore 00:00 Lyubomir Petrov < ***@***.***> ha scritto:

…

[image: Screen Shot 2021-05-05 at 12 49 19 AM] <https://user-images.githubusercontent.com/139877/117074858-9981dd80-ad3c-11eb-81f4-405bfacdb0de.png> Sorry, but can you redo the same steps with all from the screenshot checked. E.g. In the console window, click "All levels" dropdown and mark all except "Default" - Verbose, Info, Warnings and Errors And resend the new log as a reply to the support email. A potential fixes are: - Try "Menu -> Reload your account" - I saw you are using the extension...disabling the extension or removing it and reinstalling it may help But those won't guarantee it won't happen again. I will log it as a bug and try to dig more, but still, a log would speed things up a bit :) Thanks! — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#79 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIUDJ5I43Z3OW4KJ7BHA7CLTMBU7NANCNFSM44CST2VA> .

Answer 8 · 2021-05-05T08:13:57.000Z

Can you redo the same steps with all from the screenshot checked?
E.g. In the console window, click "All levels" dropdown and mark all except "Default" - Verbose, Info, Warnings and Errors
And resend the new log as a reply to the support email.

Answer 9 · 2021-05-05T08:23:01.000Z

It's what I've done already, Lyubomir. Something missing in the -99014.log file sent in previous email? I've done these steps: 1. Log out 2. Refresh the page. 3. Log in 4. Go to that chat that says there are unread messages and open it (that would clear the unread counter) 5. Right click in the console -> Save as, save the file and email it ***@***.*** (since the file may be too big to paste in the form I provided earlier) I've not re-typed "localStorage.d = 1; localStorage.chatdLogger = 1" since for what I see, it was already active, or should I have re-typed the command in the console?

Answer 10 · 2021-05-06T14:32:16.000Z

Yeah, the log didn't included "Verbose" messages, since they were filtered by that feature in the dev tools.
So, basically once those are enabled as in the screenshot I'd provided and steps redone, the log would contain the complete data where the client tries to mark the messages as read :)

Answer 11 · 2021-05-06T14:44:07.000Z

Ok, I've done and sent as attachment in an email.

Answer 12 · 2021-05-10T19:42:15.000Z

Sorry for the delay, it had been a busy days (even on the weekend).
I got the log and I'm discussing it internally with some other team members, since from the log, it seems ok at first, but we would check few more stuff to try to figure it out :)

Answer 13 · 2021-05-10T20:17:30.000Z

No problem, I understand. My intent here is to report and give you all the details that might help the team. I'm not focused to require an immediate fix.

As extra info, without any test on my side to troubleshoot the issue, yesterday was completely fixed. Once I asked to my chat partner to send me a message there...the issue reappeared and is currently still occurring.

Answer 14 · 2021-05-22T08:02:45.000Z

Hello there.
We found the core issue and it should be fixed.
Let us know if it works for you :)

Thanks!
Lyubomir

Answer 15 · 2021-05-22T08:08:38.000Z

Great, thanks. I'm waiting for the MEGA app CHrome extension update, to have the 4.0.6 web app to test.

Answer 16 · 2021-05-22T08:20:30.000Z

The fix was server side related, so it should work no matter the client version :)

Answer 17 · 2021-05-22T08:24:43.000Z

Even better, I'll check in coming hours/days. Thanks.

Answer 18 · 2021-05-22T11:57:23.000Z

It seems solved, at least with the chat that I've always used to reproduce the issue, thank server side team.