> ## Documentation Index
> Fetch the complete documentation index at: https://learn.social.plus/llms.txt
> Use this file to discover all available pages before exploring further.

# React Native Push Notifications

> Understand React Native push-notification support in the SDK docs.

The TypeScript SDK does not currently expose a client-side push device registration API. That means a React Native app cannot complete social.plus push registration by calling a TypeScript SDK method from JavaScript.

<Warning>
  Do not build React Native push setup around a TypeScript SDK method such as `registerPushNotification()` or `registerDeviceNotification()`. Those APIs are not exported by `@amityco/ts-sdk`.
</Warning>

## Current Support Boundary

| Layer                                          | Status                            | What to use                                                                                          |
| ---------------------------------------------- | --------------------------------- | ---------------------------------------------------------------------------------------------------- |
| React Native JavaScript with `@amityco/ts-sdk` | No client device registration API | Use the TypeScript SDK for supported chat and social data features, not push device registration.    |
| Android native SDK                             | Supported                         | Use [Android Push Notifications](./android-setup) and call the native Android SDK registration APIs. |
| iOS native SDK                                 | Supported                         | Use [iOS Push Notifications](./ios-setup) and call the native iOS SDK registration APIs.             |
| Flutter SDK                                    | Supported                         | Use [Flutter Push Notification Setup](./flutter-setup) for Flutter apps.                             |

## Integration Options

For a React Native app that needs social.plus push notifications, choose one of these supported paths:

1. Implement push registration in native Android and iOS layers using the native SDKs.
2. Bridge the native registration result into React Native only for app state or UI, not as a TypeScript SDK call.
3. If you use a React Native UI Kit package, follow the UI Kit's push-notification instructions for that package. UI Kit APIs are outside this SDK-first audit.

## Console Configuration Still Applies

Even when registration happens through native code, the app still needs provider credentials in the social.plus Console:

* Android builds need the Firebase service account JSON uploaded under **Settings > Push Notifications**.
* iOS builds need the APNs credential for the app Bundle ID uploaded under **Settings > Push Notifications**.

## Related Setup

<CardGroup cols={3}>
  <Card title="Android Setup" icon="android" href="/social-plus-sdk/core-concepts/realtime-communication/push-notifications/setup/android-setup">
    Configure FCM and register the signed-in device through the Android SDK.
  </Card>

  <Card title="iOS Setup" icon="apple" href="/social-plus-sdk/core-concepts/realtime-communication/push-notifications/setup/ios-setup">
    Configure APNs and register the device token through the iOS SDK.
  </Card>

  <Card title="Device Registration" icon="bell" href="/social-plus-sdk/core-concepts/realtime-communication/push-notifications/register-and-unregister-push-notifications-on-a-device">
    Compare device registration APIs across supported SDK platforms.
  </Card>
</CardGroup>