Attempt to invoke virtual method 'com.google.firebase.inappmessaging.model.MessageType com.google.firebase.inappmessaging.model.InAppMessage.getMessageType()' on a null object reference

[zhaiyunbin]

[REQUIRED] Step 2: Describe your environment

• Android Studio version: 4.1.2
• Firebase Component: inappMessaging
• Component version: 20.1.2

[REQUIRED] Step 3: Describe the problem

Steps to reproduce:

firebase crash

Relevant Code:

Fatal Exception: java.lang.NullPointerException: Attempt to invoke virtual method 'com.google.firebase.inappmessaging.model.MessageType com.google.firebase.inappmessaging.model.InAppMessage.getMessageType()' on a null object reference
       at com.google.firebase.inappmessaging.display.FirebaseInAppMessagingDisplay.extractActions(FirebaseInAppMessagingDisplay.java:438)
       at com.google.firebase.inappmessaging.display.FirebaseInAppMessagingDisplay.inflateBinding(FirebaseInAppMessagingDisplay.java:309)
       at com.google.firebase.inappmessaging.display.FirebaseInAppMessagingDisplay.access$000(FirebaseInAppMessagingDisplay.java:79)
       at com.google.firebase.inappmessaging.display.FirebaseInAppMessagingDisplay$1.run(FirebaseInAppMessagingDisplay.java:287)
       at android.os.Handler.handleCallback(Handler.java:938)
       at android.os.Handler.dispatchMessage(Handler.java:99)
       at android.os.Looper.loop(Looper.java:257)
       at android.app.ActivityThread.main(ActivityThread.java:8192)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:626)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1015)

[google-oss-bot]

I found a few problems with this issue:

• I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
• This issue does not seem to follow the issue template. Make sure you provide all the required information.

[argzdev]

Hi @zhaiyunbin, thanks for reporting. Could you provide steps how to reproduce this issue? If you could also provide a minimal repro of the issue, that'll greatly help us in our investigation. Thanks!

[zhaiyunbin]

``> Hi @zhaiyunbin, thanks for reporting. Could you provide steps how to reproduce this issue? If you could also provide a minimal repro of the issue, that'll greatly help us in our investigation. Thanks!

I just add firebase related dependencies ,The in-appmessage message was sent in the firebase console and then the error was found in carsh.

    //firebase 
    implementation platform('com.google.firebase:firebase-bom:29.2.0')
    implementation 'com.google.firebase:firebase-crashlytics'
    implementation 'com.google.firebase:firebase-analytics'
    implementation 'com.google.firebase:firebase-perf'
    implementation 'com.google.firebase:firebase-messaging'
    implementation 'com.google.firebase:firebase-inappmessaging-display'
    //ads
    implementation 'com.google.android.gms:play-services-ads:20.5.0'
    implementation 'com.google.android.gms:play-services-auth:19.2.0'
    //pay
    implementation "com.android.billingclient:billing:4.0.0"

[argzdev]

Hi @zhaiyunbin, I'm unable to reproduce this issue. Could you answer some details below:

1. Could you reproduce this issue? If yes, could you provide a minimal repro?
2. Is this issue persistent? In what Android version are you able to reproduce this issue?
3. Looking in the code, it seems that the error InAppMessage.getMessageType() is related to the InAppMessage layout. What option did you select in the Firebase InAppMessage Console?

Thanks!

[zhaiyunbin]

• Could you reproduce this issue? If yes, could you provide a minimal repro?
• Is this issue persistent? In what Android version are you able to reproduce this issue?
• Looking in the code, it seems that the error InAppMessage.getMessageType() is related to the InAppMessage layout. What option did you select in the Firebase InAppMessage Console?

This message has been deleted，I don't have any more information either...Just remember that the type is Top banner

[argzdev]

Hi @zhaiyunbin, unfortunately I'm unable to reproduce the issue even with a top banner. Given that the issue is difficult to reproduce, I'm unable to investigate this further. If you could provide more details, it'll greatly help us out. However, I'll close this for now, since there's no way of moving forward. Feel free to reopen once you have more details. Thanks!