Mobile SDKs

Hi Intercom Team,We are currently integrating the Intercom SDK into our application and have encountered the following three issues that are affecting the user experience:1. Partial Language Update via updateUser Issue: When calling Intercom.updateUser({ languageOverride: Language }) to switch the UI language, the change is inconsistent. Sometimes only a portion of the Intercom UI updates, while other elements remain in the previous language.     Workaround: A full and correct language switch only occurs after calling Intercom.logout() and re-initializing, which is not ideal for user experience. Expected Behavior: The entire Intercom UI should refresh to the target language immediately upon calling updateUser. 2. Android: Messages Not Appearing After Sending Issue: On Android devices, when a user sends a message, the message bubble occasionally fails to appear in the chat interface immediately. Details: The user has to exit the conversation screen and re-enter the chat to see the

We’re presenting Intercom articles with Intercom.presentContent(content) . Everything was working well in version 8.8.0 but after bumping to 9.x, the close button at the top article header is broken in iOS and doesn’t respond to taps. The only way to close the article is to drag the overlay down (which is something that might not be obvious for every user). It is working correctly on Android.

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. 

Hi, we tried to integrate the voice transcription feature in our iOS application but we encountered an issue with the SDK. We have a HTTP Error: 401 unauthorized, with message “Tried to transcribe audio but there was a network error”All other features (message, document, photos) work correctly and our Android version succeed to use voice transcription.We check this list and seems ok in our side : Verify iOS preprod Identity Verification secret in Intercom dashboard (Security Settings → Identity Verification → iOS → Preprod) Ensure backend generates ios_user_hash with correct iOS preprod secret Upgrade Intercom SDK to latest version both apps Add NSSpeechRecognitionUsageDescription permission in Info.plist files Ensure setUserHash is called before any other Intercom methodI extract the intercom log : [Intercom] Push Notifications Handler: AUTO[Intercom] INFO - Checking if user identity matches existing identity.[Intercom] INFO - User identity matches existing identity.[Intercom] INFO -

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?

Hello community, I am responsible for a project that requires a technical expert. I am seeking out a qualified professional to assist with implementation efforts. We are looking for a developer with technical proficiency in the Intercom SDK. This is for a defined scope of work to support a critical business function. The project has defined deliverables and milestones. I welcome all inquiries and recommendations.

Android API 36 is ignoring the orientation configuration. The Android SDK is fixing the orientation as portrait. We have got the following warning on Google Play: From Android 16, Android will ignore resizability and orientation restrictions for large screen devices, such as foldables and tablets. This may lead to layout and usability issues for your users.We detected the following resizability and orientation restrictions in your app:<activity android:name="io.intercom.android.sdk.activities.IntercomCarouselActivity" android:screenOrientation="PORTRAIT" />To improve the user experience for your app, remove these restrictions and check that your app layouts work on various screen sizes and orientations by testing on Android 16 and below.Would it be possible to avoid orientation restrictions in the SDK?

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.

I want to report an issue we have encountered with the Intercom SDK on Android. When a user attempts to open a password-protected PDF sent by the support team, the application crashes with the following error:Fatal Exception: java.lang.SecurityException: password required or incorrect password       at android.graphics.pdf.PdfRenderer.nativeCreate(PdfRenderer.java)       at android.graphics.pdf.PdfRenderer.<init>(PdfRenderer.java:172)       at io.intercom.android.sdk.ui.preview.ui.PreviewUriKt$loadFilesAsBitmaps$1.invokeSuspend(PreviewUri.kt:269)       at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)       at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:104)       at androidx.compose.ui.platform.AndroidUiDispatcher.performTrampolineDispatch(AndroidUiDispatcher.android.kt:81)       at androidx.compose.ui.platform.AndroidUiDispatcher.access$setScheduledFrameDispatch$p(AndroidUiDispatcher.android.kt:41)       at androidx.compose.ui

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 Re-adding the Intercom package Confirmed same SDK version (19.2.1) Still, the issue reappears randomly on some environments  ObservationWhen we “Jump to Definition,” for working setups i

I own an iOS application that supports Teacher - student lessons. So I need a 1:1 chat where the student can be connected directly with the teacher and the teacher will only see their open chats with students that have started conversations with them. I did some quick prototyping on iOS and I see I can pretty easily set it up where the student can open up a global message queue (Messages Space) but how can I limit their scope to a particular conversation? Is that available in the iOS SDK or will I have to reach for some admin routes? 

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.

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

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’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:  This is urgent for us as Intercom provides a critical piece of functionality that our customers rely on to report issues and get customer support.Please can this be fixed as quickly as possible as we are blocked from releasing new version of our app without this.

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?

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.

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?

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.

We’re creating the intercom user account from the backend when a new user signs up in our systems. We set up the account with the email ID, name, and mobile number, but not the user ID. [We wanted to keep the email as the single source of truth.]When the user logs in to our mobile app (iOS and Android), we use the same email ID to log in to the intercom using the identified user login option (without a user ID).However, instead of identifying the existing account and logging in, it creates a new account again. Earlier, we faced similar issues with duplicate accounts because a few intercom accounts from the mobile app had logged in with the user ID and email. That created new accounts in the intercom. We resolved this by permanently deleting those accounts and now only using the email ID to log in. But even with this change, the mobile SDK is unable to identify the user and instead creates a new duplicate account again. Could you help me understand the issue better and suggest the right

Bug Report: Android crash due to setNeedsStatusBarAppearanceUpdate in @intercom/intercom-react-nativePackage: @intercom/intercom-react-nativeVersion: 9.2.0React Native: (e.g. 0.81.0)Platform: AndroidReact Native CLIDescription  The Android build crashes on startup due to a null reference to the property setNeedsStatusBarAppearanceUpdate in IntercomModule. Additional Notes Crash reproducible in RN 0.81.0  Occurs on both emulators and physical Android devices. Works fine on iOS. Cleaning android/build or reinstalling pods does not resolve it. Everything worked as expected when I had intercom version 8.8.0