Mopub 5.2.0 Load Rewarded Videos gives a lot of ANRs

[Nordhal]

Hi,
As described in the title, loading a rewarded Ad through MopubRewardedVideos gives me a lot of ANR reports. Seems to me there is a dead lock somewhere :

Blockquote
“main” prio=5 tid=1 Blocked
| group=“main” sCount=1 dsCount=0 obj=0x76741f30 self=0x7837ecba00
| sysTid=25094 nice=0 cgrp=default sched=0/0 handle=0x783c4d2ab0
| state=S schedstat=( 1561190611 428079191 2104 ) utm=82 stm=74 core=6 HZ=100
| stack=0x7fdb2a5000-0x7fdb2a7000 stackSize=8MB
| held mutexes=
at com.mopub.network.Networking.getRequestQueue (Networking.java:65)

• waiting to lock <0x0001e01a> (a java.lang.Class<com.mopub.network.Networking>) held by thread 45
  at com.mopub.mobileads.MoPubRewardedVideoManager.loadVideo (MoPubRewardedVideoManager.java:396)
  at com.mopub.mobileads.MoPubRewardedVideoManager.loadVideo (MoPubRewardedVideoManager.java:373)
  at com.mopub.mobileads.MoPubRewardedVideos.loadRewardedVideo (MoPubRewardedVideos.java:91)

I think it is not related to my code. Am I the only one to get this ANR ?
Thanks

[Nordhal]

I did not find this post yesterday, but it is related to https://twittercommunity.com/t/mopub-v-5-0-0-cause-a-lot-of-anrs-in-google-play-dev-console/107655/3 (However this is Mopub 5.2)

I need to check if SDK is initialized before trying to call the rewarded videos.
Could be great in future if we can have a static SDK InitializationListener like : Mopub.addSdkInitializationListener which call immediately “OnSDKInitializationFinished” when the sdk is already initialized.
It could help to load ads on other activities than the main one (which holds the Mopub Initialization).

[westsidefeline]

Thanks for the feedback. If you have any other issues, please contact support@mopub.com and we’ll take a look.