iOS SDK Release 19.3.2 | Community
Skip to main content

iOS SDK Release 19.3.2

  • November 4, 2025
  • 3 replies
  • 141 views
Brian B11
Intercom Team
Forum|alt.badge.img+2
Release Date: 04-11-2025

🐛 Bug Fixes

  • Fixed an issue where tapping the close button on an article in a conversation would not dismiss the article.
  • Fixed an issue where tapping on a link in an article would not open the link.
  • Fixed an issue where carousels were not dismissing correctly.
  • Fixed an issue where reactions to articles were not being handled correctly.

November 12, 2025

​@Matias Tebele  Hi 👋

Sorry you had to encounter that crash.


We’ve identified the root cause and fixed the issue — we’ve fixed this in the latest release of react native released here.

 

Just for context, this happened because we introduced a new dependency called Ably, which was pulling in some transitive dependencies that weren’t building correctly. We’ve since updated our build scripts to ensure Ably is properly included.

 

Could you please try again with the latest version of Intercom to see if that resolves the problem?

 

One quick note : the version you’re currently using (8.5.0) shouldn’t actually be interacting with Ably, so it’s a bit odd that you’re seeing this issue. It might be that a newer version was pulled in unintentionally. Either way, the fix is now in the latest release, so updating should sort it out.

Thanks! 

 

Hi Raj, thanks for the response and for the fix.

I solved it adding the following to my proguard-rules.pro file:

-keep class io.ably.** { *; }
-dontwarn io.ably.**
-keep class org.msgpack.** { *; }
-dontwarn org.msgpack.**
-keepclassmembers class * {
    @org.msgpack.** <fields>;
    @org.msgpack.** <methods>;
}

Thanks,

3 replies

M
Forum|alt.badge.img+1
Release Date: 04-11-2025

🐛 Bug Fixes

  • Fixed an issue where tapping the close button on an article in a conversation would not dismiss the article.
  • Fixed an issue where tapping on a link in an article would not open the link.
  • Fixed an issue where carousels were not dismissing correctly.
  • Fixed an issue where reactions to articles were not being handled correctly.

Hi ​@Brian B11 ,

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

R
Employee
  • Raj SEmployee
  • Employee
  • November 12, 2025

​@Matias Tebele  Hi 👋

Sorry you had to encounter that crash.


We’ve identified the root cause and fixed the issue — we’ve fixed this in the latest release of react native released here.

 

Just for context, this happened because we introduced a new dependency called Ably, which was pulling in some transitive dependencies that weren’t building correctly. We’ve since updated our build scripts to ensure Ably is properly included.

 

Could you please try again with the latest version of Intercom to see if that resolves the problem?

 

One quick note : the version you’re currently using (8.5.0) shouldn’t actually be interacting with Ably, so it’s a bit odd that you’re seeing this issue. It might be that a newer version was pulled in unintentionally. Either way, the fix is now in the latest release, so updating should sort it out.

Thanks! 

M
Forum|alt.badge.img+1

​@Matias Tebele  Hi 👋

Sorry you had to encounter that crash.


We’ve identified the root cause and fixed the issue — we’ve fixed this in the latest release of react native released here.

 

Just for context, this happened because we introduced a new dependency called Ably, which was pulling in some transitive dependencies that weren’t building correctly. We’ve since updated our build scripts to ensure Ably is properly included.

 

Could you please try again with the latest version of Intercom to see if that resolves the problem?

 

One quick note : the version you’re currently using (8.5.0) shouldn’t actually be interacting with Ably, so it’s a bit odd that you’re seeing this issue. It might be that a newer version was pulled in unintentionally. Either way, the fix is now in the latest release, so updating should sort it out.

Thanks! 

 

Hi Raj, thanks for the response and for the fix.

I solved it adding the following to my proguard-rules.pro file:

-keep class io.ably.** { *; }
-dontwarn io.ably.**
-keep class org.msgpack.** { *; }
-dontwarn org.msgpack.**
-keepclassmembers class * {
    @org.msgpack.** <fields>;
    @org.msgpack.** <methods>;
}

Thanks,

    Terms & ConditionsAccessibility statement