adforus_ual_adapter 1.0.2
adforus_ual_adapter: ^1.0.2 copied to clipboard
Native UAL SDK dependencies for the Adforus Flutter plugin, with Android and iOS support through CocoaPods and Swift Package Manager.
Adforus UAL Adapter #
This is not a standalone plugin and must be used with the Adforus main plugin.
It provides the platform dependencies required for UAL:
- Android:
com.adforus.sdk:ual:1.0.1 - iOS:
UALKit 1.0.2
iOS integration supports both CocoaPods and Swift Package Manager.
Installation #
Add this adapter alongside the Adforus main plugin:
dependencies:
adforus_ual_adapter: ^1.0.2
This package provides native dependencies; initialize and load ads through the Adforus main plugin. No Dart import or adapter initialization is required.
Requires Dart 3.12+, Flutter 3.44+, Android API 24+, and iOS 14+ (or the minimum required by your Flutter version). Android builds resolve dependencies from Google Maven, Maven Central, and the Adforus and Pangle repositories configured by the adapter.
UAL's Android dependencies include the AppLovin AdMob mediation adapter. In the
full CuBid stack, adforus_uad_adapter 2.2.0 supplies Google Mobile Ads Next-Gen
SDK 1.2.1, including the compatibility classes used by the mediation adapters.
No extra legacy Google Ads SDK is required. The isolated example supplies the
same Next-Gen SDK directly. The test_bed app verifies all four published
packages together and also supports testing this local UAL update.
UAL and AppLovin ship their own keep rules. This adapter also supplies consumer
R8 rules for AppLovin's optional Fire TV PrivacyPass APIs and the WorkManager
database constructor used by Google Ads 1.2.1, so Android release builds can
keep shrinking enabled with AGP 9.
Release verification #
flutter pub get
flutter analyze
dart pub publish --dry-run
cd example
flutter test
flutter build apk --release
flutter build appbundle --release
flutter build ios --release --no-codesign
flutter test integration_test/plugin_registration_test.dart -d <android-device-id>
The example checks native plugin registration using the ual_adapter method
channel. It does not request ads or validate API tokens. Example Android release
builds use the debug signing key for local verification only.
This plugin requires API tokens available through Adforus programs. Visit the official Adforus website for more information.