NullPointerException at AbtIntegrationHelper.setExperimentActive

[OlehHaidaienko]

[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)

[google-oss-bot]

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

[igoralvess]

I'm having the same issue :(

[hallefy]

The same issue here, almost 60k users crashing 💣

[argzdev]

Hi all, did you happen to use an earlier version prior to encountering this problem? Would it be possible for you to provide us with the previous version that was working?

However, if there were no changes made to the version before the problem occurred, it's possible that the issue is related to the backend. In that case, please reach out to our Firebase support team. They can assist you better since you'll be able to share project details and campaign configurations.

[OlehHaidaienko]

@argzdev Hi, we have this crash only in the latest versions of the app where we updated Firebase BoM from 29.2.0 to 31.1.1. As I see the In-App Message was updated from 20.1.2 to 20.2.0

[OlehHaidaienko]

@argzdev HI, after monitoring this issue for a while I can confirm that it appears only in versions where Firebase BoM was updated.
We're gonna update BoM to 31.2.3 and will check if the crash still exists

[argzdev]

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.

[OlehHaidaienko]

Hi @argzdev
We started rolling out a new app version with updated Firebase BoM 31.2.3 but the issue still exists
Currently, 16k crash events affecting ~2.7k users.
I could provide some extra logs if you need

[argzdev]

Hi guys, we're still investigating this. Any chance you could share with us the setup of your campaign. Please do remove any PII (personal identifiable information) if needed. This might give us an idea what's causing the issue.

Yes, those extra logs will be helpful, @OlehHaidaienko. Thanks!