We regularly encounter situations where after implementing Bitrix24, mobile push notifications do not work. Clients receive complaints from employees: chat messages missing, tasks overlooked, lead notifications arriving late. Most often, the problem lies in incorrect Firebase Cloud Messaging (FCM) keys for Android or Apple Push Notification Service (APNs) certificates for iOS. We handle this setup end-to-end and resolve failures within 1–2 days. Our service costs $150–$350 depending on complexity, saving businesses up to 5% of revenue by preventing missed leads.
How push notification delivery works
Bitrix24 uses the mobile module and the push.bitrix24.com service as an intermediate push broker. Your Bitrix24 server sends an event to push.bitrix24.com, which then forms a request to FCM or APNs, and finally the notification reaches the device. This is important: if your Bitrix24 is installed on-premise and firewalled, the broker must be able to reach your server via API.
For on-premise Bitrix24, the chain looks like this:
- Event on the portal (new message, task, lead) → trigger in the
mobilemodule - Request to
https://push.bitrix24.com/pub/with device token and payload - Broker → FCM/APNs → user's device
Device tokens are stored in the b_mobile_device table. When the app is reinstalled, the token changes, and the old one is marked invalid after the first failed response from FCM/APNs.
Why push notifications don't arrive: typical causes
-
Firebase key mismatch. Bitrix24 up to version 22.x uses Legacy API — a key like
AAAAxxxxxxx:APA91b.... Starting from newer versions of themobilemodule, FCM HTTP v1 API via OAuth2 token from a service account is supported. If you upgraded but kept the old key, push stops working. We recommend configuring FCM v1 immediately — it's more reliable and won't require key updates in the future. -
Apple APNs certificates. Apple uses two authentication mechanisms:
.p12certificates and.p8keys (token authentication). Certificates expire after one year — a typical reason for sudden push failure on iOS..p8keys have no expiration, so we recommend them. To generate a.p8key: Apple Developer Console → Certificates, Identifiers & Profiles → Keys → create a key with the Apple Push Notifications service (APNs) flag. You can download it only once.
Comparison of Legacy and FCM v1 for Bitrix24
| Aspect | FCM Legacy API | FCM HTTP v1 |
|---|---|---|
| Support in Bitrix24 | Up to version 22.x | Starting from mobile module 22.x |
| Key type | Static Server Key | OAuth2 token from a service account |
| Key duration | Unlimited | Token auto-refreshes |
| Security | Low (key can be easily compromised) | High (limited permissions) |
| Recommendation | Only for old versions | For all new projects |
FCM HTTP v1 is better than Legacy API in terms of security and does not require manual key renewal. We migrate clients to v1 as part of push setup.
How to diagnose push notification failures
If push isn't working, first check the b_push_queue table. If unprocessed records accumulate, the agent \Bitrix\Push\QueueAgent is not running. Set up cron for agents. Another common cause is an incorrectly set external portal address in on-premise settings. Ensure that push.bitrix24.com can reach your server.
Technical details for setting up FCM v1
- Create a project in Firebase Console.
- Add a service account in project settings (IAM & Admin → Service Accounts).
- Download the JSON key.
- In Bitrix24: Administration → Mobile App → Push Notifications → select FCM HTTP v1, upload the JSON.
- Test with a test notification.
What is included in push notification setup?
- Full FCM setup (Legacy or v1) for Android
- Full APNs setup (certificate or
.p8key) for iOS - Checking and configuring the push broker for on-premise
- Resolving typical issues (duplicates, missing push, delays)
- Administrator instructions for certificate renewal
- 1 month of support after delivery
- Documentation of all settings for future reference
Estimated timeline: from 1 day to 3 days depending on configuration complexity. Cost is calculated individually after an audit.
Diagnosing typical failures
During diagnostics, we often encounter the following situations. If push notifications don't arrive only on iOS, first check the certificate expiry date. Open Keychain Access, find the Apple Push Services: com.your.bundleid certificate — look at the expiration date. If expired — regenerate via Apple Developer Portal and re-upload to Bitrix24.
If push notifications don't arrive on both Android and iOS after a server migration, the portal may have changed its domain or IP, but push.bitrix24.com doesn't know the new address yet. In on-premise registration settings, ensure the external portal address is correct and externally accessible.
Duplicate notifications occur when a user logs in from multiple devices — several active tokens in b_mobile_device. This is normal, but if duplicates multiply without stopping, the app may be registering a new token on each launch instead of updating the existing one.
Check the send queue: if rows in b_push_queue are not decreasing, the agent \Bitrix\Push\QueueAgent is not running. Check cron.
Note: push notifications reach users faster with FCM v1 compared to Legacy, especially under high load on chats and tasks.
For more details, see the official documentation: Push Notifications in Mobile App.
Comparison of APNs authentication methods
| Authentication | Duration | Setup complexity | Recommendation |
|---|---|---|---|
| .p12 certificate | 1 year | Medium | Only if already using |
| .p8 key (token) | Unlimited | Low | Recommended for all projects |
We have configured push notifications on more than 200 Bitrix24 portals over 5 years. We are a certified Bitrix24 Partner with guaranteed quality. Non-functioning notifications can cost a business up to 5% of revenue due to missed leads and delayed communication. Setting up push notifications pays off within a week by accelerating employee response. Timely diagnostics prevents financial losses from missed leads.
Contact us for a free audit of your current push configuration. We will assess your project and offer the optimal solution. Order push notification setup and ensure stable operation. Get a consultation — write to us on Telegram or by email.