AppLovin / AppLovin-MAX-Unity-Plugin

129 stars 35 forks source link

When displaying ads by connecting to Google AdMob with mediation, the X button for Close and the status bar may overlap and you cannot press it. #279

Open h-okuyama opened 1 year ago

h-okuyama commented 1 year ago

MAX Plugin Version

5.11.2

Unity Version

2020.3.48f1

Device/Platform Info

Confirmed is iPhone 11

Current Behavior

Other Versions

Behavior

I have AppLovinMax SDK Unity Plugin 5.11.2 and AppLovinMax Mediation AdMob SDK imported.

In these versions, the x button in Reward ads may be positioned outside the safe area and cannot be pressed.

Regarding the position of the x button, you can press it by hiding the status bar, Originally, it should be correct to press the x button while the status bar is displayed, so can you fix this?

Expected Behavior

The x button is displayed in the safe area and the x button can be pressed.

How to Reproduce

Same as the document here, Call ShowRewardedAd() at the timing you want to display rewards. https://dash.applovin.com/documentation/mediation/unity/ad-formats/rewarded-ads

Additional Info

Show StatusBar (In this case, the x button cannot be pressed.) ShowStatusBar

Hide StatusBar (In this case, you can press the x button, but I want you to be able to press it within the safe area) HideStatusBar

JonathanLiuApp commented 1 year ago

Hi @h-okuyama, unfortunately, I wasn't able to reproduce the bug. Are you able to reproduce this in our demo app?

h-okuyama commented 1 year ago

@JonathanLiuApp Sorry for the late reply. You said you weren't able to reproduce the bug but you mean you technically could not reproduce the bug or you tried it but you couldn't see the same result that I told you?

h-okuyama commented 1 year ago

@JonathanLiuApp I may have been a little short in providing my information. When I connected with AdMob Mediation, this occurred only for ads from specific domains, not for all ads. Maybe it is a problem on the side of the advertiser who set up the ads, such as the size ratio of the ads. I am currently blocking this domain, so the above phenomenon does not appear in my demo app, I have a feeling that the same phenomenon will occur in the future when similar settings are made by certain advertisers. Thank you always.

h-okuyama commented 1 year ago

What I want to know this time is whether the position of the × button can be adjusted on the AppLovin MAX SDK side, or whether the position of the × button when displaying an ad may change depending on the ad size and advertiser settings.

h-okuyama commented 1 year ago

@JonathanLiuApp Currently, I'm blocking ads that don't allow users to press x, so I'll try temporarily unblocking them to make it reproducible.

Attach an ad Unit Id that can display the corresponding ad later.

I'm sorry for the circumstances on my side, but I can't unblock you for a very long time because it affects 200,000 daily active users, so I'd like to know the date and time zone you can check, including the timezone.

You can unblock and review advertisers within that time.

santoshbagadi commented 1 year ago

Hi @h-okuyama , From the screenshots, those ads seem to be coming from AdMob. So, you'd have to reach out to the AdMob team.

Also, you can try to get more data about the ad using our Creative Debugger tool that let's you know what network was showing the ad.

h-okuyama commented 1 year ago

Hi @santoshbagadi , Yes, the ads are from AdMob. Since the connection is through an intermediary, I think there is probably a problem with the settings on the advertiser's side.

I had the same issue previously on Android and it was resolved by upgrading the MAX SDK (Unity: 5.11.1 -> 5.11.2, Android: 11.11.1 -> 11.11.2). I had the same problem on iOS, so I thought I might find a solution.

I am currently using a temporary method to prevent this ad from displaying, but is there a way to use the AppLovinMAX SDK or AppLovinMediationGoogleAdapter SDK to deal with this if the ad cannot be clicked?

Or, as you say, is it better to contact AdMob every time I see an ad like this?

github-actions[bot] commented 2 weeks ago

This issue is stale because it has been open for 30 days with no activity.