[Android] App crashing on 16.0.0 | Community
Skip to main content
Answered

[Android] App crashing on 16.0.0

  • May 22, 2025
  • 1 reply
  • 146 views

Hello, we've recently updated our SDK to the latest version (16.0.0) and we've been seeing a few crashes in production related to the in app notification. This seems to happen when showing the Full notification, as there seems to be something missing in the layout that intercom uses internally. We've just bumped to the latest version, but looking at the code, that doesn't seem to solve this particular issue.

This is the stack trace we're getting:

Fatal Exception: java.lang.NullPointerException
Parameter specified as non-null is null: method io.intercom.android.sdk.m5.notification.InAppNotificationCardKt.addInappNotificationCardToView, parameter composeView

io.intercom.android.sdk.m5.notification.InAppNotificationCardKt.addInappNotificationCardToView (InAppNotificationCard.kt:3)
io.intercom.android.sdk.overlay.ChatNotification.populateViewsWithData (ChatNotification.java:90)
io.intercom.android.sdk.overlay.ChatNotification.display (ChatNotification.java:64)
io.intercom.android.sdk.overlay.InAppNotificationPresenter.addNewNotifications (InAppNotificationPresenter.java:185)
io.intercom.android.sdk.overlay.InAppNotificationPresenter.displayNotificationsAfterAttach (InAppNotificationPresenter.java:91)
io.intercom.android.sdk.overlay.InAppNotificationPresenter$1.run (InAppNotificationPresenter.java:80)
io.intercom.android.sdk.utilities.ViewUtils$1.onGlobalLayout (ViewUtils.java:19)
android.view.ViewTreeObserver.dispatchOnGlobalLayout (ViewTreeObserver.java:1142)
android.view.ViewRootImpl.performTraversals (ViewRootImpl.java:4214)
android.view.ViewRootImpl.doTraversal (ViewRootImpl.java:3009)
android.view.ViewRootImpl$TraversalRunnable.run (ViewRootImpl.java:10514)
android.view.Choreographer$CallbackRecord.run (Choreographer.java:1566)
android.view.Choreographer$CallbackRecord.run (Choreographer.java:1575)
android.view.Choreographer.doCallbacks (Choreographer.java:1175)
android.view.Choreographer.doFrame (Choreographer.java:1104)
android.view.Choreographer$FrameDisplayEventReceiver.run (Choreographer.java:1549)
android.os.Handler.handleCallback (Handler.java:991)
android.os.Handler.dispatchMessage (Handler.java:102)
android.os.Looper.loopOnce (Looper.java:232)
android.os.Looper.loop (Looper.java:317)
android.app.ActivityThread.main (ActivityThread.java:8934)
java.lang.reflect.Method.invoke (Method.java)
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:591)
com.android.internal.os.ZygoteInit.main (ZygoteInit.java:911)

Could you investigate this, please? Let us know if you need any more information!

Best answer by Emilygav

Hey ​@Rodrigo Lessinger! Emily here from Support Engineering at Intercom 👋🏼

 

This was identified as a bug and fixed in the version 16.2.0 which you can find the changes for here.

However I would recommend updating to the latest version of the SDK which is our 16.3.0 version 😎

 

Updating your version should solve your problem!

1 reply

Emilygav
Intercom Team
Forum|alt.badge.img+6
  • Intercom Team
  • Answer
  • June 13, 2025

Hey ​@Rodrigo Lessinger! Emily here from Support Engineering at Intercom 👋🏼

 

This was identified as a bug and fixed in the version 16.2.0 which you can find the changes for here.

However I would recommend updating to the latest version of the SDK which is our 16.3.0 version 😎

 

Updating your version should solve your problem!