You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a rewarded ad has been closed by the user func didClick(_ ad: MAAd) of MARewardedAdDelegate is called while the ALAppLovinVideoViewController (the rewarded ad screen) is still in the view/navigation hierarchy.
close it by tapping on the cross button on the top right corner of the ad
check the view hierarchy at this right moment
For now my temporary solution is to delay for 800ms next tasks. 300ms is not enough for instance. So we prefer avoiding doing that since we decrease UX
Reproducible in the demo app?
Not Tested
Additional Info
here is a print after receiving the didHide event from the MARewardedAdDelegate
The text was updated successfully, but these errors were encountered:
MathisDetourbet
changed the title
didHide event from MARewardedAdDelegate called before rewarded ad dismissed
didHide event from MARewardedAdDelegate called before rewarded ad is dismissed
Oct 17, 2024
MAX SDK Version
1.13.0
Device/Platform Info
iOS 17.4
Current Behavior
When a rewarded ad has been closed by the user
func didClick(_ ad: MAAd)
of MARewardedAdDelegate is called while theALAppLovinVideoViewController
(the rewarded ad screen) is still in the view/navigation hierarchy.Expected Behavior
As the naming says,
didHide
should be called when the rewarded ad is not in the view hierarchy anymore. The documentation also says that this event is send when "Rewarded ad is hidden." (https://developers.applovin.com/en/max/ios/overview/manual-integration#loading-a-rewarded-ad)How to Reproduce
For now my temporary solution is to delay for 800ms next tasks. 300ms is not enough for instance. So we prefer avoiding doing that since we decrease UX
Reproducible in the demo app?
Not Tested
Additional Info
here is a print after receiving the didHide event from the
MARewardedAdDelegate
The text was updated successfully, but these errors were encountered: