You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -329,6 +332,10 @@ After successful activation, `deviceId` contains the unique device ID assigned t
329
332
On Android, use `notifee.requestPermission()` instead of React Native's `PermissionsAndroid` because it handles the `POST_NOTIFICATIONS` permission consistently across Android API levels. On iOS, `messaging().requestPermission()` shows the system notification permission dialog; Firebase Messaging calls the native iOS permission APIs internally.
330
333
</Aside>
331
334
335
+
<Asidedata-type='note'>
336
+
In React Native `realtime.push.activate()` is not used because it's a JS SDK and it registers browser for push notifications, which is not what we want in a React Native app. Instead, `realtime.push.admin.deviceRegistrations` API is used to register the device.
337
+
</Aside>
338
+
332
339
## Step 3: Subscribe and test push notifications <aid="step-3"/>
333
340
334
341
The FCM SDK handles background push notifications automatically and displays them as system notifications. For foreground handling, use `@notifee/react-native` to display notifications while the app is open.
0 commit comments