Getting Started

An Ad Unit defines an ad placement and format in your app. For the DARO 2.0.1 SDK, copy the Ad Unit Key from the updated dashboard. This is different from the app’s Integration Key. API parameters such as adUnitId, unitId, and key, and example placeholders such as YOUR_AD_UNIT_ID, keep their names but take that Ad Unit’s Ad Unit Key. Existing integrations using Ad Unit IDs remain supported. Do not confuse reporting or callback identifiers with the key for a new integration.

Before You Begin

Check requirements before integration.

Requirements

Android minSdkVersion: 23

Verify app-ads.txt setup before proceeding.

Desugaring required: Configure desugaring if minSdk is below 26.

android {
    ...

    compileOptions {
        isCoreLibraryDesugaringEnabled = true
        sourceCompatibility = JavaVersion.VERSION_1_8
        targetCompatibility = JavaVersion.VERSION_1_8
    }

    ...
}

...

dependencies {
    ...

    coreLibraryDesugaring("com.android.tools:desugar_jdk_libs:2.0.4")

    ...
}

android {
    ...

    compileOptions {
        coreLibraryDesugaringEnabled true
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }

    ...
}

...

dependencies {
    ...

    coreLibraryDesugaring 'com.android.tools:desugar_jdk_libs:2.0.4'

    ...
}

Upgrading From an Earlier Version

Follow the Android migration guide to update the dashboard and remove legacy key files and app key settings first. Then integrate the DARO 2.0.1 SDK in the order below.

Configure Your App

Project-level build configuration

Add the repositories below to settings.gradle.kts (Kotlin DSL) or settings.gradle (Groovy DSL) in the project root.
If dependencyResolutionManagement already exists, add the repositories to its repositories block.

dependencyResolutionManagement {
    repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS)
    repositories {
        google()
        mavenCentral()
        maven { url = uri("https://artifact.bytedance.com/repository/pangle") }
        maven { url = uri("https://android-sdk.is.com/") }
        maven { url = uri("https://dl-maven-android.mintegral.com/repository/mbridge_android_sdk_oversea") }
        maven { url = uri("https://repo.pubmatic.com/artifactory/public-repos") }
        maven { url = uri("https://maven.ogury.co") }
    }
}

dependencyResolutionManagement {
    repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS)
    repositories {
        google()
        mavenCentral()
        maven { url 'https://artifact.bytedance.com/repository/pangle' }
        maven { url 'https://android-sdk.is.com/' }
        maven { url 'https://dl-maven-android.mintegral.com/repository/mbridge_android_sdk_oversea' }
        maven { url 'https://repo.pubmatic.com/artifactory/public-repos' }
        maven { url 'https://maven.ogury.co' }
    }
}

Add the DARO plugin to build.gradle(root)

Add the DARO plugin to your build.gradle(root) file.

Set the DARO plugin version separately from daro-sdk. When updating the plugin in an existing integration, change its classpath version in the root build.gradle as well.

Latest version

daro-plugin : 2.0.3

buildscript {
    repositories {
        google()
        mavenCentral()
        maven { url = uri("https://artifacts.applovin.com/android") }
    }
    dependencies {
        classpath("so.daro:daro-plugin:2.0.3")
    }
}

buildscript {
    repositories {
        google()
        mavenCentral()
        maven { url 'https://artifacts.applovin.com/android' }
    }
    dependencies {
        classpath 'so.daro:daro-plugin:2.0.3'
    }
}

Apply the DARO plugin to build.gradle(app)

Apply the DARO plugin in build.gradle(app).

plugins {
    ...
    id("so.daro")
    ...
}

plugins {
    ...
    id 'so.daro'
    ...
}

Declare DARO_INTEGRATION_KEY in AndroidManifest.xml

Declare the Integration Key inside <application> in your app module’s src/main/AndroidManifest.xml.

<application
    ...>

    <meta-data
        android:name="DARO_INTEGRATION_KEY"
        android:value="YOUR_INTEGRATION_KEY" />

    ...
</application>

The Integration Key is issued per app and can be obtained from the DARO dashboard.

This example uses the same dashboard app for every build variant. Enter that app’s Integration Key as a literal value in the app module’s src/main/AndroidManifest.xml. When setting DARO_INTEGRATION_KEY in the manifest, enter the actual key value instead of a ${...} placeholder.

Update app-ads.txt

Follow the app-ads.txt guide and publish the latest content provided by the dashboard.

Add DARO SDK

Add the DARO SDK.

Latest version

daro-sdk : 2.0.2

dependencies {
    ...
    implementation("so.daro:daro-sdk:2.0.2")
    ...
}

dependencies {
    ...
    implementation 'so.daro:daro-sdk:2.0.2'
    ...
}

daro-sdk provides Compose components, including DaroBanner and DaroNative, in the droom.daro.compose package.
For a new integration, use these components without a separate daro-compose-util dependency. Your app needs Compose runtime 1.7.0 or later.
If you previously used so.daro:daro-compose-util, remove that dependency and use the Compose components provided by daro-sdk. You can keep your existing imports.

If a Release build fails with a SafeDK error

If a Configuration Cache serialization error occurs

Use the following steps if a Release build with Configuration Cache enabled fails while storing the cache, and the error log names a safedkAdjustInputs... or safedkInstrumentation... task with messages such as:

cannot serialize object of type 'com.android.build.gradle.internal.tasks.R8Task'
cannot serialize object of type 'org.gradle.api.internal.project.DefaultProject'

When this error occurs, use these steps to bypass Configuration Cache for SafeDK tasks:

Update the daro-plugin version in the root build.gradle classpath to 2.0.3 or later. You can keep your daro-sdk version.
Add the following setting to the project’s root gradle.properties.
gradle.properties
daro.safedkConfigurationCacheWorkaround=true
Run the failed Release build again and check the result. If errors remain in other tasks, investigate those errors separately.

This setting keeps SafeDK functionality and tasks enabled while preventing builds that include those tasks from storing or reusing the Configuration Cache. The configuration phase runs again on the next build and may take longer. Gradle’s build output cache is separate.

You do not need to enable this option if your project does not encounter the error. It is disabled by default. Remove the option or set it to false after verifying a compatible vendor fix in that app environment.

If Manifest serialization still fails after enabling the option

If daro-plugin 2.0.1 still fails on a process<Variant>Manifest task after you enable the option, and the error mentions com.safedk.gradleplugin.configurators.ManifestConfigurator and ReferenceQueue serialization, update the plugin to 2.0.3 or later, keep daro.safedkConfigurationCacheWorkaround=true, and run the same Release build again. Starting with 2.0.2, this option also covers the processing that SafeDK adds to Manifest tasks. If you cannot update immediately, add --no-configuration-cache to the failed Release build command and run it again. For example, use this command when the app module is named app and the build variant is release:

./gradlew :app:assembleRelease --no-configuration-cache

If your module or flavor differs, keep the original Release task name. This option disables Configuration Cache for that invocation while keeping SafeDK tasks enabled. The build output cache remains separate. If the same error persists, send DARO the failing task name and error log.

If a Release build fails because `build_info.json` cannot be found

Update the plugin if a Release build restores the build output cache (Build Cache) after clean and fails with the following error:

FileNotFoundException: .../safedk/properties/.../build_info.json (No such file or directory)

Update the daro-plugin version in the root build.gradle classpath to 2.0.3 or later.
kotlin
classpath("so.daro:daro-plugin:2.0.3")
Run the failed Release build again and check the result.

The fix for this error applies automatically when you update the plugin. You do not need to add a separate option or change your daro-sdk version. If you already use daro.safedkConfigurationCacheWorkaround=true to bypass a Configuration Cache error, keep it after updating. Adding only this option without updating the plugin does not fix the Build Cache restoration error.

The SDK includes consumer obfuscation rules that Gradle applies automatically. You do not need to copy them into your project.

Initialize SDK

Important: Load Ads After Initialization

Initialize DARO SDK before loading ads by calling Daro.init().
Requesting ads before initialization may prevent proper display.

import android.app.Application
import droom.daro.SDKConfig
import droom.daro.sdk.Daro

class AppApplication : Application() {

  override fun onCreate() {
    super.onCreate()

    // Daro SDK initialization
    Daro.init(
      application = this,
      sdkConfig = SDKConfig.Builder()
          .setDebugMode(false) // (debug mode, default : false — must be false in production builds)
          .setAppMuted(false) // (set app mute, default : false)
          .build()
    )
  }
}

setDebugMode(true) is for test builds only. Always set it to false in production builds.

App Mute Setting

For app open, banner, interstitial, rewarded, rewarded interstitial, and native ad formats, you can use the setAppMuted(...) method to inform the DARO SDK that the app volume has been muted.

// Mute app
Daro.setAppMuted(true)


// Unmute app
Daro.setAppMuted(false)

Native ads apply the mute state to video playback at load time, so call setAppMuted before loading native ads.

App Mute Usage PrecautionsWhen app mute is enabled, some video ad creatives that cannot play while muted may be excluded from ad requests, which can slightly reduce the ad pool and affect revenue.

DARO 2.0 SDK Migration

SDK Integration

How to Use DARO

FAQ

Legacy SDK

Getting Started

Before You Begin

Requirements

Upgrading From an Earlier Version

Configure Your App

If a Release build fails with a SafeDK error

If a Configuration Cache serialization error occurs

If Manifest serialization still fails after enabling the option

If a Release build fails because `build_info.json` cannot be found

Initialize SDK

App Mute Setting

​Before You Begin

​Requirements

​Upgrading From an Earlier Version

​Configure Your App

​If a Release build fails with a SafeDK error

​If a Configuration Cache serialization error occurs

​If Manifest serialization still fails after enabling the option

​If a Release build fails because build_info.json cannot be found

​Initialize SDK

​App Mute Setting

Before You Begin

Requirements

Upgrading From an Earlier Version

Configure Your App

If a Release build fails with a SafeDK error

If a Configuration Cache serialization error occurs

If Manifest serialization still fails after enabling the option

If a Release build fails because `build_info.json` cannot be found

Initialize SDK

App Mute Setting