Push notifications not delivered on HONOR Magic 8 Pro (MagicOS 10+) – token registration OK, but no background notifications

Community Support Mobile Apps
1

Hello Team,

I’m running a self-hosted Rocket.Chat server (v7.13.x, Snap package) and I’m experiencing a push notification issue that affects only one specific device.

Affected device

  • Phone: HONOR Magic 8 Pro

  • OS: MagicOS 10+ (Android)

  • Rocket.Chat mobile app: installed from Google Play Store

  • Google Play Protect: device is certified

What works

  • Push notifications work normally on other Android phones and iPhones for the same workspace/server.

  • Push is enabled on the server (Gateway enabled).

  • I verified that push token registration works correctly for this HONOR device (tokens are present on the server and test pushes report successful sending to registered devices).

  • The app works normally in the foreground.

Problem

  • When the app goes to background (even by pressing Home), the user status quickly becomes offline.

  • No push notifications are received while the app is in background or when the screen is locked.

  • This happens even after reinstalling the app and testing with a brand-new Rocket.Chat user account on the same HONOR device.

Troubleshooting already done

  • MagicOS background settings: manual App Launch enabled (auto-launch / secondary launch / run in background), battery set to “Unrestricted” for Rocket.Chat, background data enabled, battery saver disabled.

  • System notifications: Rocket.Chat notifications enabled and notification channels enabled.

  • Reinstalled Rocket.Chat, cleared app data/cache.

  • Verified other apps receive push notifications normally on this device.

  • Tested on both Wi-Fi and LTE/5G.

  • Server-side push configuration verified and working for other devices.

Request
Could you please advise:

  1. Any known Rocket.Chat Android push/background delivery issues on HONOR / MagicOS 10+ devices?

  2. Recommended on-device debugging steps/logs (e.g., Android logcat filters) to confirm whether FCM messages are received and whether the app posts notifications in background.

  3. Any Rocket.Chat mobile versions/builds or configuration changes recommended for this scenario.

I can provide, if helpful:

  • Server logs around push delivery attempts

  • Reverse proxy logs for /api/v1/push.token and related endpoints

  • Android logcat excerpts filtered for FirebaseMessaging/FCM

Thank you for your help.

Best regards,
Rafał

2

Please note you got banned for typing to fast. Slow down your copy & paste translation.

This is a highly hacked non standard Android (waaaay too much AI junk for me!)

Not seen anyone else use it.

At a guess this is some OS “optimisation” that is sleeping the app somehow. Suprised your AI can’t tell you how to fix it…. :wink:

“All that glisters is not gold”

Suggest you ask in the react native channel on open.rocket.chat

The react devs are pretty amenable.