jacattrongnlh
commented
2 years ago Here are the relevant codes:
public void InitializeBannerAds()
{
MaxSdkCallbacks.Banner.OnAdLoadFailedEvent += OnBannerAdLoadFailedEvent;
}
private void OnBannerAdLoadFailedEvent(string adUnitId, MaxSdkBase.ErrorInfo errorInfo)
{
QueueMainThreadExecution(() =>
{
GetCurrentBannerAd().State = AdObjectState.LoadFailed;
onBannerAdLoadFailedEvent?.Invoke(GetCurrentBannerAd().AdPlacementType, errorInfo);
});
}
public static void QueueMainThreadExecution(Action action)
{
#if UNITY_ANDROID
UnityMainThreadDispatcher.Instance().Enqueue(() =>
{
action.Invoke();
});
#else
action.Invoke();
#endif
}I used UnityMainThreadDispatcher since other ad networks like IronSource & Admob do not use Unity's main thread to execute callbacks so I expected AppLovin's MAX to do the same, so I used UnityMainThreadDispatcher to invoke MAX's callbacks.
UnityMainThreadDispatcher: https://github.com/PimDeWitte/UnityMainThreadDispatcher
santoshbagadi
I load a banner only once and it failed, then I get this message logged in console continously, it logged multiple times a seconds.
It also invoke the callback
MaxSdkCallbacks.Banner.OnAdLoadFailedEventwhich I'm using to log Firebase event so if this happens in release build, it'll clog up my Firebase which is unwanted.Expected behavior: When banner failed to load, error should only be logged once.
Unity version: 2020.3.18
MAX Unity Plugin version: 5.4.3.