When you have finished integrating and testing the Connect SDK in development, work through this checklist to move your integration to production. Going to production requires changes to ConnectConfig.json and privacy protection. If your app uses push notifications, you also need to update your app key and, on iOS, switch the APNs environment.

Language: TypeScript and JavaScript

Availability: Pro, Premium, and Ultimate

Switch to the release build

In development, ConnectConfig.json uses "useRelease": false, which pulls in the AcousticConnectDebug iOS pod and enables verbose logging on both iOS (Xcode console) and Android (Logcat). Before releasing, switch to the release build.

1. Open ConnectConfig.json in the root of your project and set useRelease to true.

{
  "Connect": {
    "useRelease": true,
    ...
  }
}

2. Rebuild the native layers.

cd ios && pod install

npm run ios
npm run android

With useRelease: true, the AcousticConnect release pod is used on iOS (replacing AcousticConnectDebug), and verbose logging is suppressed on both platforms.

As a cleanup step, remove the CONNECT_DEBUG, TLF_DEBUG, and EODebug environment variables from your Xcode scheme if you added them for development. They have no effect once useRelease is true, but removing them avoids any ambiguity if a Release-configuration build is ever run outside the Archive flow.

Update your app key (push-enabled apps only)

If your app uses push notifications, you must use a production app key. Development and production app keys are tied to different APNs environments (iOS) and FCM configurations (Android), so the key swap and environment switch must happen together.

Ask your Connect administrator to issue a production app key, then update AppKey in ConnectConfig.json with the production value. Rebuild after saving.

Verify production push delivery

Before submitting to the App Store or Google Play, confirm the production push path end to end:

1. Archive a Distribution-signed build (iOS) or a release APK/AAB (Android) and distribute it via TestFlight or an internal track to a real device.
2. Launch the app on the device and grant notification permission when prompted.
3. Coordinate with your marketing team to send a test push to your device, or do it yourself — see Test your push notification setup.
4. Verify the notification appears, images load, and push signals appear in the contact's activity feed in Connect.

Enable privacy protection

Before releasing your app to production, mask the personally identifiable information (PII) that session replay would otherwise capture from your screens.

For instructions, see Mask PII in session replay (React Native).

Verify the iOS privacy manifest

The Connect iOS SDK pod bundles its own PrivacyInfo.xcprivacy. Xcode automatically includes it in your app's privacy report at build time — no manual entries are required. Before submitting to the App Store, confirm the SDK's entries appear in your app's privacy report. For the full list of declared API types and reasons, see Connect iOS SDK privacy manifest.