AndroidDeveloperLB

Results 854 comments of AndroidDeveloperLB
trafficstars

It's wrong because I've noticed it on my own app, when I wanted to use the same but with both width&height, using `AdSize.getInlineAdaptiveBannerAdSize`. When I've provided it a height of...

I've found a workaround: replace the theme of AdActivity that is responsible of ad-inspector, to avoid edge-to-edge, as possible via this: https://www.androidauthority.com/android-15-edge-to-edge-opt-out-3467646/#:~:text=The%20API%20in,window%20in%20question. Meaning to add this to manifest: ``` ```...

It seems to occur now for Unity ads too, and so it seems it's the behavior of errors on such SDKs in general: https://github.com/googleads/googleads-mobile-android-mediation/issues/558 What I suggest is: 1. Before...

It seems that at least for the case of Vungle/Liftoff, I had an issue on the mapping on Admob website, where a space character (" ") was added to the...

I think it got fixed today on v24.3.0, despite not being mentioned on the version history yet: https://developers.google.com/admob/android/rel-notes Weird thing is that when I target API 36 and run on...

@1nikolas I think it's not fixed for the ad-inspector (and only on API 36 when targeting it), but fine for rewarded ads. Weird.

@wasky Seems you are correct. I wonder what exactly did I see... So still need to use the workaround I wrote about, and still target API 35...

@wasky Sure you target API 35 and not API 36 ? Here's how it looks like after using it, tested on Pixel 6 with Android 15: Rewarded ad: ![Image](https://github.com/user-attachments/assets/657982d3-4d02-4f21-a65a-6cd0036dd65d) Ad...

@wasky No. The app targets API 35. When I target API 36 and run on API 36, the workaround can't work, because the windowOptOutEdgeToEdgeEnforcement can't be used there anymore. https://developer.android.com/about/versions/16/behavior-changes-16#edge-to-edge...