This "onAdHidden have long time callback" issue is not complete yet!

[tracer8]

MAX SDK Version

13.0.1

Device/Platform Info

Samsung A71

Current Behavior

Hello,

I previously reported a bug at: #756

The issue was closed without being resolved. I kindly request that issues be fully investigated and resolved before closing them. I have included my last response from that thread below for reference.

Thank you for your attention to this matter.

Thanks for the logs!

2024-12-12 15:23:13.089 18342-18342/com.example.platformsdks I/AppLovinSdk: [GoogleMediationAdapter] Interstitial ad hidden: ca-app-pub-3940256099942544/1033173712
2024-12-12 15:23:13.608 18342-18342/com.example.platformsdks D/AppLovinSdk: [MaxInterstitialAd] MaxAdListener.onAdHidden(ad=MediatedAd{thirdPartyAdPlacementId=ca-app-pub-3940256099942544/1033173712, adUnitId=acc968b6b1bb7ae0, format=INTER, networkName='Google AdMob'}), listener=com.airbnb.lottie.ads.adapters.max.MaxNetwork$2@193256

As you can see, in the above two logs there is no time gap. The first log is printed when the AdMob SDK fires the onAdDismissedFullScreenContent() callback. You can also check by adding logs in the onAdHidden callbacks you receive from AppLovin MAX. Let us know if you have any questions.

2024-12-12 15:23:13.089 -> 2024-12-12 15:23:13.608
You can observe a delay of approximately 1 second in the callback response, which is not the immediate response I expected. This noticeable delay occurs consistently, unlike the instant response we typically get with direct Admob implementation.

Expected Behavior

The onAdHidden callback is experiencing a significant delay (600ms-1second), which is causing compliance issues with Google AdMob's policies. Here's why this is problematic:

According to Google AdMob policy, interstitial ads must be shown between two screens/activities
The expected behavior: When a user closes an interstitial ad, the app should immediately transition to the next screen
Current issue: The onAdHidden callback is delayed by 600ms-1second
This delay forces users to wait before the screen transition occurs
This waiting period violates Google AdMob's policy for interstitial ad implementation
Request: The onAdHidden callback should fire immediately after the ad is closed to ensure proper screen transitions and maintain compliance with Google AdMob policies.

Expected behavior:

Ad closes
onAdHidden triggers immediately
Screen transition occurs without noticeable delay
Current behavior:

Ad closes
600ms-1second delay
onAdHidden triggers
Delayed screen transition
This needs to be addressed to maintain compliance with AdMob policies and provide a better user experience.

How to Reproduce

.

Reproducible in the demo app?

Yes

Additional Info

No response

[tracer8]

The onAdHidden callback is experiencing a significant delay (600ms-1second), which is causing compliance issues with Google AdMob's policies. Here's why this is problematic:

According to Google AdMob policy, interstitial ads must be shown between two screens/activities
The expected behavior: When a user closes an interstitial ad, the app should immediately transition to the next screen
Current issue: The onAdHidden callback is delayed by 600ms-1second
This delay forces users to wait before the screen transition occurs
This waiting period violates Google AdMob's policy for interstitial ad implementation
Request: The onAdHidden callback should fire immediately after the ad is closed to ensure proper screen transitions and maintain compliance with Google AdMob policies.

Expected behavior:

Ad closes
onAdHidden triggers immediately
Screen transition occurs without noticeable delay
Current behavior:

Ad closes
600ms-1second delay
onAdHidden triggers
Delayed screen transition
This needs to be addressed to maintain compliance with AdMob policies and provide a better user experience.

[alvarshahanji]

The delay is less than 600ms and within the acceptable range and we haven't received any complaints from AdMob or other publishers.

We closed the issue as we were able to confirm the delay is not 2-3 seconds as originally reported

[alvarshahanji]

@tracer8 Also, could you point me to the policy(link) you are referring to?