Popular Topics

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 

Im trying to install the Messenger app in Salesforce Community. I found this old article but it seems incomplete.  Im wondering if I could get help with this integration.  I Edit the Head Markup in the Salesforce Community with the pre-filled script.Then in a lightning component I tried to Instantiate the Intercom instance:import { LightningElement, api } from 'lwc';export default class IntercomApp extends LightningElement { connectedCallback() { try { window.intercomSettings = { api_base: 'https://api-iam.intercom.io', app_id: 'my-app-id-here' }; } catch (error) { console.error(error); } }}I get this warning:frame-modern.812d2c17.js:1 [Intercom] The App ID in your code snippet has not been set. Set it to your App ID found in settings to complete installation: https://app.intercom.com/a/apps/_/settings/web With this message below:[Intercom] Launcher is disabled in settings or current page does not ma

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

When I pull down an example line in the body via API I get something like this:\n<p class=\"no-margin\"></p>\n<p class=\"no-margin\"><b>Can I add in other activities?</b></p>\n<p class=\"no-margin\">Not at this time. If this is a feature you would like, please send us a message.</p>When I push that back up, it adds a new line to below the bolded text. This is also happening above lists as well, but only when it’s below a <p> class.The output looks like this:<b>Can I add in other activities?<b/>Not at this time. If this is a feature you would like, please send us a message.Where the intended output should be<b>Can I add in other activities?</b>Not at this time. If this is a feature you would like, please send us a message.Is this a bug? Is there a way around this?

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

The 19.3.0 release introduced a bug where opening articles could sometimes crash, reported here. That was fixed in 19.3.1, but at the same time or possibly earlier, it seems another issue was introduced and the articles now aren’t loading at all.When calling Intercom.presentContent(.article(id: “123456”)), while the app no longer crashes, I’m instead stuck on a blank screen that can’t be dismissed.The close button on that page also does not do anything. I believe this bug was introduced with version 19.2.0. It has already been reported multiple times, but seemingly with little response, here and here.

We are seeing quite a few crashes for the latest Intercom SDK. Older SDKs do not crash.  OS Version: iOS 26.0.1 (23A355)Report Version: 104Exception Type: EXC_BREAKPOINT (SIGTRAP)Exception Codes: 0 at 0x00000001077393e8Crashed Thread: 0Application Specific Information:Exception 6, Code 1, Subcode 4419982312Thread 0 Crashed:0   Intercom                        0x1077393e8         ListBlockView.configure1   Intercom                        0x107738d40         ListBlockView.init2   Intercom                        0x10773f1c0         closure in BlockViewFactory.getViewsForBlocks3   Intercom                        0x10773efc4         BlockViewFactory.getViewsForBlocks4   Intercom                        0x1077432cc         BlockPartView.addBlocks5   Intercom                        0x107744a3c         BlockPartView.configureLayout6   Intercom                        0x10774ec1c         PartViewFactory.getView7   Intercom                        0x107754034         ConversationCellViewFactory.getV

Hi!I’m new to Intercom and Workflows. I’m a French speaker, so apologies if some of the wording isn’t perfect.We use Intercom to communicate with professionals using our AI tool for healthcare.To improve efficiency, we created a Workflow that automatically generates tickets depending on the issue type.I looked into the “Auto-close incomplete Workflow conversations” option, but it doesn’t work in our case, since most of our Workflows end with a ticket.I also considered using the “When the customer doesn’t respond” trigger, but that doesn’t help either—because it’s the bot (not a human) interacting with the user.And most importantly: I don’t want conversations to close automatically when the Workflow ends, because our goal is to continue helping the client if they still need support.Fin suggested I try using tags inside the Workflow to trigger auto-close only in specific cases.So I was thinking: what if I add a tag like “not_finished” while the Workflow is still in progress, and then swi

Hello everyone.I'm experiencing an MQRC 2035 (Authorization) error when integrating Intercom with our messaging queue system. The setup involves deploying an application with MQ Client Connection Properties, specifying all necessary details.While trying to resolve the issue, I reached out to RabbitMQ support to ensure our configurations were correct. Despite Intercom running as the root user and the queue manager using default mqm users, the connection still fails. The error message indicates a failure to connect to the queue manager on the specified hostname and port.Has anyone encountered this issue while integrating Intercom with a messaging queue? What steps did you take to resolve it?Any insights or suggestions would be greatly appreciated.

Looking for an experienced consultant to help build and optimize Intercom chatbot solutions for customer support automation and lead generation. Need expertise in conversational AI design and Intercom platform integration.Requirements:Experience with Intercom's Resolution Bot and Custom Actions for automated customer interactions Knowledge of conversation flows, intent recognition, and fallback scenarios for complex customer queries Understanding of Intercom's Messenger integration, help desk workflows, and CRM data synchronization Ability to design multilingual chatbots with personalization and user segmentation Familiarity with Intercom's API for custom integrations and third-party tool connectionsRemote work preferred. Please share relevant Intercom chatbot implementation experience and approach to conversational AI optimization.

Hey, im currently creating an Chatbot Workflow. My maingoal is to split the current workflow in 2 parts. I want to do this to clean it up a bit.The Workflow asks the User if hes a Customer or a driver and this is where i want to split it. Id like to have one workflow for customers and one for Drivers.Any Ideas on how to implement this?You can see the current Workflow on the attached picture. 

We were able to go on Phone queue but whenever we receive calls , agents cant be heard. All headset and sound setup were working fine. tried basic t/s but issue persists.

Since the upgrade to 9.*.* of version for React Native Intercom (https://github.com/intercom/intercom-react-native), we can no longer build and compile our Expo React Native app for iOS.Somehow the Intercom upgrade introduces a failure where C++ files are not correctly mapped during compiling. This is only when combined with other packages (in our case UserCentrics for RN).It is important to highlight that although other third party apps are involved, Intercom’s upgrade breaks the building process. Compiling fails with: 13 | 14 | #ifndef __cplusplus> 15 | #error This file must be compiled as Obj-C++. If you are importing it, you must change your file extension to .mm. | ^ This file must be compiled as Obj-C++. If you are importing it, you must change your file extension to .mm. 16 | #endif 17 | 18 | // Avoid multiple includes of IntercomReactNativeSpec symbolsand 'optional' file not found'tuple' file not found'utility' file not foundI’ve added a minimal reproducible

Hi, We are using Intercom's API in Europe and have been experiencing an outage in one of the endpoints since October 25th.It fails with error 504 IntercomException: API service is temporarily unavailable.The status page does not show any incidents https://www.intercomstatus.com/Do you experience any API outages?Thanks!

Fatal Exception: java.net.MalformedURLException: unknown protocol: content at java.net.URL.<init>(URL.java:608) at java.net.URL.<init>(URL.java:498) at java.net.URL.<init>(URL.java:447) at io.intercom.android.sdk.ui.preview.ui.PreviewUriKt$loadFilesAsBitmaps$1$1.invokeSuspend(PreviewUri.kt:252) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:101) at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:113) at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:89) at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:589) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:823) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:720) at kotlinx.coroutines.scheduling

Release Date: 28-10-2025 🐛 Bug Fixes Fixed a crash that could happen when opening articles from a conversation.

Fatal Exception: java.lang.NoSuchMethodError: No virtual method close()V in class Landroid/media/MediaMetadataRetriever; or its super classes (declaration of 'android.media.MediaMetadataRetriever' appears in /system/framework/framework.jar) at io.intercom.android.sdk.m5.conversation.utils.URIExtensionsKt.getVideoData(URIExtensions.kt:146) at io.intercom.android.sdk.m5.conversation.utils.URIExtensionsKt.getMediaData(URIExtensions.kt:51) at io.intercom.android.sdk.m5.conversation.ui.ConversationScreenKt.ConversationScreen$lambda$29(ConversationScreen.kt:286) at io.intercom.android.sdk.m5.conversation.ui.ConversationScreenKt.$r8$lambda$l4hfoRjJBkYl_jEYY6YWj7rurp4() at io.intercom.android.sdk.m5.conversation.ui.ConversationScreenKt$$ExternalSyntheticLambda2.invoke(D8$$SyntheticClass) at io.intercom.android.sdk.m5.conversation.ui.ConversationScreenKt$ConversationScreenContent$35.invoke$lambda$3$lambda$0(ConversationScreen.kt:572) at io.intercom.and

We are longtime users of Intercom’s API.  The majority of our requests to Intercom’s API succeed.  Here are examples of two payloads that consistently fail.{  "event_name": "new-feature-receive_this_response",  "created_at": 1761447241,  "user_id": "x12x227f8x4067cx7a5dx97x"} {  "event_name": "experiments-show_experiment",  "created_at": 1761447325,  "user_id": "x12x227f8x4067cx7a5dx97x",  "metadata": {    "label": "experiment_questions"  }} When they fail, Intercom’s API just returns a 422 with no additional details about the problem. Reading through the docs, I can’t figure out what is wrong with these.  They both have event_name and created_at, the two required fields.  One has metadata, and one does not, but metadata is listed as optional, anyway.  I tried adjusting the event_names — replacing underscores with hyphens, truncating them &c., even trying a random string of 10 ascii chars, but these requests always still fail.  I got a coding agent to read through the docs, and it

When a contact replies through the email channel to a closed ticket, there is no webhook received even though the ticket reopens. Is this a feature or a bug?

https://developers.intercom.com/docs/references/rest-api/api.intercom.io/contacts/createcontacthttps://developers.intercom.com/docs/references/rest-api/api.intercom.io/contacts/updatecontact I am unable to figure out why this is happening and on the API documentation says it should be able to update the value.