Skip to main content
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.
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.

​
Current Support Boundary

​
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.

Android Setup

Configure FCM and register the signed-in device through the Android SDK.

iOS Setup

Configure APNs and register the device token through the iOS SDK.

Device Registration

Compare device registration APIs across supported SDK platforms.