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

Hello!Has anyone run into this error when using the Intercom Expo plugin (@intercom/intercom-react-native@9.1.1) with an app.config.ts setup?PluginError: Package "@intercom/intercom-react-native" does not contain a valid config plugin.Learn more: https://docs.expo.dev/guides/config-plugins/#creating-a-pluginUnexpected token 'typeof'SyntaxError: Unexpected token 'typeof' at compileSourceTextModule (node:internal/modules/esm/utils:344:16) at ModuleLoader.moduleStrategy (node:internal/modules/esm/translators:105:18) at ModuleLoader.#translate (node:internal/modules/esm/loader:534:12)Not sure if this is an issue with the way the plugin is authored or how Expo expects config plugins to behave in a .ts setup.Would appreciate any insight or workarounds others may have found!

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);a

We’re unable to safely download the Intercom iOS SDK to build with our application using Swift Package Manager. Adding the Intercom Package to our project on a clean SPM cache returns the following error:checksum of downloaded artifact of binary target 'Intercom' (83f26a63832df968d0279ecdd03d8e5039ebf9bb91a9e0b1783cf184101c5a82) does not match checksum specified by the manifest (b87d95eabe645523f417b9051c20151ca7720c93116b163435c2ce1e87aa65ac)fatalError There is a ‘patch’ raised by someone on a fork of the project, but as this is not an official fix by Intercom we do not consider this a safe approach to include your SDKThis looks very similar to an issue on your forum that was raised (and fixed) last year: 

Hi Intercom team,After updating our app to Intercom iOS SDK 19.2.1, several developers on our team started facing issues where Swift methods (like loginUser(with:), logout(), etc.) are no longer properly inferred or recognized by the compiler.Details Integration: Swift Package Manager (official repo intercom-ios-sp) Project type: Pure Swift (no Objective-C bridging) Issue: For some developers, Xcode shows only Objective-C versions of methods (e.g. loginUserWithUserAttributes:success:failure:). Error: Cannot infer type of function call or No exact matches in call to function 'loginUser' Behavior: Happens inconsistently across machines — some developers see the correct Swift interface and can compile fine, others cannot. We already tried: Clearing DerivedData & SPM caches

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

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 cr

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.