Migration Guide

​

1. Update the dashboard

• In the DARO dashboard, select the app you are migrating and complete the update.
• Find the Integration Key and Ad Unit Keys for the Android app and the iOS app separately.

​

2. Remove legacy key files and settings

• Remove daro-services.json, daro-service.json, daro-key.txt, android-daro-key.txt, ios-daro-key.txt, and any settings that reference them. Also check file references registered in Xcode and the Copy Bundle Resources entries.
• Remove the existing daroAppKey setting from android/gradle.properties and your build scripts.
• If you used the Expo config plugin, remove daroAppKey, daroKeyFile, and admobAppId.

​

3. Configure DARO integration tools

• If you used react-native-daro-m, remove it and install react-native-daro.
• If you already use react-native-daro, update the same package.

npm uninstall react-native-daro-m
npm i [email protected]

• The two packages pull in different native SDKs, so do not keep both.
• Follow the Android migration guide and the iOS migration guide to prepare the build tools the new SDK requires.
• Expo projects use the config plugin described in Get Started.
• React Native CLI projects follow the manual setup in the same document.
• Do not apply the previous plugin alongside the new one.

​

4. Configure the Integration Key and app settings

• Get the Integration Key for each platform’s app from the dashboard and configure it.
• Use the key that belongs to each app for Android and iOS.
• The Expo config plugin takes a single key per platform.

{
  "expo": {
    "plugins": [
      [
        "react-native-daro",
        {
          "ios": {
            "daroAppKey": "YOUR_PREVIOUS_IOS_APP_KEY",
            "daroKeyFile": "./ios-daro-key.txt",
            "admobAppId": "ca-app-pub-xxxxxxxx~xxxxxxxx"
          },
          "android": {
            "daroAppKey": "YOUR_PREVIOUS_ANDROID_APP_KEY",
            "daroKeyFile": "./android-daro-key.txt"
          }
        }
      ]
    ]
  }
}

{
  "expo": {
    "plugins": [
      [
        "react-native-daro",
        {
          "ios": {
            "daroIntegrationKey": "YOUR_IOS_INTEGRATION_KEY"
          },
          "android": {
            "daroIntegrationKey": "YOUR_ANDROID_INTEGRATION_KEY"
          }
        }
      ]
    ]
  }
}

• After changing the configuration, run npx expo prebuild.
• For manual integration, follow the platform settings in Get Started, and run pod install in the ios/ directory.

​

5. Update app-ads.txt

• Follow the app-ads.txt guide and publish the latest content provided by the dashboard.
• Confirm that the file is accessible on the website registered in the dashboard.

​

6. Update SDK dependencies and code

​

Update import paths

• Update every import path that came from react-native-daro-m.

// Before
import { AdBannerView, AdFormat, initialize } from "react-native-daro-m";

// After
import { AdBannerView, AdFormat, initialize } from "react-native-daro";

​

Remove placement

• placement has been removed from ad creation arguments and from the banner and native components.

// Before
<AdBannerView
  style={styles.bannerView}
  adFormat={AdFormat.BANNER}
  adUnitId={BANNER_AD_UNIT_ID}
  placement="main_bottom"
/>

// After
<AdBannerView
  style={styles.bannerView}
  adFormat={AdFormat.BANNER}
  adUnitId={BANNER_AD_UNIT_ID}
/>

​

Move from the static ad API to the Hook or instance API

• The static APIs for interstitial, rewarded, and light popup ads (InterstitialAd.loadAd and so on) still work the same way in the DARO 2.0 SDK, but they are deprecated.
• Your app still builds if you move only some of the formats, so you can migrate one format at a time.

import { InterstitialAd } from "react-native-daro-m";

InterstitialAd.addAdLoadedEventListener(() => {
  InterstitialAd.showAd(INTERSTITIAL_AD_UNIT_ID);
});

InterstitialAd.loadAd(INTERSTITIAL_AD_UNIT_ID);

import { Button } from "react-native";
import { useInterstitialAd } from "react-native-daro";

function InterstitialAdButton() {
  const { isLoaded, load, show } = useInterstitialAd(INTERSTITIAL_AD_UNIT_ID, {
    onLoadFailed: (error) => console.log(error.message),
  });

  return (
    <Button
      title={isLoaded ? "Show Ad" : "Load Ad"}
      onPress={() => (isLoaded ? show() : load())}
    />
  );
}

• To manage an ad outside a component, use the instance API.
• Registering a listener returns a function that removes it.

import { AdEventType, InterstitialAd } from "react-native-daro";

const ad = InterstitialAd.createForAdRequest(INTERSTITIAL_AD_UNIT_ID);
const removeLoadedListener = ad.addAdEventListener(AdEventType.LOADED, () => {
  ad.show();
});

ad.load();

// When the ad is no longer needed
removeLoadedListener();
ad.removeAllListeners();

​

Initialization order

• Load ads and render the banner and native components only after initialize() completes.
• If your app sets consent states, call setGdpr, setCcpa, and setCoppa before initialize(). For child-directed apps, setCoppa must already be in effect for the initialization request itself.

​

Check each ad format

​

What you gain after migrating

• Native ads, which react-native-daro-m did not provide, are now available.
• AdInfo in the ad callbacks adds mediationPlatform and adNetwork, so you can see which ad demand source filled the ad. The existing fields are unchanged.
• Native ads accept adChoicesPosition to set the preferred position of the AdChoices icon.

​

Verify before release

• Rebuild the Android and iOS apps, then verify loading, display, dismissal, and callbacks on a real device for every ad format you use.
• If you use rewarded video ads, verify the reward callback as well.
• Keep the existing Ad Unit IDs in released versions that still use the legacy SDK (before 2.0.0).