Skip to main content
Blockli delivers push notifications via Firebase Cloud Messaging (FCM v1). FCM handles both Android directly and iOS via APNs relay. Credentials are stored in Studio and injected into builds — you don’t configure Firebase keys in the plugin directly.

​
Setup overview

  1. Create a Firebase project for your app (or use an existing one)
  2. Add your iOS and Android apps to the Firebase project
  3. Upload credentials to Studio (see iOS credentials and Android credentials)
  4. Studio injects the credentials into your builds
The plugin receives a push token from each device when a user logs in. It stores the token against the user’s account and uses it when dispatching notifications.

​
Notification types

The plugin defines these notification events (BMA_Push_Types): Each type can be enabled or disabled by users in the app’s notification preferences screen.

​
Silent / data-only pushes

Blockli uses data + title/body pushes (not silent-only) so that addNotificationReceivedListener fires on both foreground and background. The notification UI is suppressed programmatically when the notification should be handled in-app without showing a banner.
Pure data-only (silent) pushes will not trigger addNotificationReceivedListener in Expo. Always include title and body in notification payloads; suppress the UI via the notification handler instead.

​
Real-time events

In addition to push, the plugin includes a real-time channel (BMA_Realtime) for in-app events while the user has the app open. This uses a polling or WebSocket connection depending on your server configuration. Real-time events power features like:
  • Live activity feed updates
  • Chat message delivery
  • Presence indicators
  • Livestream status changes
See the Real-time section for configuration details.