[Bug] Next-Gen SDK: java.lang.Error crash on InterstitialAd.load() in production (Android)

[sucheendradas]

[REQUIRED] Step 1: Describe your environment

• Unity version: Unity 6.3
• Google Mobile Ads Unity plugin version: v11.1.0 & v11.2.0
• Plugin installation method: .unitypackage import (with External Dependency Manager)
• Platform: Android
• Platform OS version: Multiple Android versions (Live Production Issue)
• Any specific devices issue occurs on: Various Android devices
• Mediation ad networks used, and their versions: None

[REQUIRED] Step 2: Describe the problem

Steps to reproduce:

I am experiencing a critical production crash when attempting to load an Interstitial Ad using the new Next-Gen Android SDK. The crash originates deep within the native Android SDK (ads_mobile_sdk.ie1.a and ads_mobile_sdk.jg1.a, depending on R8 obfuscation) during the UnityInterstitialAd.lambda$load$0 execution.

Reverting the AdMob settings back to the "Standard" SDK completely resolves the issue. Updating from GMA v11.1.0 to v11.2.0 did not resolve the issue, confirming this is an ongoing native bug in the Next-Gen architecture.

1. Import Google Mobile Ads Unity Plugin v11.2.0.
2. Enable the Next-Gen Android SDK in Assets > Google Mobile Ads > Settings.
3. Force Resolve Android dependencies.
4. Call InterstitialAd.Load() from the Unity C# script.
5. Observe the fatal java.lang.Error crash on the Android UI thread.

Relevant Code:

public void Initialize()
{
    // Note: Ensuring ad events run on the main thread does NOT prevent this crash, 
    // as the crash occurs synchronously during the JNI load invocation, not during an async callback.
    MobileAds.RaiseAdEventsOnUnityMainThread = true;
    MobileAds.Initialize(initStatus => LoadInterstitial());
}

private void LoadInterstitial()
{
    string adUnitId = "ca-app-pub-xxxxxxxxxxxxxxxx/xxxxxxxxxx"; 
    AdRequest request = new AdRequest();

    // The crash triggers the moment this Load method is invoked.
    InterstitialAd.Load(adUnitId, request, (InterstitialAd ad, LoadAdError error) =>
    {
        if (error != null || ad == null) return;
        // Code never reaches here.
    });
}

Crash Logs (from Play Console):

Stack Trace (v11.2.0 / jg1.a obfuscation):

Exception java.lang.Error:
  at ads_mobile_sdk.jg1.a (SourceFile:138)
  at com.google.android.libraries.ads.mobile.sdk.interstitial.InterstitialAd$Companion.load (SourceFile:13)
  at com.google.android.libraries.ads.mobile.sdk.interstitial.InterstitialAd.load (Unknown Source:2)
  at com.google.unity.ads.nextgen.AdWrapper.load (AdWrapper.java:32)
  at com.google.unity.ads.nextgen.UnityInterstitialAd.lambda$load$0 (UnityInterstitialAd.java:58)
  at android.os.Handler.handleCallback (Handler.java:958)
  at android.os.Handler.dispatchMessage (Handler.java:99)
  at android.os.Looper.loopOnce (Looper.java:222)
  at android.os.Looper.loop (Looper.java:314)
  at android.app.ActivityThread.main (ActivityThread.java:8671)
  at java.lang.reflect.Method.invoke
  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:565)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1081)

---

🔍 Deep Technical Analysis & Execution Path

To assist the engineering team, here is a breakdown of the architectural failure point based on the stack trace:

1. The JNI Handoff is Successful
The C# command successfully crosses the JNI boundary. The native Java wrapper receives it at com.google.unity.ads.nextgen.AdWrapper.load (AdWrapper.java:32) and delegates it to a lambda function at UnityInterstitialAd.lambda$load$0.

2. Synchronous UI Thread Crash
Looking at the bottom of the stack trace (ActivityThread.main -> Looper.loop -> Handler.dispatchMessage), this code is being executed synchronously on the core Android UI Thread, not a background worker thread.

Because this is a synchronous failure on the native UI thread, Unity's MobileAds.RaiseAdEventsOnUnityMainThread = true configuration cannot catch or mitigate it. The crash happens before the SDK can ever generate an async callback.

3. The Point of Failure: Kotlin Lazy Initialization
The exact failure occurs at:

at kotlin.SynchronizedLazyImpl.getValue (LazyJVM.kt:74)
at ads_mobile_sdk.jg1.a (SourceFile:138)

When InterstitialAd.load is called, the obfuscated internal Next-Gen library attempts to instantiate a required object using a Kotlin SynchronizedLazyImpl. This lazy initialization fails catastrophically, throwing a java.lang.Error (not an Exception).

Because it throws an Error, it bypasses standard exception handling and instantly terminates the application. This indicates a severe internal state issue, missing dependency, or memory fault directly inside the compiled Next-Gen AAR files.

[An4seen]

Same issue here , Exception java.lang.IllegalStateException: MobileAds.initialize must be called before using the Google Mobile Ads SDK.
at ads_mobile_sdk.jg1.a (SourceFile:138)
at com.google.android.libraries.ads.mobile.sdk.interstitial.InterstitialAd$Companion.load (SourceFile:13)
at com.google.android.libraries.ads.mobile.sdk.interstitial.InterstitialAd.load (Unknown Source:2)
at com.google.unity.ads.nextgen.AdWrapper.load (AdWrapper.java:32)
at com.google.unity.ads.nextgen.UnityInterstitialAd.lambda$load$0 (UnityInterstitialAd.java:58)
at android.os.Handler.handleCallback (Handler.java:996)
at android.os.Handler.dispatchMessage (Handler.java:110)
at android.os.Looper.loopOnce (Looper.java:210)
at android.os.Looper.loop (Looper.java:302)
at android.app.ActivityThread.main (ActivityThread.java:9717)
at java.lang.reflect.Method.invoke
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:601)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1062)

[eduardocoelho]

Same here. Any update?

[vinkini]

Hey @sucheendradas, thanks for bringing this issue to our attention. We have escalated this internally and I will get back to you with an update shortly.

[vinkini]

@An4seen The exception message in your case shows that the MobileAds.Initialize has not been called before the Interstial.load call. The new Next Gen SDK made it mandatory to call the MobileAds.Initialize before loading any ads. Can you confirm that MobileAds.Initialize() has been called befoer the call to InterstitialAd.Load()

[eduardocoelho]

Please fix this. My app has ~6% crash rate after the last update, and I'm afraid this may negatively affect rankings.

[sucheendradas]

@An4seen The exception message in your case shows that the MobileAds.Initialize has not been called before the Interstial.load call. The new Next Gen SDK made it mandatory to call the MobileAds.Initialize before loading any ads. Can you confirm that MobileAds.Initialize() has been called befoer the call to InterstitialAd.Load()

Thanks for your response.

In my implementation, MobileAds.Initialize() is called before InterstitialAd.Load(). The initialization callback is where I preload all ad formats:

MobileAds.Initialize(initStatus =>
{
    Debug.Log("AdMob Initialized.");

    LoadInterstitial();
    LoadRewarded();
    LoadAppOpenAd();

    onInitializationComplete?.Invoke();
});

LoadInterstitial() is only called from:

• The MobileAds.Initialize() callback after initialization completes.
• OnAdFullScreenContentClosed to preload the next interstitial after the previous one is closed.

It is not called anywhere before MobileAds.Initialize() completes.

I have also enabled:

MobileAds.RaiseAdEventsOnUnityMainThread = true;

The crash still occurs in production with the Next Gen SDK, while the same implementation works correctly with v11.0.0. This makes me suspect there may be a regression or race condition in the newer SDK rather than an initialization order issue.

Please let me know if there is any additional logging or diagnostic information that would help identify the cause.

[sucheendradas]

Please fix this. My app has ~6% crash rate after the last update, and I'm afraid this may negatively affect rankings.

I recommend using v11.0.0 for production, as it is currently the most stable version.

[kvvin-dn]

Getting the same issue while using rewarded ads as well

[eduardocoelho]

Still happens with the latest SDK (v11.3.0).

From Google Play:

Exception java.lang.Error:
  at ads_mobile_sdk.ni1.a (SourceFile:138)
  at com.google.android.libraries.ads.mobile.sdk.interstitial.InterstitialAd$Companion.load (SourceFile:13)
  at com.google.android.libraries.ads.mobile.sdk.interstitial.InterstitialAd.load (SourceFile:2)
  at com.google.unity.ads.nextgen.AdWrapper.$r8$lambda$HfeSmb4aLtmcEewuq-RLsN_Vh6s (AdWrapper.java)
  at com.google.unity.ads.nextgen.AdWrapper$$ExternalSyntheticLambda3.load (D8$$SyntheticClass)
  at com.google.unity.ads.nextgen.AdWrapper.load (AdWrapper.java:32)
  at com.google.unity.ads.nextgen.UnityInterstitialAd.lambda$load$0$com-google-unity-ads-nextgen-UnityInterstitialAd (UnityInterstitialAd.java:58)
  at com.google.unity.ads.nextgen.UnityInterstitialAd$$ExternalSyntheticLambda1.run (D8$$SyntheticClass)
  at android.os.Handler.handleCallback (Handler.java:1029)
  at android.os.Handler.dispatchMessage (Handler.java:107)
  at android.os.Looper.loopOnce (Looper.java:274)
  at android.os.Looper.loop (Looper.java:369)
  at android.app.ActivityThread.main (ActivityThread.java:10090)
  at java.lang.reflect.Method.invoke
  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:616)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1137)

[vinkini]

This shouldnt be happening with v11.3.0. We updated the threading in that SDK to ensure the initialize and load are seriazlized.
Can you confirm that the MobileAds.Initialize is being called on the main thread. You can ensure that by calling inside the MobileAdsEventExecutor.ExecuteInUpdate() method.

MobileAdsEventExecutor.ExecuteInUpdate(() =>
{
         InitializeGoogleMobileAds();
});

[sucheendradas]

@vinkini

This shouldnt be happening with v11.3.0. We updated the threading in that SDK to ensure the initialize and load are seriazlized. Can you confirm that the MobileAds.Initialize is being called on the main thread. You can ensure that by calling inside the MobileAdsEventExecutor.ExecuteInUpdate() method.

MobileAdsEventExecutor.ExecuteInUpdate(() =>
{
         InitializeGoogleMobileAds();
});

Thanks for the suggestion!

I haven't updated my production app to Google Mobile Ads SDK v11.3.0 yet; my production app is still using v11.0.0. I'll update it to v11.3.0 soon, test it, and check whether the crash still occurs. I'll share the results once I've verified them.

Thanks for your support!

[eduardocoelho]

I’m still seeing this on v11.3.0.

After the previous discussion here, I went through my integration carefully and did find a couple of places where I was violating the SDK’s main-thread requirement.

In particular, the UMP callbacks from ConsentInformation.Update() / ConsentForm.Load() were coming back on a background thread, which meant my MobileAds.Initialize() and first InterstitialAd.Load() could also run off-thread.

I also noticed that, with RaiseAdEventsOnUnityMainThread left at its default (false), ad-event callbacks can run off-thread as well, so my reload/retry logic could end up calling back into the SDK from there.

I changed my wrapper so that I now marshal both directions onto the Unity main thread using the plugin’s own GoogleMobileAds.Common.MobileAdsEventExecutor:

static void RunOnMainThread(Action action)
{
    if (action == null) return;
    if (MobileAdsEventExecutor.IsOnMainThread())
        action();
    else
        MobileAdsEventExecutor.ExecuteInUpdate(action);
}

I call MobileAdsEventExecutor.Initialize() once on the main thread at startup, and I’m now using the helper around the SDK entry points such as MobileAds.Initialize(), SetApplicationVolume/Muted, ConsentInformation.Update(), ConsentForm.Load(), InterstitialAd.Load() and InterstitialAd.Show(), as well as inside callbacks that may trigger another SDK call.

So I was hopeful that this would finally fix the crash, but unfortunately it didn’t.

I’m still getting the following crash from Google Play:

Exception java.lang.Error:
  at ads_mobile_sdk.ni1.a (SourceFile:138)
  at com.google.android.libraries.ads.mobile.sdk.interstitial.InterstitialAd$Companion.load (SourceFile:13)
  at com.google.android.libraries.ads.mobile.sdk.interstitial.InterstitialAd.load (SourceFile:2)
  at com.google.unity.ads.nextgen.AdWrapper.$r8$lambda$HfeSmb4aLtmcEewuq-RLsN_Vh6s (AdWrapper.java)
  at com.google.unhttps://github.com/googleads/googleads-mobile-unity/issues/4206#topity.ads.nextgen.AdWrapper$$ExternalSyntheticLambda3.load (D8$$SyntheticClass)
  at com.google.unity.ads.nextgen.AdWrapper.load (AdWrapper.java:32)
  at com.google.unity.ads.nextgen.UnityInterstitialAd.lambda$load$0$com-google-unity-ads-nextgen-UnityInterstitialAd (UnityInterstitialAd.java:58)
  at com.google.unity.ads.nextgen.UnityInterstitialAd$$ExternalSyntheticLambda1.run (D8$$SyntheticClass)
  at android.os.Handler.handleCallback (Handler.java:942)
  at android.os.Handler.dispatchMessage (Handler.java:99)
  at android.os.Looper.loopOnce (Looper.java:201)
  at android.os.Looper.loop (Looper.java:288)
  at android.app.ActivityThread.main (ActivityThread.java:7941)
  at java.lang.reflect.Method.invoke
  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:569)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1019)

What is especially confusing to me is that the stack trace itself now shows UnityInterstitialAd dispatching through an Android Handler, followed by Looper.loop() and ActivityThread.main(). So at least in this crash, it really looks like InterstitialAd.load() is already being called on Android’s main thread.