Push notification delayed after upgrade to 2.1.1

Community Support
1

Description

We are currently running a RC server for our 400 delegates in Sharm El-Sheik on the World Radio Conference. The server is a Ubuntu 18 LTS server, and Rocket chat is installed with the SNAP subsystem. Until friday last week we were running version 1.3.5 of rocket chat, friday night the SNAP updated the RC server to version 2.1.1

Unfortunately our experience is that push notifications to mobile devices now are delayed anywhere from a few seconds up to 15 minutes.

I have reset the connection to the cloud, and activated the “Sync” function, all seems to work, and if i test the push just says “send to two devices”.

I have enabled logging of push messages, but i can not figure out what happens, it seems like notifications are going out but at slow pace.

Also i have tried to writes to sales, if it were some kind of ceiling i have hit, that i could purchase more, but i thiink sales department is closed - they dont answer.

Any ideas anyone - where to go from here ?

Server Setup Information

  • Version of Rocket.Chat Server: 2.1.1
  • Operating System: Ubuntu 18
  • Deployment Method: Snap
  • Number of Running Instances: 1
  • DB Replicaset Oplog: Enabled
  • NodeJS Version: v8.15.1
  • MongoDB Version: 3.6.14
  • Proxy: nginx
  • Firewalls involved: Cisco ASA

Any additional Information

2

We have the same situation. If an Android phone is not being used you go offline after a couple of minutes. We tried disabling battery optimizations and the like, with no luck. The push notifications will arrive around 5 to 10 minutes later when this happens. I wonder if it is related to the priority of the message?

https://firebase.google.com/docs/cloud-messaging/concept-options#setting-the-priority-of-a-message

3

https://github.com/RocketChat/Rocket.Chat/pull/15803