Migrate Adapty React Native SDK to v4.1

Adapty React Native SDK 4.1 changes how Adapty Attribution is enabled, renames the external attribution APIs, and changes the fallback file format. It also lets your app take over App Store promoted in-app purchases and brings back the hasViewConfiguration flag on AdaptyFlow.

If you’re still on 3.x, start with Migrate to v4.0 and then follow this guide.

Quick reference

Installation

Update the react-native-adapty package:

npm install react-native-adapty@latest
# or
yarn add react-native-adapty@latest

The runtime requirements are unchanged from 4.0: iOS 15.0 and React Native 0.75. See Install Adapty SDK for the full setup.

4.1 also supports React Native’s SPM integration, which replaces CocoaPods for your iOS project and needs React Native 0.87 or later. It covers pure React Native projects only, CocoaPods remains the default, and moving over is optional — see Set up your iOS project. If your app uses Kids Mode, each package manager applies it differently.

⚠️ Adapty Attribution is disabled by default

In 4.0 and earlier, the SDK registered installs for Adapty Attribution automatically. Starting from 4.1, this is off by default: the SDK doesn’t register installs, the 'onInstallationDetailsSuccess' and 'onInstallationDetailsFail' events never fire, and getCurrentInstallationStatus returns the not_available status.

If you use Adapty Attribution, enable it when activating the SDK:

  adapty.activate('YOUR_PUBLIC_SDK_KEY', {
+   adaptyAttributionEnabled: true,
  });

If you don’t use Adapty Attribution, no changes are needed.

Renamed external attribution APIs

The APIs that pass attribution data from an external provider (Adjust, AppsFlyer, Branch, Tenjin, or a custom one) are renamed to match the native SDKs.

updateAttribution → updateExternalAttribution

The method is renamed and its second parameter is renamed from source to provider. Attribution data is still a plain object:

- await adapty.updateAttribution(attribution, 'adjust');
+ await adapty.updateExternalAttribution(attribution, 'adjust');

AttributionSource → AdaptyExternalAttributionProvider

The provider type is renamed. It stays an open union — the predefined values are 'apple_search_ads', 'adjust', 'appsflyer', 'branch', 'tenjin', and a new 'custom' for providers Adapty doesn’t integrate with directly. Any other string is accepted too, so a provider Adapty adds later works without an SDK update:

- import type { AttributionSource } from 'react-native-adapty';
+ import type { AdaptyExternalAttributionProvider } from 'react-native-adapty';

AdaptyProfile.appliedAttributionSources → appliedExternalAttributionProviders

The profile property that lists the attribution providers applied to the profile is renamed, and its element type changes accordingly:

- if (profile.appliedAttributionSources?.includes('apple_search_ads')) {
+ if (profile.appliedExternalAttributionProviders?.includes('apple_search_ads')) {
      // Apple Ads attribution has been applied
  }

Code that reads it needs updating — see Show an Apple Ads targeted paywall.

Fallback files

The fallback file format changed in SDK 4.1. Download the file again from Placements > Fallbacks and bundle it in your app, even if you already downloaded one for 4.0.

hasViewConfiguration returns to AdaptyFlow

4.0 dropped hasViewConfiguration when AdaptyPaywall became AdaptyFlow. 4.1 restores it on AdaptyFlow, so a v3-era hasViewConfiguration branch works again once you rename the function and the object it reads:

- if (paywall.hasViewConfiguration) {
-   const view = await createPaywallView(paywall);
+ if (flow.hasViewConfiguration) {
+   const view = await createFlowView(flow);
    await view.present();
  }

On 4.0, where the flag is absent, createFlowView throws an AdaptyError for a flow with no view configuration. That’s still true on 4.1 — the flag is an alternative to catching, not a replacement. See Fetch the view configuration.

App Store promoted in-app purchases

On 4.0, an in-app purchase promoted on your App Store product page completed on its own and Adapty recorded the transaction like any other, but your app had no way to intercept it. 4.1 adds that hook, so this is a new capability rather than a migration step: without code of your own, the SDK still completes promoted purchases for you.

Write code only to take over completion yourself — for example to show a screen first. Register a listener for the new 'onPromotedPurchaseReceived' event, and complete the purchase with adapty.makePromotedPurchase. While that listener is registered, the SDK stops completing promoted purchases for you.