Intercom SDK Android Not Working, Crashing and Not Loading Everywhere | Community
Skip to main content

Intercom SDK Android Not Working, Crashing and Not Loading Everywhere

  • October 27, 2025
  • 3 replies
  • 37 views
Z

We are using Intercom React Native 7.1.0 (Intercom Android 15.8.+) with iOS working fine except for Android. and it keeps crashing.

“Something Went Wrong”

“Content Cannot Be Loaded”

This has been happening for a long time, this doesn’t happen on iOS or the Web.

I have tried this solution:

We already have this option enabled, and still doesn’t work.

I don’t know what is causing this issue as we already have loginUserWithAttributes() in our app and iOS is not breaking with this error message either.

We use it like this in our code:

await Intercom.setUserHash(user_hash);

await Intercom.loginUserWithUserAttributes({
     email: user_email,
      userId: uid,
});

We want to support lower versions of users on iOS and Android so upgrading is a not an option.

Is there a way we can resolve this.

3 replies

Z
  • zackgao
  • Author
  • New Participant
  • 2 replies
  • November 5, 2025

Can anyone help?

M
Forum|alt.badge.img
  • Matias Tebele
  • Connector
  • 8 replies
  • November 6, 2025

We have our React Native app on production using v8.5.0. Since two days ago (the exact date you released v9.3.2), it's been crashing on Android when users open the Intercom screen, with the following error:

Caused by java.lang.RuntimeException
java.lang.ClassNotFoundException: org.msgpack.core.buffer.MessageBufferU

It seems you broke something retroactively. I need your help, as the Intercom support on our production app has stopped working suddenly.

Thanks

Z
  • zackgao
  • Author
  • New Participant
  • 2 replies
  • November 8, 2025

​@Matias Tebele  I don’t know if this is the same thing as us but Intercom on Android is completely broken and is now a non functioning product / SDK.

 

We didn’t change anything on our side and everything on Android just started breaking with “Something Went Wrong”

 

​@Matias Tebele Are you seeing the same message? as I am?

 

Please take a look at this: ​@Paul D ​@Jacques Reynolds 


Terms & ConditionsAccessibility statement