Delayed push notification delivery

Open
#31,923 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
android, ios, mongodb, nodejs
Domain
backend, mobile

Research direction

Reproduce the delay by sending a message from the on-premise Rocket.Chat server to the official iOS or Android clients, then compare delivery timing with the Desktop App. Start by gathering server and push-proxy logs, which are absent from the report; done means push notifications arrive immediately rather than after about two minutes.

Written by the indexing model from the issue text.

Description

Description:

I got an on-premise installation of Rocket.Chat and experiencing a delayed delivery of push notifications, sent through the official push notification proxy.

Push notifications on the Desktop App (Mac) is delivered immediately.

Steps to reproduce:
  1. Send a message to someone
  2. Wait about 2 Minutes until push notification is delivered
Expected behavior:

Receive push notifications immediately.

Actual behavior:

Push notifications are delivered delayed (approx. 2 Minutes; sometimes even longer).

Server Setup Information:
  • Version of Rocket.Chat Server: 6.6.2
  • Operating System: RedHat EL 9
  • Deployment Method: npm
  • Number of Running Instances: 1
  • NodeJS Version: v14.21.3
  • MongoDB Version: 6.0.11
Client Setup Information
  • Operating System: iOS/Android
  • We're using the official Rocket.Chat-Clients
Additional context

This issue is ongoing for years in our installation. We recently had a pro trial version and this didn't change the behaviour.

Relevant logs:

None

Dominant language
TypeScript
Stars
46.1k
Forks
13.9k
Avg merge
3d 3h
Merged PRs (30d)
130

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from RocketChat/Rocket.Chat

All issues in RocketChat/Rocket.Chat

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.