firebase-android-sdk: NullPointerException at AbtIntegrationHelper.setExperimentActive

[REQUIRED] Step 2: Describe your environment

  • Android Studio version: Android Studio Electric Eel | 2022.1.1 Patch 1
  • Firebase Component: In-App Messaging
  • Component version: 20.3.0

[REQUIRED] Step 3: Describe the problem

Steps to reproduce:

I can’t reproduce. Please take a look at the log and screenshot from Firebase Crashlytics

Caused by java.lang.NullPointerException: Attempt to invoke interface method 'void java.util.concurrent.Executor.execute(java.lang.Runnable)' on a null object reference
       at com.google.firebase.inappmessaging.internal.AbtIntegrationHelper.setExperimentActive(AbtIntegrationHelper.java:94)
       at com.google.firebase.inappmessaging.internal.InAppMessageStreamManager.triggeredInAppMessage(InAppMessageStreamManager.java:363)
       at com.google.firebase.inappmessaging.internal.InAppMessageStreamManager.lambda$getTriggeredInAppMessageMaybe$27(InAppMessageStreamManager.java:346)
       at com.google.firebase.inappmessaging.internal.InAppMessageStreamManager.$r8$lambda$w4tUspl0-bTh48AvRyCAZ0a1mSM(InAppMessageStreamManager.java)
       at com.google.firebase.inappmessaging.internal.InAppMessageStreamManager$$InternalSyntheticLambda$1$4b09f0da19d4914563fbc47a8eb385ca850290e0e2e34b6d79e30263981ca83c$3.apply(InAppMessageStreamManager.java:6)
       at io.reactivex.internal.operators.maybe.MaybeFlatten$FlatMapMaybeObserver.onSuccess(MaybeFlatten.java:88)
       at io.reactivex.internal.operators.flowable.FlowableElementAtMaybe$ElementAtSubscriber.onNext(FlowableElementAtMaybe.java:80)
       at io.reactivex.internal.operators.flowable.FlowableFlattenIterable$FlattenIterableSubscriber.drain(FlowableFlattenIterable.java:312)
       at io.reactivex.internal.operators.flowable.FlowableFlattenIterable$FlattenIterableSubscriber.onNext(FlowableFlattenIterable.java:174)
       at io.reactivex.internal.operators.flowable.FlowableMap$MapSubscriber.onNext(FlowableMap.java:56)
image

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Reactions: 7
  • Comments: 17 (8 by maintainers)

Most upvoted comments

The same issue here, almost 60k users crashing 💣

Sorry for the radio silence here. Really appreciate the updates, @OlehHaidaienko. I was able to reproduce the same behavior from your steps to reproduce the issue. I’ll bring this up to our engineers and see what we can do here.

Hi all, this fix is now release on Firebase BoM version 32.0.0 or In-App Messaging version 20.3.2. You may check out the release notes for more information. I’ll close this issue now. Thanks!

Fix merged. Will be available in next release.

Hi all, a fix is on the way #4913. Thank you for your patience.

I’m having the same issue 😦

Hey @OlehHaidaienko, sorry for the radio silence here. We’re still investigating this. Thanks for the extra details.

Here are some of my findings:

  • Changes made between versions 20.1.2 to 20.2.0 is during the commit dates between Mar. 10, 2022 - Oct. 12, 2022.
  • History of commits for firebase-inappmessaging shows around 10-11 commits during this timeline (Mar - Oct 2022).
  • All commits in the given timeline doesn’t seem to have any changes made to the AbtIntegrationHelper and InAppMessageStreamManager

We’ll reply back here once once we get some further updates.