For Android

Declaring and Setting up Maven Dependencies

1. Open the Player Settings, and select the Custom Gradle Template checkbox, which generates a file in Assets/Plugins/Android/launcherTemplate.gradle.

2. Copy the following repositories and dependencies, and add them to your corresponding repositories and dependencies blocks in launcherTemplate.gradle.

For iOS

Declaring and Setting up CocoaPods Dependencies

1. Export the Xcode project and build the project on Unity.

2. If CocoaPods is not installed on your system, install it by running the following command in the terminal:

sudo gem install cocoapods

pod init

pod install --repo-update

target 'Unity-iPhone' do 
end

For Android

Resolving Dependencies on Android

Dependencies resolve automatically for Android.
(Optional) To force dependency resolution, from the Menu bar, navigate to Assets → External Dependency Manager → Android Resolver → Force Resolve.

For iOS

Resolving Dependencies on iOS

EDM4U automatically resolves all the dependencies declared in a specific .xml file and add the respective entries to your Podfile.

In iOS, resolution occurs when you export the project. Do the following when you select AdMob, hyprMX, or EDM:

• AdMob: Click build as you need to Add SKAdNetwork IDs to the Info.plist.
• HyprMX: 
  1. Navigate to Assests → External Dependency Manager → iOS Resolver  → Settings.
  2. Select Always add the main target to Podfile.
• EDM: 
  1. Navigate to Assets → External Dependency Manager → iOS Resolver  → Settings.
  2. Deselect Link frameworks statically.
     If you do not deselect the option, you may encounter a compilation error about missing the   FairBidSDK/FairBidSDK-Swift.h file. 
  3. Open the .xcworkspace file in Xcode, not the .xcodeproj file.
     EDM creates the .xcworkspace file when it builds the project.
  4. Locate the Podfile in the build folder and run pod install when the .xcworkspace file does not appear to generate .xcworkspace.

For Android

Configuring the Android Manifest

Some networks might require you to add entries to AndroidManifest.xml when you build for Android. Create an AndroidManifest.xml file  in Assets → Plugins → Android when your project does not contain an AndroidManifest.xml. If you have selected one of those networks in the table, the respective entries appear:

1. Copy the following entries to the AndroidManifest.xml.

2. Paste the relevant entries in the root level under <manifest> and the remaining ones under <application>.

The following example shows a typical Unity Manifest:

<?xml version="1.0" encoding="utf-8"?>
<manifest
    xmlns:android="http://schemas.android.com/apk/res/android"
    package="com.unity3d.player"
    xmlns:tools="http://schemas.android.com/tools"
    android:installLocation="preferExternal">
    <supports-screens
        android:smallScreens="true"
        android:normalScreens="true"
        android:largeScreens="true"
        android:xlargeScreens="true"
        android:anyDensity="true"/>

    <application
        android:theme="@style/UnityThemeSelector"
        android:icon="@mipmap/app_icon"
        android:label="@string/app_name">
        <activity android:name="com.unity3d.player.UnityPlayerActivity"
                  android:label="@string/app_name">
            <intent-filter>
                <action android:name="android.intent.action.MAIN" />
                <category android:name="android.intent.category.LAUNCHER" />
            </intent-filter>
            <meta-data android:name="unityplayer.UnityActivity" android:value="true" />
        </activity>
    </application>
</manifest>

For most Unity installations, the default manifest is available in the Editor's installation at the following location: /Applications → Unity → Hub → Editor → [version] → PlaybackEngines → AndroidPlayer → Apk

For further information about integrating and controlling an Android manifest in your Unity integration, see Utility Android App Manifest.

Dex limit

An Android limitation prevents you from having more than 65536 methods when you package your app plus dependencies. A limitation typically occurs when your app targets versions lower than Android API 21. Enable multidex to solve the problem, and add the following snippet to your launcherTemplate.gradle file. 

android {
    defaultConfig {
        ...
        multiDexEnabled true
    }
    ...
}

dependencies {
    implementation 'com.android.support:multidex:1.0.3'
}

For further information, see Enable multidex for apps with over 64K methods.

For iOS

Configuring the Info.plist and Adding SKAdNetwork IDs

DT helps you and generates an exhaustive list of the required SKAdNetwork IDs to implement in your Info.plist file. The list includes the SKAdNetwork IDs of the DT Exchange DSPs and any check-boxed mediated networks in Step 1.

Add the SKAdNetwork ID list below to the app Info.plist file when you select your mediated network set.

You can use Xcode's GUI to edit it or open the .plist file with a text editor, copy and paste the snippet.