Mobile SDKs

We are experiencing an issue with the Intercom Android Mobile SDK. The issue is that the in-app message notifications appear underneath the navigation bar at the bottom of the screen, as opposed to sitting directly above the navigation icons.Our app currently uses the SDK version 17.1.1 – however we have been able to reproduce the issue even on the latest version of the SDK (17.3.0). The release notes for 17.2.0 indicate the issue was resolved.  Upon further investigation, it appears the issue stems from the fact our app still uses AppCompatActivity as our base Activity, instead of ComponentActivity which is what the sample app uses. I tested this theory but switching the ComponentActivity to an AppCompatActivity in the sample app and the bug was surfaced there as well. As it would not be trivial for us to switch our base Activity to ComponentActivity, I'm wondering if there are any further solutions currently being worked on for the next release of the Intercom SDK that would resolve

Hi Intercom Team,After updating our app to Intercom iOS SDK 19.3.2, several developers on our team have encountered issues where Swift methods (e.g. loginUser(with:), logout(), etc.) are no longer properly inferred or recognized by the compiler.Details Integration: Swift Package Manager (official intercom-ios-sp repo) Project Type: Pure Swift (no Objective-C bridging) Issue:  Xcode only exposes the Objective-C versions of the APIs (e.g. loginUserWithUserAttributes:success:failure:). Error Messages: “Cannot infer type of function call” “No exact matches in call to function 'loginUser'” Troubleshooting Tried Cleared DerivedData and SPM caches Removed and re-added the Intercom package Could you please confirm: The officially supported Xcode versions for SDK 19.3.0? Whether there’s a known issue or upcoming patch related to this Swift interface mismatch when using SPM?

When updating to io.intercom.android:intercom-sdk version 17.2.0If R8/Proguard is enabled the following error occurs on the build:Missing class lombok.Generated (referenced from: io.ably.lib.network.HttpBody io.ably.lib.network.HttpResponse$HttpResponseBuilder.body and 94 other contexts) This does not happen on version 17.1.1  It looks like maybe something changed in the build but didn’t include a rule in it’s consumer-rules.pro?  gemini says: -dontwarn lombok.** may fix it?

Hi Intercom team, we receive several errors after trying to login a user with attributes using react-native sdk.We check if the user is logged in before making a Intercom.loginUserWithUserAttributes call.A short stack-trace for the error we receive: code: 102,domain: io.intercom.ios.error.network,message: Error in loginUserWithUserAttributes,name: Error,NSLocalizedDescription: HTTP Error: 400 bad requestWe send email and userId to the method call, like this: Intercom.loginUserWithUserAttributes({ email, userId }) Could you help us understand why we still get an error, I’ve run a console.log for both email and userId and both seem legit.

Hi,I’ve found an issue with the in-app message preview on Android where the actual message content is not visible, I assume because the text color matches the background color.You can see this issue replicated in your expo-example app from https://github.com/intercom/intercom-react-native/tree/main/examples/expo-example in the screenshot below.I can’t find anything obvious on the Native Android app settings that is causing this issue, so perhaps there is a styling issue in the Intercom SDK?Thanks for your help  

Hey! I’m facing an issue with intercom-sdk version 17.2.0.The in-app message doesn’t display any message text when it’s a new message in an existing conversation. I’ve attached a Layout Inspector screenshot for more details.Compose version in the app: composeBom = "2025.09.01"  At the same time, if you start a new conversation from the Intercom web interface, the very first message is visible in the app — but from the second message onward, it disappears again. 

I am using Intercom.presentMessageComposer(initialMessage) to show Intercom with a pre-filled message in my React Native app like this:await Intercom.presentMessageComposer(‘An initial message.’);I’m using this version: "@intercom/intercom-react-native": "^9.3.2"This launches the Intercom messenger on iOS with pre-filled message.On Android, this launches the Intercom messenger but there’s no pre-filled message. Also the message input is not visible on Android.Is this an expected behavior on Android or is it a bug?

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.

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.MessageBufferUThe 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:Why did the crash start happening all of a sudden? Why is it not mentioned in the documentation that we need to keep org.msgpack classes unobfuscated? How can we be sure to prevent similar crashes from happening ever again? Thank you

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.

Can I please have a code sample on how to implement dark mode (or switch themes) for Android. E.g. something likeimport io.intercom.android.sdk.ui.theme.ThemeMode;Intercom.client().setThemeMode(ThemeMode.DARK);I noted that Dark Mode was enabled on Android SDK v17.0.0

We are having issues when using presentContent for presenting an article, the close button does not close the modal, though it can be closed with a drag down.any workaround?

On the intercom landing page, we have some pinned articles. If you open the pinned article, and try to tap the "X" button, it will not close the article. However, swiping down will still allow you to close that article. This behavior only occurs on iOS - it does not occur on Android.Some notes:If you go from the landing page and select the "Help" to go to the collection of articles (rather than the pinned article on the landing page), then those articles CAN be closed via the "X" button. This behavior occurred on the latest react native SDK version, 19.1.2 We checked and found we had to regress to 19.0.3 to resolve the problem - however we cannot use this older version, otherwise we will lose the iOS 26 changes.

When using `Intercom.presentContent(.article(id: articleId))` with the current version of the iOS SDK (19.3.0), the app presents an empty view for a second or two and then crashes after outputting the following.*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[IntercomSDKPrivate.ArticleHostingController setContentDelegate:]: unrecognized selector sent to instance 0x12aeec000'*** First throw call stack:(0x1863e28c8 0x1833597c4 0x18647e838 0x18cfb1484 0x18635f4f8 0x1863673a0 0x10915b2f4 0x18645dd64 0x10913e12c 0x10787c63c 0x1078962d0 0x1078b74c0 0x10788c778 0x10788c6b4 0x186384520 0x186336d14 0x186335c44 0x225726498 0x18bcb0ddc 0x18bc55b0c 0x18bd91860 0x10bad5448 0x10bad53bc 0x10bad7308 0x1833aee28)Exception received: NSInvalidArgumentException - -[IntercomSDKPrivate.ArticleHostingController setContentDelegate:]: unrecognized selector sent to instance 0x12aeec000 

Hello, We are currently using Intercom in our Expo React Native app for customer service messaging. We have previously been using Expo SDK 53 and React Native 0.79.5 with the react native intercom package 9.0.3 and all has been working well.However upgrading Intercom to 9.1.0 or higher is causing some very weird issues for us.Our app streams HLS video where the HLS playlist contains 10s chunks of video which is presented to the user as one long continuous clip. When scrubbing forward in the clip further than what’s been buffered the stream will obviously need to buffer. Our player is using the expo-video package, but we’ve tried with other packages as well such as react-native-video. Now to the issue; Intercom 9.1.0 and higher causes the app to crash when scrubbing forward quickly in the video stream, this problem is only present there and when downgrading Intercom to 9.0.3 it’s working fine again and I can scrub and pause/forward/rewind with no problem and the app is not crashing. I c

We are getting a great number of crashes on the Android version 14.1.0.This seems to happen to the conversation_list RecyclerView.You can find the stack trace bellow:java.lang.IllegalStateException: The specified child already has a parent. You must call removeView() on the child's parent first. at android.view.ViewGroup.addViewInner(ViewGroup.java:4471) at android.view.ViewGroup.addView(ViewGroup.java:4312) at android.view.ViewGroup.addView(ViewGroup.java:4252) at android.view.ViewGroup.addView(ViewGroup.java:4225) at androidx.compose.ui.viewinterop.AndroidViewHolder.setView$ui_release(AndroidViewHolder.android.kt:97) at androidx.compose.ui.viewinterop.ViewFactoryHolder.<init>(AndroidView.android.kt:332) at androidx.compose.ui.viewinterop.ViewFactoryHolder.<init>(AndroidView.android.kt:312) at androidx.compose.ui.viewinterop.AndroidView_androidKt$createAndroidViewNodeFactory$1.invoke(AndroidView.android.kt:247) at androidx.compose.ui.viewinterop.