You can modify the AndroidManifest using one of two methods:

Method 1: Unity Custom Manifest

1. Navigate to File > Build Settings > Player Settings > Publishing Settings.
2. Enable "Custom Main Manifest" under the Publishing Settings section.
3. Unity generates a default AndroidManifest.xml file at Assets/Plugins/Android/AndroidManifest.xml.
4. Edit this file to add required permissions and configurations.

Source: Unity Android Manifest Documentation

Method 2: Android Studio

1. Export your project from Unity using File > Build Settings > Export Project.
2. Open the exported project in Android Studio.
3. Edit the AndroidManifest.xml file directly in Android Studio.

Method 1: Unity Custom Template

1. Navigate to File > Build Settings > Player Settings > Publishing Settings.
2. Enable "Custom Gradle Template" under the Publishing Settings section.
3. Unity generates a mainTemplate.gradle file at Assets/Plugins/Android/mainTemplate.gradle.
4. Add your custom Gradle configurations to this file.

Source: Unity Gradle Overview Documentation

Method 2: Android Studio

1. Export your project from Unity.
2. Open the project in Android Studio.
3. Edit the app's build.gradle file directly.

When building Android apps in Unity, you may encounter "Duplicate class" errors caused by multiple SDKs including the same transitive dependencies. This commonly occurs with the Android Vending Licensing library when using both AppLovin SDK and Singular SDK.

Duplicate class com.android.vending.licensing.ILicensingService found in modules 
applovin-sdk-13.5.0.aar -> jetified-applovin-sdk-13.5.0-runtime (com.applovin:applovin-sdk:13.5.0) 
and singular_sdk-12.10.0.aar -> jetified-singular_sdk-12.10.0-runtime (com.singular.sdk:singular_sdk:12.10.0)

Solution 1: Using External Dependency Manager (EDM4U)

If your project uses External Dependency Manager for Unity (recommended), add exclusion rules to your Dependencies XML file.

1. Locate your *Dependencies.xml file in your Unity project (typically in Assets/Editor or a similar location).
2. Add an exclusion rule to one of the SDK dependencies:

<dependencies>
  <androidPackages>
    <androidPackage spec="com.applovin:applovin-sdk:13.5.0">
      <androidSdkPackageIds>
        <exclude group="com.android.vending" module="licensing"/>
      </androidSdkPackageIds>
    </androidPackage>
    <androidPackage spec="com.singular.sdk:singular_sdk:12.10.0" />
  </androidPackages>
</dependencies>

Solution 2: Using Custom Gradle Templates

If you're not using EDM4U, apply exclusion rules directly in your Gradle configuration files.

1. Navigate to File > Build Settings > Player Settings > Publishing Settings.
2. Enable "Custom Main Gradle Template" or "Custom Launcher Gradle Template".
3. Open Assets/Plugins/Android/mainTemplate.gradle (or launcherTemplate.gradle).
4. Add the exclusion rule to your dependencies block:

dependencies {
    implementation('com.applovin:applovin-sdk:13.5.0') {
        exclude group: 'com.android.vending', module: 'licensing'
    }
    implementation 'com.singular.sdk:singular_sdk:12.10.0'
}

Alternative: Apply a global exclusion by adding this after your dependencies block:

configurations.all {
    exclude group: 'com.android.vending', module: 'licensing'
}

Verify Resolution

1. After applying the exclusion, clean your project by deleting Library/Bee and Temp folders.
2. Rebuild your Android project in Unity.
3. Verify the duplicate class error no longer appears in the build output.

If your project uses ProGuard for code obfuscation, add the following keep rules to your proguard-unity.txt file to prevent the Singular SDK from being stripped:

-keep class com.singular.sdk.** { *; }
-keep public class com.android.installreferrer.** { *; }
-keep public class com.singular.unitybridge.** { *; }

After building your Unity project for iOS and before building in Xcode, update your CocoaPods dependencies to ensure you have the latest SDK versions.

cd /path/to/your/ios/project
pod repo update
pod update

For testing your integration, log the IDFV (Identifier for Vendor) to quickly add your test device in the Singular SDK Console.

Add IDFV Logging

1. Open your Xcode project after building from Unity.
2. Navigate to Classes > UnityAppController.mm.
3. Find the applicationDidBecomeActive method.
4. Add the following code to log the IDFV:

// Log IDFV for testing
NSLog(@"Singular === IDFV: %@", [[[UIDevice currentDevice] identifierForVendor] UUIDString]);

5. Build and run your app in Xcode.
6. Check the Xcode console logs for the IDFV output.
7. Copy the IDFV and add it as a test device in the Singular SDK Console.

Enable Universal Links for deep linking by configuring Associated Domains in your Xcode project.

Deep Link Setup Steps

1. Add Associated Domain: In Xcode, navigate to your app target's Signing & Capabilities tab.
2. Enable capability: Click [+] Capability and add "Associated Domains".
3. Add domain: Add your Singular tracking domain in the format: applinks:yourdomain.sng.link
4. Configure Team ID: In the Singular dashboard, navigate to your app's settings and add your Apple Team ID. This allows Singular to generate and host the Apple App Site Association (AASA) file required for Universal Links.

Add Prefab to Scene

1. In the Project pane, navigate to Packages > Singular > SingularSDK > Prefabs.
2. Drag the SingularSDKObject prefab into your Hierarchy pane.
3. The prefab is now ready to configure in the Inspector.

Manual GameObject Creation

1. In the Hierarchy pane, right-click and select Create Empty.
2. Name the GameObject SingularSDKObject (exact name required).
3. With the GameObject selected, navigate to the Inspector pane.
4. Click Add Component.
5. Search for "Singular" and select the Singular SDK script component.

• Initialize On Awake: Enabled by default. The SDK initializes automatically when the GameObject awakens. Disable this if you need to delay initialization for privacy consent or other requirements.
• SKAN Enabled: Enabled by default (iOS only). Enables SKAdNetwork attribution in Managed Mode, where Singular automatically updates conversion values based on your configured conversion model.
• Wait For Tracking Authorization: Set to 0 (disabled). If your app shows the iOS App Tracking Transparency (ATT) prompt, set this to 300 seconds. This delays the SDK session until the user responds to the ATT prompt, ensuring the IDFA can be captured if consent is granted. Leave at 0 if not using ATT.
• Enable Logging: Enabled by default. Outputs SDK debug logs to help with integration and troubleshooting. Should be disabled in production builds. Works with the Log Level setting (see below).
• Log Level: Set to 3 (Info) by default. Controls logging verbosity. Lower numbers produce more verbose logs:
  C#

  // Based on Android Logger log levels
  public enum LogLevel {
     Verbose = 2,  // Most verbose
     Debug   = 3,
     Info    = 4,  // Default
     Warn    = 5,
     Error   = 6,
     Assert  = 7   // Least verbose
  }

  Note: Detailed logs are primarily available on Android.

• DDL Timeout Sec: Set to 0 (uses 60-second default). Determines how long the SDK waits for deferred deep link data from the server. The server stops searching after this timeout if no deferred deep link is found.
• Session Timeout Sec: Set to 0 (uses 60-second default). Defines how long the app can be backgrounded before the SDK creates a new session upon returning to the foreground.
• Shortlink Resolve Timeout: Set to 0 (uses 10-second default). Maximum time to wait for short link resolution. Protects user experience by preventing long waits if a short link can't be resolved.

If you need to support the legacy Meta Install Referrer attribution method, add your Facebook App ID to the SingularSDKObject configuration.

Configuration Steps

1. Select the SingularSDKObject in your scene hierarchy.
2. In the Inspector pane, locate the "Facebook App ID" field.
3. Enter your Facebook App ID (find this in your Facebook Developer Console).

Additional Resources:

• What is Meta Install Referrer?
• Where to find your Facebook App ID

Upgrade Procedure

Complete these steps in order before installing the SDK via Unity Package Manager: