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, including updating your app key for push notifications.

Language: JavaScript, with TypeScript definitions

Availability: Pro, Premium, and Ultimate

Switch the SDK to the release build

In development, ConnectConfig.json uses "useRelease": false, which pulls in the AcousticConnectDebug iOS pod and enables verbose logging on iOS (Xcode console) when your build is a Debug configuration. Before releasing, switch to the release build — this replaces AcousticConnectDebug with the AcousticConnect release pod and suppresses verbose logging outright, regardless of Xcode build configuration.

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

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

2. Rebuild.

npx cordova prepare ios
npx cordova build ios

This only affects iOS. Android always uses the same release SDK artifact regardless of useRelease, so no Android-side change or rebuild is needed for this step.

Update push notification settings

Android setup

Use a dedicated production Firebase project rather than your development one — this keeps test data separate from live data and avoids sending test pushes to production users.

1. Create a production Firebase project in the Firebase console and download its google-services.json.
2. Replace google-services.json at your Cordova project root with this file, then rebuild.
3. Generate a service account key for the production project (Project settings > Service accounts > Generate new private key).
4. Share this file with your Connect administrator — see Production integration in Connect below.

iOS setup

When you switch your signing profile from Development to Distribution as a standard part of your iOS release, the plugin picks it up automatically: it sets the aps-environment entitlement to production for a Release-configuration entitlements file, development otherwise. You don't need to edit any .entitlements file by hand.

Production integration in Connect

Ask your Connect administrator to create a dedicated production Mobile app integration and share the app key and collector URL with you. When you get the credentials, update AppKey and PostMessageUrl in ConnectConfig.json and rebuild.

What the Connect administrator does

This is how the Connect administrator adds the new mobile app to Acoustic Connect.

1. General settings — under Configurations, select both Analytics and Marketing. Assign a descriptive name to the app to differentiate it from the development version (for example, "My App — Prod").

2. External settings — Copy the app key and collector URL from here. The collector URL can differ from the one in your project if your company has separate production and testing subscriptions.

3. iOS Mobile Push Notifications — All values are the same as for your development integration, except for Environment which must be Production for a Distribution-signed build. A mismatch breaks push delivery.

4. Android Firebase Mobile Push Notifications — Requires the production Firebase service account key from Android setup above.

5. Huawei Mobile Services Push Notifications — leave this off. Huawei push isn't supported for hybrid apps.
6. Confirmation — save the integration.

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 and push signals appear in the contact's activity feed in Connect.