npx expo install \
@react-native-firebase/app \
@react-native-firebase/messaging \
@stream-io/react-native-callingxExpo
If you are on version 1.31.0 or below, you would need to upgrade to 1.32.0 or above to follow the setup. As 1.32.0 release had breaking changes with respect to setting up of push notifications and CallKit integration. We recommend to update to the current latest version. Additionally, the ringing flow requires @stream-io/react-native-webrtc version 137.1.2 or higher.
Add push notifications for ringing calls to your Expo project. Covers both Android and iOS setup.
Users receive push notifications for incoming calls and can accept or reject directly from the notification.
| Android preview | iOS preview |
|---|---|
![]() | ![]() |
Full-screen notifications are displayed when the phone screen is locked or the app is active (foreground state). However, when the app is terminated or in the background and the screen is awake, notifications may appear as heads-up notifications instead of a full-screen alerts.
Add push provider credentials to Stream
Follow these guides to add push providers:
- Android - Firebase Cloud Messaging
- iOS - Apple Push Notification Service (APNs)
Install Dependencies
Package purposes:
@react-native-firebase/appand@react-native-firebase/messagingfor handling incoming Firebase Cloud Messaging notifications on Android.@stream-io/react-native-callingxfor registering calls in iOS CallKit and Android Telecom.
Add Firebase credentials
- Create a Firebase project at Firebase console
- Add your Android app in Project settings > Your apps. Use the same package name as
android.packagein app.json - Download google-services.json to your project root
- Add to app.json:
{
"android": {
"googleServicesFile": "./google-services.json"
}
}- For iOS, add your Apple app in Project settings > Your apps. Use the same bundle ID as
ios.bundleIdentifierin app.json - Download GoogleService-Info.plist to your project root
- Add to app.json:
{
"ios": {
"googleServicesFile": "./GoogleService-Info.plist"
}
}The google-services.json and GoogleService-Info.plist files contain unique and non-secret identifiers of your Firebase project. For more information, see Understand Firebase Projects.
We will not be using firebase for iOS. But it is necessary for the setup for react-native-firebase to have the GoogleService-Info.plist file.
iOS - Notifications entitlement
For Expo SDK 51+, add the notifications entitlement to app.json:
{
"expo": {
"ios": {
"entitlements": {
"aps-environment": "production"
}
}
}
}Add the config plugin properties
In app.json, in the plugins field, add the ringing property to the @stream-io/video-react-native-sdk plugin.
{
"plugins": [
[
"@stream-io/video-react-native-sdk",
{
"ringing": true
}
],
[
"@config-plugins/react-native-webrtc",
{
"cameraPermission": "$(PRODUCT_NAME) requires camera access in order to capture and transmit video",
"microphonePermission": "$(PRODUCT_NAME) requires microphone access in order to capture and transmit audio"
}
],
"@react-native-firebase/app",
"@react-native-firebase/messaging",
[
"expo-build-properties",
{
"ios": {
"useFrameworks": "static",
"forceStaticLinking": [
"RNFBApp",
"RNFBMessaging",
"stream-react-native-webrtc"
]
}
}
]
// your other plugins
]
}- For iOS only:
firebase-ios-sdkrequires static frameworks then you want to configureexpo-build-propertiesby adding"useFrameworks": "static".- Since Expo 54,
forceStaticLinkingis required for certain libraries when"useFrameworks": "static"is used.
The plugin adds a foreground service and the necessary permissions for Android. It shows incoming call notifications and keeps video/audio calls active when the app is in the background.
When uploading the app to the Play Store, declare these permissions in the Play Console and explain their usage, including a link to a video demonstrating the service. This is a one-time requirement. For more information, click here.
The added permissions are:
android.permission.FOREGROUND_SERVICE_PHONE_CALL- To maintain active video and audio calls when app goes to background
If Expo EAS build is not used, please do npx expo prebuild --clean to generate the native directories again after adding the config plugins.
Optional: Disable Firebase integration on iOS
Disable Firebase APNs registration since iOS uses VoIP push. Create firebase.json:
{
"react-native": {
"messaging_ios_auto_register_for_remote_messages": false
}
}Add Firebase message handlers
Add SDK utility functions to Firebase notification listeners:
import messaging from "@react-native-firebase/messaging";
import {
isFirebaseStreamVideoMessage,
firebaseDataHandler,
} from "@stream-io/video-react-native-sdk";
export const setFirebaseListeners = () => {
// Set up the background message handler
messaging().setBackgroundMessageHandler(async (msg) => {
if (isFirebaseStreamVideoMessage(msg)) {
await firebaseDataHandler(msg.data);
} else {
// your other background notifications (if any)
}
});
// Optionally: set up the foreground message handler
messaging().onMessage((msg) => {
if (isFirebaseStreamVideoMessage(msg)) {
firebaseDataHandler(msg.data);
} else {
// your other foreground notifications (if any)
}
});
};Firebase message handlers:
- The
onMessagehandler should not be added if you do not want notifications to show up when the app is in the foreground. When the app is in foreground, you would automatically see the incoming call screen. - The
isFirebaseStreamVideoMessagemethod is used to check if this push message is a video related message. And only this needs to be processed by the SDK. - The
firebaseDataHandlermethod is the callback to be invoked to process the message. This callback reads the message and display push notifications.
If you have disabled the initialization of Firebase on iOS, add the above method only for Android using the Platform-specific extensions for React Native.
For example, say you add the following files in your project:
setFirebaseListeners.android.ts
setFirebaseListeners.tsThe method above must only be added to the file that .android extension. The other file must add the method but do nothing like below:
export const setFirebaseListeners = () => {
// do nothing
};Setup the push notifications configuration for the SDK
The SDK automatically processes the incoming push notifications once the setup above is done if the push notifications configuration has been set using StreamVideoRN.setPushConfig.
Also you can override the default notification texts and adjust ringtone for both iOS CallKit and Android Telecom.
Below is an example of how these methods can be called:
import {
StreamVideoClient,
StreamVideoRN,
User,
} from "@stream-io/video-react-native-sdk";
import AsyncStorage from "@react-native-async-storage/async-storage";
import { STREAM_API_KEY } from "../../constants";
export function setPushConfig() {
StreamVideoRN.setPushConfig({
ios: {
// add your push_provider_name for iOS that you have setup in Stream dashboard
pushProviderName: __DEV__ ? "apn-video-staging" : "apn-video-production",
supportsVideo: true,
callsHistory: true,
displayCallTimeout: 60000,
},
android: {
// add your push_provider_name for Android that you have setup in Stream dashboard
pushProviderName: __DEV__
? "firebase-video-staging"
: "firebase-video-production",
incomingChannel: {
id: "incoming_call_channel",
name: "Call notifications",
vibration: true,
},
notificationTexts: {
accepting: "Connecting...",
rejecting: "Declining...",
},
},
shouldRejectCallWhenBusy: true,
enableOngoingCalls: true,
// add the async callback to create a video client
// for incoming calls in the background on a push notification
createStreamVideoClient: async () => {
const userId = await AsyncStorage.getItem("@userId");
const userName = await AsyncStorage.getItem("@userName");
if (!userId) return undefined;
// an example promise to fetch token from your server
const tokenProvider = async (): Promise<string> =>
yourServerAPI.getTokenForUser(userId).then((auth) => auth.token);
const user: User = { id: userId, name: userName };
return StreamVideoClient.getOrCreateInstance({
apiKey: STREAM_API_KEY, // pass your stream api key
user,
tokenProvider,
options: { rejectCallWhenBusy: true },
});
},
});
}Always use StreamVideoClient.getOrCreateInstance(..) instead of new StreamVideoClient(..). Reusing the client instance preserves call accept/decline states changed while the app was in the background. The getOrCreateInstance method ensures the same user reuses the existing instance.
iOS calling experience options:
supportsVideo- tells CallKit that video calls should be supported. Affects system UI and routing. Default value istrue.callsHistory- enables calls history. When enabled, all registered calls will be displayed in recent calls section in default dial app. Default value isfalse.displayCallTimeout– timeout value in ms which will be used to hide system UI if JS is not loaded during that time. Default value is60000.sound- ringtone resource name that will be used by CallKit. Detailed instructions are provided on CallKit options page.imageName- image resource name that will be used on CallKit dialer UI. Detailed instructions are provided on CallKit options page.
Android calling experience options:
incomingChannel.id- notification channel id for incoming callsincomingChannel.name- notification channel nameincomingChannel.sound- ringtone resource name that will be used for ringing notification. Detailed instructions are provided on Android custom ringtone page.incomingChannel.vibration- enables vibration for notification channelnotificationTexts– allows to override default texts displayed in notifications for accepting/declining intermediate state. By default,Connecting...andDeclining...will be displayed for corresponding state.titleTransformer- allows you to modify displayed notification title. Receives member name andincomingboolean flag as parameters. By default, just returns the member name value.
General calling experience options:
shouldRejectCallWhenBusy– blocks new incoming calls in cases when there is an active ongoing call. Default value isfalse. For setting up call interruption behavior on a client level, please check Reject call when busy. Note: for consistent behavior, this flag should be defined both in the client constructor and insetPushConfigcall.enableOngoingCalls– enables CallKit/Telecom support for outgoing calls. Default value isfalse.
Please note that all described parameters are optional.
Initialize SDK push notification methods
Call the methods we have created outside your application cycle. That is, alongside your AppRegistry.registerComponent() method call at the entry point of your application code. A root file index.js is a good place do this as the app can be opened from a dead state through a push notification, and in that case, we need to use the configuration and notification callbacks as soon as the JS bridge is initialized.
import { setPushConfig } from "./utils/setPushConfig";
import { setFirebaseListeners } from "./utils/setFirebaseListeners";
setPushConfig();
setFirebaseListeners();
// always import expo-router/entry at the end of the file
import "expo-router/entry";The index.js file must be made as the entry point file to your app. This can be done via editing the main property in the package.json file:
{
...
"main": "index.js",
...
}Disabling push notifications
Disable push on user logout or user switch:
import { StreamVideoRN } from "@stream-io/video-react-native-sdk";
await StreamVideoRN.onPushLogout();Android full-screen incoming call view on locked phone
For apps installed on phones running versions Android 13 or lower, the USE_FULL_SCREEN_INTENT permission is enabled by default.
For all apps being installed on Android 14 and above, the Google Play Store revokes the USE_FULL_SCREEN_INTENT for apps that do not have calling or alarm functionalities. Which means, while submitting your app to the play store, if you do declare that 'Making and receiving calls' is a 'core' functionality in your app, this permission is granted by default on Android 14 and above.
If the USE_FULL_SCREEN_INTENT permission is not granted, the notification will show up as an expanded heads up notification on the lock screen.
Incoming and Outgoing call UI in foreground
Show call UIs during ringing calls. See watching for calls for implementation.
Testing Ringing calls
To test properly:
- Use a real physical device (APNs do not work in simulators).
- Ensure your Firebase/APNs credentials are correctly configured in the Stream Dashboard.
- Ensure your iOS provisioning profile includes Push Notifications capability and the
aps-environmententitlement.
For the best experience, run the Android and iOS app without the metro bundler to the respective physical devices using the following command:
To generate native code directories:
npx expo prebuild --cleanFor iOS:
npx expo run:ios --no-bundler --device --configuration ReleaseFor Android:
npx expo run:android --no-bundler --device --variant releaseTroubleshooting
See the Troubleshooting guide for common issues.
- Add push provider credentials to Stream
- Install Dependencies
- Add Firebase credentials
- Add Firebase message handlers
- Setup the push notifications configuration for the SDK
- Initialize SDK push notification methods
- Disabling push notifications
- Android full-screen incoming call view on locked phone
- Incoming and Outgoing call UI in foreground
- Testing Ringing calls
- Troubleshooting

