Integration

Digital Turbine (Fyber Marketplace) adapter for CloudX iOS SDK. Supports Banner, MREC, Interstitial, Rewarded, and Native.

For CloudX dashboard mapping and Digital Turbine-side ID setup, see the Digital Turbine bidder guide. This page covers iOS-specific integration details only.

Installation

CocoaPods

pod 'CloudXDigitalTurbineAdapter', '~> 8.4.10.0'

pod install --repo-update

Swift Package Manager

Add the adapter package to your project:

• Package URL: https://github.com/cloudx-io/cloudx-ios-swift-package-adapter-digitalturbine.git
• Exact package version: 8041000.0.0
• Product: CloudXDigitalTurbineAdapter

The package installs CloudX Core and Digital Turbine as dependencies. Add $(inherited) -ObjC to the app target’s Other Linker Flags.

Manual

1. Download CloudXDigitalTurbineAdapter.xcframework.zip from Releases.
2. Unzip and drag CloudXDigitalTurbineAdapter.xcframework into your Xcode project.
3. Add Fyber_Marketplace_SDK (= 8.4.10) manually.

Info.plist Configuration

SKAdNetwork IDs (Required for iOS 14+)

Include the SKAdNetwork IDs provided by Digital Turbine for your integration. Refer to the current Fyber_Marketplace_SDK documentation for the latest SKAdNetworkItems list.

App Tracking Transparency (iOS 14+)

<key>NSUserTrackingUsageDescription</key>
<string>This identifier will be used to deliver personalized ads to you.</string>

Project Configuration

Linker Flags: Add -ObjC to Other Linker Flags in Build Settings.

Native Ads

The adapter does not expose the main image asset directly: ad.nativeAd.mainImage is not populated. Media content — image or video — renders through the adapter-provided media view, which CloudX attaches to the container bound with the view binder’s mediaContentViewTag. Bind a visible media container as described in Native ads.

Compatibility

The adapter is discovered automatically when your server-provisioned CloudX configuration includes this network’s demand. No manual adapter registration is required.

Known issues

Live issues only. Resolved entries move to the adapter changelog.

Digital Turbine is not served on the iOS Simulator

Affected: every CloudXDigitalTurbineAdapter version, on the iOS Simulator only. Physical devices are not affected.

Symptom: the Fyber Marketplace SDK crashes intermittently on the Simulator, with EXC_BAD_ACCESS while it resolves Swift type metadata for one of its own generic types. To keep the Simulator usable, CloudX omits Digital Turbine from the bidder list it provisions to Simulator sessions, so the adapter is never initialized there and Digital Turbine cannot serve an ad on the Simulator. The auction may still solicit a Digital Turbine bid for the session, but that bid cannot render. The dashboard shows the same note in the Digital Turbine bidder configuration.

Status: test Digital Turbine on a physical iOS device. We have reported the crash to Digital Turbine; this entry will move to the changelog once a fixed Fyber SDK is certified.

Fyber Marketplace SDK 8.4.8 can crash Objective-C apps after SDK init

Affected: CloudXDigitalTurbineAdapter 8.4.8.0 (Fyber Marketplace SDK 8.4.8) in apps whose main target is Objective-C, or that integrate CloudXCore as a dynamic framework. Swift apps have not reproduced it.

Symptom: EXC_BAD_ACCESS a few seconds after [CloudXCore initializeSDKWithAppKey:…], on the queue com.Fyber.SDK.Marketplace.core.config, inside the Fyber SDK’s remote-configuration decoding. It reproduces on every launch.

Workaround: pin the previous adapter line, which uses Fyber Marketplace SDK 8.4.7 and is not affected — set the CloudXDigitalTurbineAdapter version in your Podfile to ~> 8.4.7.0. Run pod install --repo-update and confirm Podfile.lock shows Fyber_Marketplace_SDK (8.4.7). We have reported the issue to Digital Turbine; this entry will move to the changelog once a fixed Fyber SDK is certified.

Support

For support, contact support@cloudx.io