"Emerging Bad Behavior" Warning from Play Console

Scripture App Builder
1

I am wondering if anyone else has gotten this warning:

PlayConsole-EmergingBadBehavior
PlayConsole-EmergingBadBehavior701×534 30.6 KB

I have now received an email for two of the apps I manage. The subject line of the email is “Android vitals bad behavior for [App Name]”, and the picture above is the entire contents of the email.

When I go into the Android Vitals tab of the Play Console, it gives me a lot of data that I don’t understand, but here are the issues it shows for one app:

image
image543×784 15.9 KB

and for the other app:

image
image771×526 30.1 KB

I’m not sure if it’s relevant, but these two apps both use FCBH audio and analytics. Both use Verse of the Day and Daily Reminder. Both have embedded YouTube videos (one only Lumo, the other Lumo and Jesus Film).

I have one other app that shares all of those things in common. I have not received this email for that one yet, but when I go to the Android Vitals tab, it is giving me a similar “bad behavior” message, and here are the stats for that one:

image
image536×443 24.7 KB

None of the other apps I manage are having a similar issue. However, in addition to not using these features, the remaining apps also have far fewer installed users…400 or less, versus 4,000+ for all of the apps I’m having issues with.

I appreciate any insight you can provide on this,
Matt A

2

I’m also experiencing a similar problem and when I look at the issues detail , there is an IllegalStateException in the fragment manager.

Exception java.lang.IllegalStateException: Must be called from main thread of fragment host
  at androidx.fragment.app.FragmentManager.ensureExecReady (Unknown Source:72)
  at androidx.fragment.app.FragmentManager.execPendingActions (Unknown Source)
  at androidx.fragment.app.FragmentManager.executePendingTransactions (Unknown Source:1)
  at q1.e.N2 (SourceFile:1)
  at t1.d.h0 (SourceFile:1)
  at d2.g.L3 (SourceFile:1)
  at d2.g$p0.f (SourceFile:1)
  at b2.f$e.b (SourceFile:1)
  at b2.f$e.run (SourceFile:1)
  at java.lang.Thread.run (Thread.java:1012)
3

The Kalaam team is getting lots and lots of these too. I have not had time to look into it but the little review done shows there is not one particular reason for all the messages we’ve received. I hope the SAB developers are able to offer some insight as soon as possible.