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
It seems to cause at least 2 different kinds of deadlock ANRs. One involving Fyber, and one involving AdMob "Google Mediation" alone.
What strikes me most about this line is the note just above it:
127// NOTE: If MAX makes an ad request to AdMob, and the AdMob account has AL enabled (e.g. AppLovin Bidding) _and_ detects the AdMob <-> AppLovin adapter, AdMob will still attempt to initialize AppLovin128MobileAds.disableMediationAdapterInitialization( context );
So, it appears as though someone is already aware that this line can lead to a deadlock, conditional upon account configuration in AdMob's dashboard.
If our AdMob account is indeed partnered with Applovin, what can we do on our end to avoid this issue?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Link to source: GoogleMediationAdapter.java:128
It seems to cause at least 2 different kinds of deadlock ANRs. One involving Fyber, and one involving AdMob "Google Mediation" alone.
What strikes me most about this line is the note just above it:
So, it appears as though someone is already aware that this line can lead to a deadlock, conditional upon account configuration in AdMob's dashboard.
If our AdMob account is indeed partnered with Applovin, what can we do on our end to avoid this issue?
Beta Was this translation helpful? Give feedback.
All reactions