Android SDK Changelog

2026-11-10

Standardized the ad unit key name to adUnitKey. The key property of ad unit objects is now adUnitKey. If you read this property or pass key = as a named constructor argument, change it to adUnitKey. Code that passes the key positionally keeps working.
Previously stored ad unit information is migrated automatically on update.

2026-11-05

Improved ad request behavior.
Ad demand sources that failed to initialize are no longer used for ad requests or retries.

2026-11-04

Fixed an issue where the app could crash if a native ad refreshed while the screen containing it was being closed.

2026-10-28

2026-10-28

Fixed a Canvas: trying to use a recycled bitmap crash that occurred while an ad was displayed.

2026-10-27

2026-09-30

2026-09-28

2026-09-28

Changes

Supports a received-asset set callback for native ads so your app can adapt its UI when assets are missing. Integration guide.
Improved Light Popup layouts, rotation handling, and dismissal.
Supports optional advertiser names in native ads. Integration guide.
Compose support from daro-compose-util is now included in daro-sdk. Use your existing Compose imports without a separate dependency.
Integrate every ad format through a single daro-sdk dependency.
Migrate to the DARO 2.0.0 SDK while keeping existing Ad Unit IDs.
Improved ad loading and reporting reliability.
Improved privacy settings and Kotlin listener stability.

Migration changes

Update the dashboard, remove legacy key files and app key settings, then configure the DARO plugin and Integration Key.
Remove the legacy SDK (before 2.0.0) dependencies and replace them with daro-sdk.
Use droom.daro.sdk.Daro for initialization and droom.daro.SDKConfig for its settings.
Remove the placement argument from Ad Unit constructors.
Use droom.daro.core.appopen.DaroAppOpenAdManager for app open ads.

See the Android migration guide for the full sequence and format checks.

2026-11-09

2026-10-20

Resolves the Integration Key per build variant. Declare a key per build variant in a flavor or build type source set AndroidManifest.xml, or through manifestPlaceholders. Use a different Integration Key per build variant.

2026-10-06

Guards against the SafeDK build_info.json not-found failure in Release builds that restore the Build Cache after clean. The process<Variant>Manifest task is excluded from Build Cache storage and restoration in builds where Ad Review is applied.
On AGP 9 and later, the process<Variant>ManifestForPackage task is excluded the same way.

2026-10-02

The daro.safedkConfigurationCacheWorkaround=true option now also covers the processing that SafeDK adds to process<Variant>Manifest tasks. This targets Release builds that still failed with a ManifestConfigurator serialization error after enabling the option.

2026-10-02

Added the daro.safedkConfigurationCacheWorkaround=true option in gradle.properties. When a Release build fails with a SafeDK task Configuration Cache serialization error, it bypasses the Configuration Cache for those tasks. When a Release build fails with SafeDK errors.

2026-09-27

Initial release of the so.daro:daro-plugin Gradle plugin for the DARO 2.0 SDK. Apps are configured with DARO_INTEGRATION_KEY in AndroidManifest.xml instead of key files.
Reads the Ad Review settings from the Integration Key and applies them to Release builds automatically.