Anyone else have crash reports for Flurry interstitials?


#1

I use Flurry exclusively through mediation so that means I have zero Flurry code of my own.

Every time I enable Flurry interstitials, I start getting these crash reports on crashlytics. I have never reproduced them myself. Flurry claimed it was my fault but no other ad network gives me that issue, I have zero Flurry code of my own, I have tried several versions and recently I tried out AdMob mediation and the crash happened there as well.

This is the stack trace:

Fatal Exception: android.view.ViewRootImpl$CalledFromWrongThreadException: Only the original thread that created a view hierarchy can touch its views.

   at android.view.ViewRootImpl.checkThread(ViewRootImpl.java:7901)

   at android.view.ViewRootImpl.requestLayout(ViewRootImpl.java:1322)

   at android.view.View.requestLayout(View.java:21049)

   at android.view.View.requestLayout(View.java:21049)

   at android.view.View.requestLayout(View.java:21049)

   at android.view.View.requestLayout(View.java:21049)

   at android.view.View.requestLayout(View.java:21049)

   at android.widget.RelativeLayout.requestLayout(RelativeLayout.java:360)

   at android.view.View.requestLayout(View.java:21049)

   at android.widget.TextView.checkForRelayout(TextView.java:8621)

   at android.widget.TextView.setText(TextView.java:5131)

   at android.widget.TextView.setText(TextView.java:4956)

   at android.widget.TextView.setText(TextView.java:4931)

   at com.flurry.sdk.hq$2.run(SourceFile:123)

   at android.os.Handler.handleCallback(Handler.java:751)

   at android.os.Handler.dispatchMessage(Handler.java:95)

   at android.os.Looper.loop(Looper.java:154)

   at android.app.ActivityThread.main(ActivityThread.java:6776)

   at java.lang.reflect.Method.invoke(Method.java)

   at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1518)

   at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1408)

Anyone else get that?


#2

Hi!
If this is still an issue for you, can you reach out to support@mopub.com and facilitate the following:

Number of observed app crashes/frequency of the crashes: (e.g 5 crashes in 500 ad requests et al)
MoPub SDK version:
Flurry SDK / adapters version:
Ad unit ID associated with the crash:
Steps to replicate the crash:
Shareable Crashlytics link:

Many thanks!


#3

I stopped using Flurry interstitials because of this issue. The issue isn’t with MoPub because I have the exact same crash if I use AdMob mediation with Flurry.

All I am curious about is whether other people see this crash since Flurry claims it is an issue on my end but I doubt that since it happens with AdMob mediation as well as MoPub mediation and on neither case do I have any of my own code for Flurry.