Popular Topics

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

Hello there!I’m looking for a to conduct quality assurance on the back-office ticket submission process and track the responsible parties for each ticket. Is there a way to generate a report that captures that info? Currently, we have a boolean attribute that we can toggle, however, we can’t filter through it by the person who submitted it. Any help is greatly appreciated! 

Hi!We are not using Fin anywhere in our product and are not currently interested in implementing it. It’s never been integrated into a workflow and I have never manually turned it on. From our customer’s help chat perspective, they are seeing the following header on the chatbox: It happens when the agent they are speaking to goes idle or if the user clicks on a conversation that was previously closed. Why does this show up? I need to remove this. Our product’s customers have no idea what “Fin” is. I also don’t know what “The team can also help” means.Any help would be so appreciated! Thanks

Scribe tutorial videos are very helpful for customers.  We would like to embed in Intercom using iframe.  Is this something product is considering, or may have already implemented?

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 everyone! Karla here from the Technical Support Engineering team. Today, we’re diving into how to use Custom Actions and Custom Objects to reference People data — the kind of data that sticks with your users across multiple conversations. We’ll walk through setting up a Prescription Tracker workflow — a simple example that shows how to store and display data for each user inside Intercom Messenger. Let’s start with the why. Imagine you’re tracking prescriptions for your customers. If a user chats today about Tylenol, you’d want that stored on their profile. Then, if they return next week about Ibuprofen, that data should build on top of their record — not replace it. That’s what People data does: it acts like a long-term memory for your users. Each conv

 Issue DescriptionWe're experiencing signal handler conflicts between Firebase Crashlytics and Intercom SDK in our app. During app initialization, we see multiple warnings in the console:[Crashlytics] The signal SIGABRT has a non-Crashlytics handler (IntercomSDK_sentrycrashcm_signal_getAPI). This will interfere with reporting.[Crashlytics] The signal SIGBUS has a non-Crashlytics handler (IntercomSDK_sentrycrashcm_signal_getAPI). This will interfere with reporting.[Crashlytics] The signal SIGFPE has a non-Crashlytics handler (IntercomSDK_sentrycrashcm_signal_getAPI). This will interfere with reporting.[Crashlytics] The signal SIGILL has a non-Crashlytics handler (IntercomSDK_sentrycrashcm_signal_getAPI). This will interfere with reporting.[Crashlytics] The signal SIGSEGV has a non-Crashlytics handler (IntercomSDK_sentrycrashcm_signal_getAPI). This will interfere with reporting.[Crashlytics] The signal SIGSYS has a non-Cra

GET https://js.intercomcdn.com/vendor-modern.1ffdfa4a.js net::ERR_SSL_PROTOCOL_ERROR GET https://js.intercomcdn.com/frame-modern.f3182eef.js net::ERR_SSL_PROTOCOL_ERRORPlease let us know if you need more details

Hi, We are looking to make our Help Center articles mostly limited to just users. We have SSO setup with Entra/Azure and that works fine for access to the backend. Is there a way to leverage Microsoft for access to the Help Center articles so only users that are part of that group can access the articles as well?Thank you!  

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?

I’m working on an email reply automation tool using the Intercom REST API. I’m trying to retrieve the email history — the quoted text that appears collapsed behind the three dots (“…”) when a customer replies to an outbound email we’ve sent them. Three dots for expanding email historyFrom inspecting the network traffic, I can see that this data is retrieved via a private Ember API endpoint:curl 'https://app.intercom.com/ember/inbox/email_history?metadata_id=XXXXXXXXX&app_id=yyyyyyy Is there an equivalent method in the public REST API to access this email history or quoted content?I’ve already tried GET /conversations/{conversation_id}, but the response only includes the conversation parts - it doesn’t contain the quoted email thread

Hi all, we use the Stripe integration from the Intercom App store, and I’ve found some cases in which not all of the Stripe data is populated when a subscription is created. Looking at the affected record in Stripe, I can see the event logs that reference data sent to Intercom but there are no errors present and the request body matches other Intercom users that DO have the subscription data. Is there any logging from the Stripe app in the Intercom marketplace where we can try and troubleshoot this? The best answer I got from Fin was “turn it on and off again” which might be the solution, but I’m hesitate to try that given how central this integration is to us. 

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.

We are trying to use official @intercom/messenger-js-sdk with our react app.https://www.npmjs.com/package/@intercom/messenger-js-sdkWe are calling Intercom instance in our App component Intercom({ app_id: ..., });and then updating user info when user data is available using following functions:import { boot, shutdown, update } from "@intercom/messenger-js-sdk"; when there is no user data we are calling boot with only id,boot({    "app_id": "...",})and if there is user data, we are passing required properties to boot functionboot({    "app_id": "...",    "user_id": "...",    "name": "...",    "email": "...@......",    "created_at": ....,}) 

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?

We are experiencing a critical issue with Intercom integration in our web application.After a user logs in without a full page reload, the Intercom widget appears and lists existing conversations. However:- Existing conversations cannot be opened- Creating a new message often fails- Network tab shows intermittent 403 Forbidden errors with the message: “App suspended”- - Specifically on requests to: POST /messenger/web/conversations/:idIf the user reloads the page after login, everything works as expected:- Conversations open normally- New messages are sent successfullyContext:- We are using the react-use-intercom package for frontend integration.- The app performs a soft reboot after login (without reloading the browser tab). Call shutdown and boot with intercomUserJwt then- When I had this issue it was always because the app_id passed was 'undefined'

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?

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