UnityRef is currently in early development. Some features may be incomplete and/or not functioning.

UNITYREF

Your Pit Stop For Solving ANYTHING in Unity

architecture

[AdMob] Ads Adapter Fails After IronSource Integration

Under Audit

neural networksadministrationtroubleshooting

Unity 2021.3.x - Unity 6.1.x

Published Tue, Mar 17

The Unity Ads adapter consistently fails to initialize via Google AdMob mediation, reporting an initialization state: 0, particularly after integrating IronSource.

Issue

 The GADMediationAdapterUnity fails to initialize when mediating through Google AdMob, consistently reporting an initialization state: 0. This issue appears to be directly linked to the creation of an IronSource account. Prior to the IronSource account creation, all existing project builds successfully initialized the Unity Ads adapter. Following the establishment of the IronSource account, all builds, including those previously functional, now report an initialization state: 0 for the adapter, and Unity impressions drop to zero.

Experimental Fixes
  • Verify AdMob mediation group configurations for both Unity Ads and IronSource to ensure no conflicting setups.
  • Check for potential SDK conflicts between the IronSource SDK and the AdMob mediation adapter for Unity Ads.
  • Confirm that the Unity Ads adapter and AdMob SDK versions are up to date and compatible with each other.

Editor's Note:

The above fixes have not been verified by our audit team yet. They are provided exclusively for your own technical research. We recommend creating a backup of your project before proceeding with any attempts. Utilize at your own discretion!

Related Posts Haven't quite found a solution to your problem? We think these posts might help you.

Content inspired by a Unity discussion post.