[Push Notifications] Again problems sending notifications that have already been read.

Description:

@sampaiodiego and @diegolmello In previous reports, I do not mention them because I can not find them now hahahaha, we discussed the notifications that are sent to mobile phones and that were already seen from a browser.
Apparently it had been resolved and the behavior held up pretty well from my perception. Now we see the same problems again.

Steps to reproduce:

I detail the problem:
I am working on the PC receiving and sending messages from the browser and the mobile is disconnected from the network. When I reconnect the mobile I get all the push notifications of messages that I had already read.

Expected behavior:

Actual behavior:

Server Setup Information:

• Version of Rocket.Chat Server: 3.12.0
• Operating System: Ubuntu
• Deployment Method: tar
• Number of Running Instances: 1
• DB Replicaset Oplog: wiredTiger (oplog Habilitado)
• NodeJS Version: v12.18.4
• MongoDB Version: 4.0.22

Client Setup Information

• Desktop App or Browser Version:
• Operating System:

Additional context

Relevant logs:

No source files, tests, or entry points are named. Reproduce with the browser active, the mobile client offline, and then reconnect it; the fix is complete when messages already read in the browser no longer generate push notifications on reconnect.