Maven Central migration guide

Migrate your Unity LevelPlay Android project to Maven Central by updating your build.gradle to remove the is.com repository and adding mavenCentral(), then importing the Unity LevelPlay SDK and Ad Quality SDK using the appropriate Maven dependencies.

Read time 1 minutes

As part of the Unity and ironSource unification, the Unity LevelPlay SDK for Android, all supported ad network adapters, and the Ad Quality SDK for Android will be migrated from is.com to Maven Central.

As a made-with-Unity developer who has integrated Unity LevelPlay, you must migrate your project dependencies to Maven Central by June 30, 2025 to continue building your projects and using Unity LevelPlay and Ad Quality without disruption.

You'll need to take specific actions depending on which version of the LevelPlay Unity package (which wraps the LevelPlay SDK) and Ad Quality SDK you've integrated into your project. Refer to the following tables to determine your next steps based on your SDK version.

LevelPlay Unity package users

LevelPlay Unity package versionInstallation dateRequired action
7.9.0 and newerInstalled after November 21, 2024No action required. Migration occurs automatically when you update.
7.9.0 - 8.4.1Installed before November 21, 2024 and not updated sinceUpdate to a newer Unity package version than your current version to enable automatic migration. If you choose not to update, check your project dependencies and follow manual migration steps if needed. Refer to Determine if manual migration is required section for details.
Earlier than 7.9.0Any dateMust update Unity package version to at least 7.9.0 to maintain development and build functionality.

Ad Quality Unity package users

Ad Quality SDK versionInstallation dateRequired action
7.19.2 and newerInstalled after October 30, 2024No action is required. Migration occurs automatically when you update.
7.19.2 and newerInstalled before October 30, 2024 and not updated sinceUpdate to a newer SDK version than your current version to enable automatic migration. If you choose not to update, check your project dependencies and follow manual migration steps if needed. Refer to Determine if manual migration is required section for details.
Earlier than 7.19.2Any dateMust update SDK version to at least 7.19.2 to maintain development and build functionality.

Before proceeding with manual migration, confirm which LevelPlay Unity package (which wraps the LevelPlay SDK) and Ad Quality SDK versions you're using. The next section provides steps to verify your SDK versions and determine if a manual migration is required.

Determine if manual migration is required for LevelPlay Unity package users

To determine if your project requires a manual migration, follow these steps to check for outdated dependencies in your project files.

In the Unity Editor, go to Assets > LevelPlay > Editor. Search for the string “https://android-sdk.is.com/” in any XML file within this folder. If found, proceed with the Manual migration steps section:

  1. Open IronSourceSDKDependencies.xml or any xml file related to the adapters used in your project.
  2. Search for the following lines of code in the repository reference file, and confirm if the AndroidPackage spec and repository tags look like the following:
    • If these lines of code exist, proceed with the Manual migration steps section.
    • If these lines of code are absent, the dependencies in your project already use Maven Central, so no action is needed from you.
<androidPackages>
 <androidPackage spec="com.ironsource.sdk:mediationsdk:7.9.0">
 <repositories>
        <repository>https://android-sdk.is.com/</repository>
      </repositories>
 </androidPackage>
</androidPackages>

Determine if manual migration is required for Ad Quality Unity package users

To determine if your project requires a manual migration, follow these steps to check for outdated dependencies in your project files.

  1. In the Unity Editor, go to Assets > LevelPlay > Editor.
  2. Open IronSourceAdQualityDependencies.xml in your project.
  3. Search for the following lines of code in the repository reference file, and confirm if the AndroidPackage spec and repository tags look like the following:
    • If these lines of code exist, proceed with the Manual migration steps section.
    • If these lines of code are absent, the dependencies in your project already use Maven Central, so no action is needed from you.
<androidPackages>
 <androidPackage spec="com.ironsource:adqualitysdk:7.19.1">
 <repositories>
        <repository>https://android-sdk.is.com/</repository>
      </repositories>
 </androidPackage>
</androidPackages>

Manual migration steps for LevelPlay Unity package users

Follow these steps to complete the manual migration of your project to Maven Central while ensuring your dependencies are correctly updated:

  1. Go to your project's Assets > LevelPlay > Editor folder.

  2. Delete the IronSourceSDKDependencies.xml file.

  3. Delete the following installed mediation adapter dependency XML files:

    • ISAdColonyAdapterDependencies.xml
    • ISAdMobAdapterDependencies.xml
    • ISAppLovinAdapterDependencies.xml
    • ISAPSAdapterDependencies.xml
    • ISBidMachineAdapterDependencies.xml
    • ISBigoAdapterDependencies.xml
    • ISChartboostAdapterDependencies.xml
    • ISCSJAdapterDependencies.xml
    • ISFacebookAdapterDependencies.xml
    • ISFyberAdapterDependencies.xml
    • ISHyprMXAdapterDependencies.xml
    • ISInMobiAdapterDependencies.xml
    • ISMaioAdapterDependencies.xml
    • ISMintegralAdapterDependencies.xml
    • ISMobileFuseAdapterDependencies.xml
    • ISMolocoAdapterDependencies.xml
    • ISMyTargetAdapterDependencies.xml
    • ISOguryAdapterDependencies.xml
    • ISPangleAdapterDependencies.xml
    • ISSmaatoAdapterDependencies.xml
    • ISSuperAwesomeAdapterDependencies.xml
    • ISTapJoyAdapterDependencies.xml
    • ISTencentAdapterDependencies.xml
    • ISUnityAdsAdapterDependencies.xml
    • ISVerveAdapterDependencies.xml
    • ISVungleAdapterDependencies.xml
    • ISYandexAdapterDependencies.xml
  4. Open the Network Manager in the Ads Mediation package, select the ironSource SDK and required mediation adapters, then select Install.

  5. Verify migration success by confirming the XML files are updated in the Assets > LevelPlay > Editor folder, and ensure the following XML files are present:

    • IronSourceSDKDependencies.xml
    • The corresponding adapter dependency XML files for the adapters you reinstalled.
  6. Open the following files and confirm they're correctly referencing the dependencies from Maven Central:

    <androidPackages>   
       <androidPackage spec="com.unity3d.ads-mediation:mediation-sdk:x.x.x">
       </androidPackage>
     </androidPackages>
    
     <androidPackages>
       <androidPackage spec="com.unity3d.ads-mediation:unityads-adapter:x.x.x">
       </androidPackage>
     </androidPackages>
    
  7. Build and run your project to verify a successful migration. If you encounter issues with the migration, update the Unity LevelPlay package to version 7.9.0 or newer.

Manual migration steps for Ad Quality package users

Follow these steps to complete the manual migration of your project to Maven Central while ensuring your dependencies are correctly updated:

  1. Go to your project's Assets > LevelPlay > Editor folder.

  2. Delete the IronSourceAdQualityDependencies.xml file.

  3. Download the XML version that supports Maven Central (7.19.2 and higher).

  4. Verify migration success by confirming the XML files are updated in the Assets > LevelPlay > Editor folder, and ensure the following XML files are present:

    • IronSourceAdQualityDependencies.xml
  5. Open the following files and confirm they're correctly referencing the dependencies from Maven Central:

    <androidPackages>   
       <androidPackage spec="com.unity3d.ads-mediation:adquality-sdk:x.x.x">
       </androidPackage>
     </androidPackages>
    
  6. Build and run your project to verify a successful migration.