RocketChat / RocketChat/Rocket.Chat
Push notifications not delivered to Android/iOS despite gateway reporting success
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Server Info
- Version: 8.3.2
- Deployment: Self-hosted Docker
- OS: Linux
- MongoDB: 8.0
Mobile Clients
- Android: Rocket.Chat app 4.71.2, Pixel 6 (stock Android), notifications permitted
- iOS: Rocket.Chat official app
Push Configuration
- Gateway: https://gateway.rocket.chat
- Push_enable: true
- Push_enable_gateway: true
- Push_production: true
- Push_request_content_from_server: false
- Push_UseLegacy: false
- Plan: Starter (Unlimited push notifications)
Describe the bug
Admin → Push → "Send a test push notification" reports "Your push was sent to 1 device" but no notification is received on Android or iOS. Nothing appears in Android notification history (Settings → Notifications → Notification history), confirming the notification never reached the device at the OS level.
Desktop notifications work correctly.
Steps to reproduce
- Deploy Rocket.Chat 8.3.2 via Docker with
gateway.rocket.chatas push gateway - Log in with the official Rocket.Chat Android app (4.71.2) and iOS app
- Verify push tokens are registered:
db.getCollection("_raix_push_app_tokens").find()— tokens exist withappName: chat.rocket.androidandchat.rocket.ios - Go to Administration → Push → Send a test push notification
- Interface reports success ("sent to 1 device") but no notification arrives
What was verified on the server side
| Check | Result |
|---|---|
| Workspace registered with Rocket.Chat Cloud | ✓ |
| Cloud Workspace ID exists | ✓ |
Push tokens registered in _raix_push_app_tokens |
✓ (Android GCM + iOS APN) |
Notification queue (rocketchat_notification_queue) processes and empties |
✓ |
Gateway reachable from server (wget https://gateway.rocket.chat) |
✓ |
| Unlimited push plan (Starter) | ✓ |
Push_request_content_from_server set to false |
✓ |
| Stale push tokens removed | ✓ |
| Cloud sync ("Sync license update") triggered | ✓ |
| Container restarted | ✓ |
Legacy push mode (Push_UseLegacy: true) tested |
✓ (no change) |
| Cloud push counter | 0 (gateway never processes) |
Conclusion
The Rocket.Chat server correctly sends push requests to gateway.rocket.chat. The gateway returns a success response (server reports "sent to 1 device") but the cloud push counter remains at 0, indicating the gateway accepts the request but does not forward it to FCM (Android) or APNs (iOS).
The issue is inside gateway.rocket.chat — nothing on the self-hosted server side can resolve this.
Similar reports
- https://forums.rocket.chat/t/push-notifications-to-mobile-not-working/22675 (v7.11.0, same symptoms)
- https://github.com/RocketChat/Rocket.Chat/issues/32130 (v6.6.x, gateway "unsupported version" error)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository file or test is identified. Start at the Administration → Push test flow and the gateway.rocket.chat request, then inspect the registered tokens in _raix_push_app_tokens and the rocketchat_notification_queue behavior. Done means the gateway processes the request and a test notification reaches Android or iOS.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, docker, ios, linux, mongodb
- Domain
- backend, cloud, mobile
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100