[AdMob] Ads Adapter Fails After IronSource Integration
Under Audit
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.
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.
- Verify
AdMobmediation group configurations for bothUnity Adsand IronSource to ensure no conflicting setups. - Check for potential SDK conflicts between the IronSource SDK and the
AdMobmediation adapter forUnity Ads. - Confirm that the
Unity Adsadapter andAdMobSDK versions are up to date and compatible with each other.
Editor's Note:
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.