Yes.
Here is the crash from Crashlytics.
Fatal Exception: java.lang.NullPointerException
Attempt to read from field 'anywheresoftware.b4a.BA anywheresoftware.b4a.BA.processBA' on a null object reference
anywheresoftware.b4a.keywords.Common$13.run (Common.java:1688)
android.os.Handler.handleCallback (Handler.java:883)
android.os.Handler.dispatchMessage (Handler.java:100)
android.os.Looper.loop (Looper.java:214)
android.app.ActivityThread.main (ActivityThread.java:7697)
java.lang.reflect.Method.invoke (Method.java)
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:516)
com.android.internal.os.ZygoteInit.main (ZygoteInit.java:950)
It seems to happen when returning to a game to play again after the results are shown. I think I can probably narrow it down further by inserting more events with Firebase and/or Crashlytics logs. It's just odd that the error is not referencing the actual activity that it is running. MemoryFlow2 is a game activity. They get to the end of the game and it shows the results activity. Then they choose to play again and it returns to the game to play again (and crash happens). Of course, I try to run through the same set of screens with no crash on my device.
Here is an example of the logs in Crashlytics.