Interstitial Ads issue on Android 15

[Nikolas Spiridakis]

Hello. Since our app now targets Android 15, we need to fix everything related to edge-to-edge which is now enabled by default. We managed to fix everything regarding that except the Admob Interstitial Ads. Since they use an activity we have no control, we couldn't fix it. The issue arises when the device has Navigation Buttons enabled instead of Gestures (the Navigation Buttons on landscape go on the right but the Gestures bar goes on the bottom which doesn't cause much of an issue) which makes the activity go behind them (due to edge-to-edge being enabled on Android 15) and thus obscure the X/Skip button (not clickable anymore). You can see the image below for reference:

We tried using interstitialAd.setImmersiveMode(true); but on this particular device this has no effect (it probably requires more SystemUI flags, not only the IMMERSIVE_MODE one). On another activity we have IMMERSIVE_MODE along with some other flags and the immersive mode works fine there (navigation bar is hidden).

So to summarize:

• With immersive mode off the bug can't be fixed (fullscreen ads go behind the navigation bar and gesture bar if any)
  
• The immersive mode doesn't work properly on all devices (doesn't hide navigation buttons on some devices)
  

Thanks

[Mobile Ads SDK Forum Advisor]

Hi,

Thank you for contacting the Mobile Ads SDK Support team. 

Could you kindly provide the below information via reply to author option for further investigation:

• app ID
• ad unit ID
• Mobile Ads SDK version

Additionally, you can check the Interstitial ad guidance, Disallowed interstitial implementations and Recommended interstitial implementations.  

This message is in relation to case "ref:!00D1U01174p.!5004Q02vGqty:ref" (ADR-00280124)

Thanks,
 

Mobile Ads SDK Team

Feedback
How was our support today?

               

[Nikolas Spiridakis]

Hello,

I sent everything requested.

I need to clarify that this is not an issue with our implementation but rather a BUG with the library. It doesn't properly support the new Android 15 edge-to-edge enforcement on Interstitial ads (where the activity is managed by the library). The issue only gets worse with devices that have Navigation Buttons enabled instead of Gestures as the Buttons on landscape appear on the right (rather than the bottom) and thus obscuring the X/Skip button of the Interstitial Ad.

Thanks

[Nikolas Spiridakis]

In addition, here are 2 pictures from the Official Android 15 emulator

Navigation Buttons enabled, obscures the X button:

Gestures enabled, still obscures a bit from the ad (the video progress bar) but not significant:

[Mobile Ads SDK Forum Advisor]

Hi,

I have raised this issue with wider team, One of our teammates will get back to you once we have an update on this.Meanwhile your patience is appreciated.

[Mobile Ads SDK Forum Advisor]

Hi,

Can you confirm if the issue still persists or not ? If the issue still exists kindly provide the ad request and response of the ad where the issue exists? See how to share ad request and response in ad inspector.

[Nikolas Spiridakis]

Hello. I can assure you this is not our app's issue. This happens in all Android 15 devices (ONLY on Android 15) and it is reproducible on the Official Android 15 Emulator from Android Studio. The interstitial ad opens a new activity which only the library can control and doesn't properly account the new edge-to-edge enforcement. Please read the following documentation. Thanks

https://developer.android.com/about/versions/15/behavior-changes-15#edge-to-edge

[Mobile Ads SDK Forum Advisor]

Hi Nikolas,

I tried to reproduce the edge-to-edge issue in our sample in Android 15 multiple times and I was unable to reproduce it. For us to further investigate this thoroughly we need below details for further investigation:

• ad request and response of the ad where the issue exists

• Video recording of the issue
• Sample project reproducing the issue

[Nikolas Spiridakis]

Sent everything privately, hope you got the message.

Thanks

[Mobile Ads SDK Forum Advisor]

Hi Nikolas,

Thank you for providing the requested information.

I will check this with the wider team on the edge-to-edge enforcement issue and one of my team members will reach out to you once we have an update.

[Nikolas Spiridakis]

I got your message and responded to it but in case you didn't get it:

Your sample app targets Android 14 not Android 15 that is why you are not able to reproduce the issue.

https://github.com/googleads/googleads-mobile-android-examples/blob/main/kotlin/admob/InterstitialExample/app/build.gradle#L11

You need to change the targetSDK to 35 and upgrade the AGP. Then the issue is reproduced in the official emulator (when you have buttons enabled instead of gestures).

Thank you

[Nikolas Spiridakis]

Here is how the sample app looks when targeting android 15 instead of 14 with no other change.

The status bar is white with white text and the ad x button is hidden behind the navigation buttons.

[Liran Barsisa]

This issue seems to be exactly what I'm having with rewarded ads and even the ads-inspector, and I've written a possible workaround for this till Admob would publish an official fix:

https://groups.google.com/g/google-admob-ads-sdk/c/ySMRrlVOfTs

https://github.com/googleads/googleads-mobile-android-examples/issues/783

[Mobile Ads SDK Forum Advisor]

Hi,

Thank you for sharing the detailed information. I have raised this issue with wider team, One of our teammates will get back to you once we have an update on this.Meanwhile your patience is appreciated.

[Liran Barsisa]

The issue seems to exist, not just for Admob full screen ads, but for others too.

Using the same workaround I've explained seems to work, but I'm not sure if it's good...

It's best that Admob will contact each of the ad-sources companies to tell them to make sure their full screen ads will show well on Android 15 when targeting it. 

These are the Activities that I've found for the other ad-sources:

• com.applovin.adview.AppLovinFullscreenActivity
• com.chartboost.sdk.view.CBImpressionActivity
  
• com.chartboost.sdk.internal.clickthrough.EmbeddedBrowserActivity
  
• com.inmobi.ads.rendering.InMobiAdActivity
• com.ironsource.sdk.controller.ControllerActivity
• com.ironsource.sdk.controller.OpenUrlActivity
• com.ironsource.mediationsdk.testSuite.TestSuiteActivity
• com.vungle.ads.internal.ui.VungleActivity
• com.mbridge.msdk.activity.MBCommonActivity
• com.mbridge.msdk.reward.player.MBRewardVideoActivity
• com.mbridge.msdk.newreward.player.MBRewardVideoActivity
• com.mbridge.msdk.out.LoadingActivity

I'm sure that the other ad-sources that I didn't use also have this issue.

[Nikolas Spiridakis]

I'd say let's focus on the main issue first and then look at the other networks

[Mobile Ads SDK Forum Advisor]

Hi Nikolas,

I will check with our team about this issue and one of my team members will reach out to you once we have an update. Meanwhile, I would appreciate your patience.

[Mobile Ads SDK Forum Advisor]

Hello,

Our Android engineering team is currently looking into this. I will follow up as soon as I have an update to share. 

 

This message is in relation to case "ref:!00D1U01174p.!5004Q02vGqty:ref" (ADR-00280124)

Thanks,
 

Justin Malandruccolo Mobile Ads SDK Team

Feedback
How was our support today?
               
 

 

[Zauzau Francis]

Enoch Francis  invites you to earn money together! No investment required, everyone can withdraw money! -> https://www.freeagqstar.top/p?0129797803862207069&s=mail

--

---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-admob-ads-sdk/KuHCm000000000000000000000000000000000000000000000SPDG9O00ddgEpCgBSYWWol6vYVHoow%40sfdc.net.

[Zauzau Francis]

https://app.getlee.co/r/0b2173eeb8 get this link earn money

On Tue, Dec 31, 2024, 7:49 PM 'Mobile Ads SDK Forum Advisor' via Google Mobile Ads SDK Developers <google-adm...@googlegroups.com> wrote:

[Zauzau Francis]

I have another interesting Link guys trying it https://r.honeygain.me/FZAUZ36FD8

On Tue, Dec 31, 2024, 7:49 PM 'Mobile Ads SDK Forum Advisor' via Google Mobile Ads SDK Developers <google-adm...@googlegroups.com> wrote:

[Axita Savani]

Any update on this issue ? 

[Mobile Ads SDK Forum Advisor]

Hello,

Thank you for your inquiry. I've reached out to the Android engineering team - nothing to share as of yet but I will follow up here as soon as I do. 
 

This message is in relation to case "ref:!00D1U01174p.!5004Q02vGqty:ref" (ADR-00280124)

Thanks,
 

Justin Malandruccolo Mobile Ads SDK Team

Feedback
How was our support today?
               
 

 

[Liran Barsisa]

Please also inform all ad-sources of the mediation and of other ad-formats that are full screen. This issue seems to exist for them too.

[Zauzau Francis]

Can you accept my invitation so that I can get a free gift?
Download Temu App and search the code below to accept my invitation!
595880417

On Tue, Dec 31, 2024, 7:49 PM 'Mobile Ads SDK Forum Advisor' via Google Mobile Ads SDK Developers <google-adm...@googlegroups.com> wrote:

[Axita Savani]

Any update ? 

--

---
You received this message because you are subscribed to the Google Groups "Google Mobile Ads SDK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-admob-ads...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/google-admob-ads-sdk/732441ab-fa19-4ca2-a1cc-23002b28e899n%40googlegroups.com.

[Axita Savani]

Any update Team? 

[Mobile Ads SDK Forum Advisor]

Hello,

The Android engineering team has accepted the issue and are looking into a solution. We will let you know if we have further steps.

 

This message is in relation to case "ref:!00D1U01174p.!5004Q02vGqty:ref" (ADR-00280124)

Thanks,
 

Nicholas Ventimiglia Mobile Ads SDK Team

Feedback
How was our support today?
               
 

 

[Liran Barsisa]

Please check on all full screen ads and even the ad-inspector, and also contact the various ad-networks of Admob mediation so that they fix this issue too.

[Mobile Ads SDK Forum Advisor]

Hello,

Thanks for the suggestion, I will be sure to forward this concern along.

[Rok Arnuš]

I have also replicated this bug on Android 15 emulator and Pixel 8 device. Using the Interstitial Example
https://github.com/googleads/googleads-mobile-android-examples/tree/main/java/admob/InterstitialExample

When displaying real ads in an Flutter app with the official Google Ads Plugin some ads have their Close button completely coverer. I have reported it there, but the issue was closed as it's an Google Ads SDK issue.
https://github.com/googleads/googleads-mobile-flutter/issues/1262

[Mobile Ads SDK Forum Advisor]

Thanks for the update and helpful screen shots. I have passed the information along to the engineers.

Thanks,
 

Nicholas Ventimiglia Mobile Ads SDK Team

Feedback
How was our support today?
               

[2025-02-24 19:18:59Z GMT] This message is in relation to case "ref:!00D1U01174p.!5004Q02vGqty:ref" (ADR-00280124)

[willp...@gmail.com]

Is there an update on this? I am facing the same issue

[Liran Barsisa]

I think a workaround is to set the theme to the full screen ads (and ad-inspector as both use the same Activity for some reason) ourselves.

I use this one:

Manifest:

<activity
android:name="com.google.android.gms.ads.AdActivity" android:exported="false"
android:theme="@style/AdInspectorActivityTheme" tools:replace="android:theme" />

theme:

<style name="AdInspectorActivityTheme" parent="@android:style/Theme.Translucent.NoTitleBar">
<item name="android:windowOptOutEdgeToEdgeEnforcement" tools:targetApi="35">true</item>
</style>

Sadly this flag will be ignored when targeting Android API 36:

https://developer.android.com/about/versions/16/behavior-changes-16#edge-to-edge

Hopefully Admob will fix this issue by then, and also not reaching new bugs when presented a new Android version like here.

[Kadir GÜN]

Is there any update?

[Mobile Ads SDK Forum Advisor]

Hi,

We've received confirmation from our engineering team that the bug has been accepted and they are actively working on a resolution. While I cannot provide a precise release date at this time, our current estimate is that the fix will be implemented by the end of the second quarter.

Thanks,
 

Nicholas Ventimiglia Mobile Ads SDK Team

Feedback
How was our support today?
               

[2025-03-31 17:09:02Z GMT] This message is in relation to case "ref:!00D1U01174p.!5004Q02vGqty:ref" (ADR-00280124)

[Oded]

I want to add to this issue that env(safe-area-inset-bottom) also does not work in interstitials (for GAM ads), so it's not solvable with CSS.

The only time that env(safe-area-inset-bottom) is working is after refreshing the ad using devtools

ב-יום שני, 31 במרץ 2025 בשעה 20:10:02 UTC+3, Mobile Ads SDK Forum Advisor כתב/ה:

[Diego]

We will wait for this fix to change our Apps to Android 15.

[Liran Barsisa]

Guys you are supposed to be a part of Google, be an example of how to prepare SDKs on time for Android versions.

This issue is on Android 15, and now there is Android 16 already...

I'm surprised you don't even have integration with Firebase Crashlytics, so that you get logs from there automatically about crashes related to Admob and fix them... When I tried to report such things to you, you ask for samples despite the fact that they aren't reproducible and only users had them...

[MK]

I truly hope we'll see a fix by end of 2nd quarter as indicated - or: by end of this week.

I'll have to chime in on the criticism: This has been a known issue for 6 months and it touches a wide spread Google product and, as publishers, our ability to comply with Google policies and user experience. We are not talking about some UI quirk - we are talking about hidden close buttons for full screen ads!

For us, this bug has already resulted in negative user reviews and clearly elevated click through rates on the ads (which is NOT a good thing!)

[Mobile Ads SDK Forum Advisor]

Hello all,

I just want to let you know that the engineering team has been actively working on this issue. I will keep this thread updated with the latest status.

Thanks!
 

Thanks,
 

Joshua Mobile Ads SDK Team

Feedback
How was our support today?
               

[2025-06-25 20:59:41Z GMT] This message is in relation to case "ref:!00D1U01174p.!5004Q02vGqty:ref" (ADR-00280124)

[Erick Lee]

According to latest Google Play's policy, new apps and app updates must target Android 15 (API level 35) or higher by August 31, 2025.

When the app targets API level 35, the close button on AdMob interstitial ads becomes invisible. This prevents users from dismissing the ad, creating a negative user experience. This behavior appears to directly violate AdMob policies, which prohibit ad implementations that are difficult for users to dismiss or that encourage accidental clicks. Adhering to this interstitial ad implementation could put our app at risk for having ad serving disabled.

This situation creates a policy conflict:

• To comply with the Google Play Store, we must target API 35, but doing so may force us to violate AdMob policy due to the disabled close button.

• To comply with AdMob policy, we must ensure ads are dismissible, which seems impossible if we target API 35. This would prevent us from publishing app updates after the deadline.

Please advise on the recommended solution that will allow us to comply with both Google Play and AdMob policies.

[Mobile Ads SDK Forum Advisor]

Hi Erick,

Thank you for contacting the Mobile Ads SDK Support team.

I ran the Google AdMob InterstitialExample in emulator target Android 15 (API level 35) using the latest mobile ads SDK v24.4.0 and the reported issue “invisible close button” is not replicating. Can you please confirm if the reported issue is reproducible in our Google AdMob InterstitialExample? If so, kindly share with us the below details privately so that we can check your implementation to find the root cause of the issue and may provide the solution:

• Charles logs
• Steps to reproduce/video recording of the issue
• Sample project that reproduces the issue with affected app ID & ad unit ID

You can provide the following details via reply privately to the author option or below link.

If the file(s) you are looking to share are less than 25mb in total you can attach them to this case on your next reply. If you are having trouble attaching your file to this case or if your file(s) are larger than 25mb, you can share your files with me by performing the following steps:

1. Navigate to

https://docs.google.com/forms/d/e/1FAIpQLSfkAiXMeYP-fw1W3Z-tT9uwmATEKO5X6S-th0gR2ezdKaaqfg/viewform?usp=pp_url&entry.400550049=Mobile+Ads+SDK&entry.460850823=500Ht00001rhF6iIAE&entry.80707362=00317274

2. Fill out all fields, and attach your file(s).

3. Please reply back on this thread when you have uploaded your file(s). Please do not share this link.

Thanks,
 

Mobile Ads SDK Team

Feedback
How was our support today?

               

[2025-07-04 20:33:31Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01rhF6i:ref" (ADR-00317274)

[alexander...@gmail.com]

I tested the Google AdMob InterstitialExample. The example still targets SDK Version 34 so I changed compileSdkVersion and targetSdkVersion to 35 in build.grade (Module: app). You can see the effect in the screenshot link at the end. On SDK Version 34 (left image) the word "Test Ad" stays below the pinhole for the camera. On SDK 35 (right image) the whole ad moved up without considering the pinhole. The word "Test Ad" is alrady overlapped with the pinhole. So whether a close button is clickable or not depends on the layout of the specific ad. I saw many full sceen ads where the clsoe button was at the bottom and the lower half of the button was out of the visible area.

I got the same message from Google Play Support that I need to update my apps to target Android 35, otherwise I will not be able to update my apps. Please understand that this issue will get many developers into big trouble because they rely on a fix for the full screen issue in order to comply with the play store and continue releasing their apps. There are only a few weeks left until the deadline. Can you prioritize the issue higher?

Screenshot:

https://download.changemystyle.com/admob.jpg

[MK]

Come on now! We need a fix here urgently! It is so ridiculous that this is still open!

[Leonardo Albregard Bortolotti]

Hello! I'm facing the same issue with my app.
Just updated Mobile Ads SDK to v24.4.0 and it seems that it was not fixed. Still same bug.
Waiting for a new update that fix it.
Thanks!

[Andi Susilo]

Hi Google Ads Developer Support,

The bug still exists even when using Ads SDK version 24.4.0 and building the app using targetSDKVersion 35.
You can test building your app in release mode (not debug mode), and install the app on a real Android 15 device to get real ads (which are the same ads our users get).
Then you will get some ads (not all ads) that will cover the close ad button and go to ad button when the device is using 3 navigation (not using swipe navigation).

Below is an example of an ad covering the close ad button and go to ad button, I took a screenshot of it.

[Jason.Thieu]

 I lost thousands of dollars because of this issue. At the end of April, I accidentally upgraded my game to API level 35, and afterward, my game's retention rate dropped significantly. I tried many methods, thinking the problem was related to ads or the app itself. Throughout May and June, I released nearly 20 updates in an effort to identify the cause, until I came across some users complaining about experiencing similar issues on API level 35. I immediately downgraded my game back to API level 34, and users started returning  

Vào lúc 03:34:35 UTC+7 ngày Thứ Bảy, 5 tháng 7, 2025, Mobile Ads SDK Forum Advisor đã viết:

[Mobile Ads SDK Forum Advisor]

Hi,

Thank you for contacting the Mobile Ads SDK Support team. 

This is a known issue and our engineering team has been actively working on this issue. I will keep this thread updated with the latest status.

Thanks,
 

Mobile Ads SDK Team

Feedback
How was our support today?

               

[2025-07-07 05:34:26Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01rhFNs:ref" (ADR-00317397)

[Mobile Ads SDK Forum Advisor]

Hi,

Thank you for contacting the Mobile Ads SDK Support team. 

This is a known issue and our engineering team has been actively working on this issue. I will keep this thread updated with the latest status.

Thanks,
 

Mobile Ads SDK Team

Feedback
How was our support today?

               

[2025-07-07 05:38:03Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01rhGmR:ref" (ADR-00317628)

[Mobile Ads SDK Forum Advisor]

Hi,

Thank you for contacting the Mobile Ads SDK Support team. 

This is a known issue and our engineering team has been actively working on this issue. I will keep this thread updated with the latest status.

Thanks,
 

Mobile Ads SDK Team

Feedback
How was our support today?

               

[2025-07-07 05:40:29Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01rhGml:ref" (ADR-00317631)

[Mobile Ads SDK Forum Advisor]

Hi,

Thank you for getting back to us. 

This is a known issue and our engineering team has been actively working on this issue. I will keep this thread updated with the latest status.

Thanks,
 

Mobile Ads SDK Team

Feedback
How was our support today?

               

[2025-07-07 05:43:12Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01rhF6i:ref" (ADR-00317274)

[Andi Susilo]

Hi Google Ads Developer Support,

You mentioned on April 1, 2025 "We've received confirmation from our engineering team that the bug has been accepted and they are actively working on a resolution", but it has been 3 times update the library since April 1, 2025 (v24.2.0, v24.3.0, v24.4.0) and it still doesn't solve it, are you just talking nonsense?
Please send this conversation link to the engineering team and please fix it asap.

Thanks.

[Mobile Ads SDK Forum Advisor]

Hi,

I've received an update from the wider team that this will be going into production soon, possibly within a couple of weeks.

Thanks,
 

Mobile Ads SDK Team

Feedback
How was our support today?

               

[2025-07-09 21:46:17Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01rhF6i:ref" (ADR-00317274)