Native Android SDK crash java.lang.ClassNotFoundException - org.msgpack.core.buffer.MessageBufferU | Community
Skip to main content
Question

Native Android SDK crash java.lang.ClassNotFoundException - org.msgpack.core.buffer.MessageBufferU

  • November 11, 2025
  • 3 replies
  • 114 views

All of sudden today our native Android crash started crashing whenever a user tried to access Intercom. This was the crash:

java.lang.ClassNotFoundException - org.msgpack.core.buffer.MessageBufferU

The crash only happened with builds obfuscated by ProGuard. The crash still happened even after adding the keep rules according to the documentation:

-keep class io.intercom.android.** { *; }
-keep class com.intercom.** { *; }

 

We solved the crash by adding the following to our proguard-rules.pro file: 

-keep class org.msgpack.** { *; }

I have a couple of questions:

  1. Why did the crash start happening all of a sudden?
  2. Why is it not mentioned in the documentation that we need to keep org.msgpack classes unobfuscated?
  3. How can we be sure to prevent similar crashes from happening ever again?

 

Thank you

3 replies

Forum|alt.badge.img
  • Connector
  • November 12, 2025

I’m seeing this crash in my app as well.


Forum|alt.badge.img
  • Connector
  • November 12, 2025

It appears that the latest SDK update fixes this:

Fixed ClassNotFoundException crash related to Ably integration

https://github.com/intercom/intercom-android/releases/tag/17.3.1


  • Author
  • New Participant
  • November 12, 2025

Thanks, we noticed the release and released a hotfix with the updated intercom version. It is horrible, however, that Intercom can suddenly start crashing like that out of nowhere. It would be great if there was a way to avoid anything similar from ever happening again - but I am not sure how, apart from not using Intercom.