Popular Topics

Howdy!We're experiencing this issue after updating from 3.x SDK to 4.0.1 (https://github.com/intercom/intercom-react-native react-native version: 0.70.5  Code sample (which is basically the same that you have in docs):  useEffect(() => { const subscription = Intercom.addEventListener( IntercomEvents.IntercomUnreadCountDidChange, (response) => { setCount(response.count); } );   return () => { try { subscription.remove(); } catch (e) { console.log(e); } }; }, []); Calling subscription.remove on line 11 during effect cleanup triggers an exception. Line 13 prints:[RangeError: Maximum call stack size exceeded]Without try/catch block the call just fails silently due to this - https://github.com/facebook/react-native/issues/32673(which doesn't contribute to the original problem, just makes it go unnoticed).  Let me know what other details you might need. What can be done about it? Thanks.

Hello Intercom team,I am encountering a Gradle build error when integrating the intercom-react-native library into my React Native project. The issue seems related to an implicit task dependency conflict.Error details:A problem was found with the configuration of task ':intercom-react-native:copyDebugJniLibsProjectAndLocalJars' (type 'LibraryJniLibsTask').Gradle detected a problem with the following location: '[project path]/node_modules/@intercom/intercom-react-native/android/build/intermediates/stripped_native_libs/debug/stripDebugDebugSymbols/out'.Reason: Task ':intercom-react-native:copyDebugJniLibsProjectAndLocalJars' uses output from ':intercom_intercom-react-native:stripDebugDebugSymbols' without declaring a dependency.Attempted solutions: Cleaned Gradle build and cache. Added explicit task dependencies using afterEvaluate, but encountered errors related to task names not found. Could you please assist in resolving this issue or provide guidance on properly handling this Gradl

Hello,It seems there may be an issue with how the Intercom API parses the src attribute of Vimeo <iframe> embeds in Help Center articles.When I try embedding a Vimeo video using a valid and supported format like this:<iframe src="https://player.vimeo.com/video/76979871?autoplay=1&loop=1&autopause=0" width="640" height="360" frameborder="0" allow="autoplay; fullscreen" allowfullscreen="allowfullscreen"></iframe>…the video fails to render in the Help Center and I get this error response:"errors":[{"code":"unsupported_html","message":"Video src is not supported"}]However, this YouTube embed works perfectly in intercom:<iframe title="YouTube video player" src="https://www.youtube.com/embed/R7CC4NYokNI?si=-s_wXnz1orMp-Dn2" width="560" height="315" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen="allowfullscreen"></

Release Date: 03-07-2025 🐛 Bug Fixes Fixes a bug that could cause a crash when trying to resend a failed media message. Fixes a bug that could cause a crash during complex gradient background processing.

Hi guys, I am having problems to upgrade from expo 52 to expo 53 due to intercom issues.In version 8.0.0, ios is not working due to  ❌ (ios/TakenosDevelop/AppDelegate.swift:1:2)> 1 | #import <IntercomModule.h> | ^ no macro named 'import' 2 | import Expo 3 | import React 4 | import ReactAppDependencyProvider This is fixed on 8.5.0 but this version uses sentry Android SDK >= 8 and clashes with sentry-react-native that uses sentry Android SDK >=7.  I am using @sentry/react-native version 6.14.0(recommended by expo)Here is a conversation related to the issue on sentry github: https://github.com/getsentry/sentry-react-native/issues/4688The error i am seeing:Error: Exception in HostFunction: No direct method <init>(Ljava/lang/String;ILio/sentry/android/core/internal/util/SentryFrameMetricsCollector;Lio/sentry/ISentryExecutorService;Lio/sentry/ILogger;Lio/sentry/android/core/BuildInfoProvider;)V in class Lio/sentry/android/core/AndroidProfiler; or its super classe

Hello! We recently integrated Intercom into our iOS app (currently using Intercom 18.7.3 SDK for iOS). As I’ve been monitoring the releases, I have seen in the Xcode Organizer → Metrics → Memory a BIG spike in our app’s memory use. We have changed little in the app itself since integrating Intercom, so my investigation of the memory spike focused on Intercom.I started with the simplest exploration: use Instruments with the Allocations tool, Mark Generations, and see what happens. In my case, I tested our invocation of the Messages UX. Our app code in question looks like this (simplified): // In the ViewControlleroverride func tableView(_ tableView: UITableView, didSelectRowAt indexPath: IndexPath) { tableView.deselectRow(at: indexPath, animated: true) let action = self.sections[indexPath.section].rows[indexPath.row] switch action { case .emailfeedback: self.viewModel.sendFeedback(from: self) }}// In the ViewModel (almost; VM uses a Service class, which then this i

Hey team,I’m Prakash Hinduja from Geneva, Switzerland (Swiss) looking to integrate a chatbot into our website to improve customer engagement, but I’m not sure about the best approach to get it set up and running smoothly. I’ve done some initial research, but I’d love to hear your thoughts and experiences. Regards Prakash Hinduja Geneva, Switzerland (Swiss)

I was trying the List collections endpoint under the Help Centre APIs using PaginationTh Pagination Guide describes List APIs as using cursor based pagination, with the “next” parameter containing the “starting_after” parameter which can be used to fetch the next page of resultsHowever, when I tried the List collections endpoint I got this as the result for the “pages” parameter. The “next” parameter gives a URL, not an object as described in the docs"pages": {    "type": "pages",    "next": "https://api.intercom.io/help_center/collections?per_page=1&page=2",    "page": 1,    "per_page": 1,    "total_pages": 4  }Here are the headers I used for reference:{“Authorization”: “Bearer <token>“,“Accept”: “application/json”,“Intercom-Version” : “2.13”}Since I’m passing the intercom-version I don’t expect this to be an error with the version. Please explain the correct way to use PaginationI see a related issue here. However I’m unsatisfied with the solution provided. In case the API

I’m trying to bring down the number of duplicate emails in Intercom so I can actually use the Hubspot integration. It looks like one of the culprits is the Stripe integration. Many of my duplicates look like this: User 1:email = jane@doe.com user_id = foobar stripe ID = unknownUser 2:email = jane@doe.com user_id = unknown Stripe ID  = abcdefI can manually go through and archive these junk users that Stripe has created, but then my question is:Can I prevent Stripe from doing that in the first place? Can it just wait for the “good” user (one with a user_id) and attach the stripe data to that one? If I archive the stripe-connected user, will Stripe attempt to find and resync with the good user?

I tried to add intercom help center articles as an embed iframe on React. But it's rejected because of CORS issue. Can you add our website, so that we can avoid CORS issue? Or is there any work around?

I’m using the API to create and manage tickets, and seeing some unexpected things in the auto-email-notification subject lines.The steps I’m following:Create a ticket via the API. Type: Tracker Ticket. It properly appears with my title and description. (Notifications skipped). Assign that ticket via the API. (Notifications skipped). Add a comment to the ticket via the API. For this step I’m not setting skip_notifications to true, so a notification does get dispatched.The problem is that the subject line of that notification is: Re: [Company Name] [Assignee Name]: ''The empty single quotes indicate that it should be possible to get something to appear there. I’d love to be able to display the ticket title, or the contents of the comment that caused the notification, or pretty much anything other than ‘’.

Hi everyone 👋We’re building a Canvas App Sheet for a live Intercom Messenger integration. Our goal is to let logged-in users view and update profile data — specifically values like First Name, Last Name, Primary Chapter, and SpotMe_Id — all of which are being passed into Intercom via a custom embed snippet.✅ These custom attributes show correctly on the user profile inside Intercom.🚫 But when the Canvas App loads via /sheet, the contact.custom_attributes payload does not include these fields (we checked with full logging of req.body). We tried accessing them via: jsconst contact = req.body.contact || req.body.context?.contact || {}; const attrs = contact.custom_attributes || {}; Even though we can see the correct attributes in Intercom, attrs only contains empty/default values like Member, or Global.We’ve verified: intercomSettings in the embed includes the attributes (they appear in the user profile) We’re using open_mode: "conversation" in our Canvas App button App is launched

Here are the errors:  jetified-intercom-sdk-base-15.10.3-runtime.jar: D8: java.lang.NullPointerException: Cannot invoke "String.length()" because "<parameter1>" is nullWhat I’ve Tried: Checked build.gradle for SDK version compatibility Cleaned and rebuilt project (./gradlew clean && ./gradlew build) Searched through Intercom docs and changelogs Looked at open issues in the GitHub repo My Setup: React Native version: 072 Intercom SDK version: 15.10.3   Gradle: 8.0.1 Questions: Are these methods deprecated or moved to a different namespace? Is there a recommended way to check login state and fetch user attributes in the latest SDK? Should I downgrade to a previous version of the Intercom SDK? Any help is greatly appreciated!

*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[__NSArrayM insertObject:atIndex:]: object cannot be nil'*** First throw call stack:(0   CoreFoundation                      0x00000001804ae0f8 __exceptionPreprocess + 1721   libobjc.A.dylib                     0x0000000180087db4 objc_exception_throw + 562   CoreFoundation                      0x0000000180393044 -[__NSArrayM insertObject:atIndex:] + 12523   Intercom                            0x00000001060eb528 IntercomSDK_saveViewHierarchy + 4969884   Intercom                            0x00000001060eadec IntercomSDK_saveViewHierarchy + 4951365   Foundation                          0x0000000180d54084 -[NSObject(NSKeyValueCoding) setValuesForKeysWithDictionary:] + 1846   Intercom                            0x00000001060eacd4 IntercomSDK_saveViewHierarchy + 4948567   Intercom                            0x00000001060eac78 IntercomSDK_saveViewHierarchy + 4947648   Intercom                           

We are encountering crashes on Android devices related to Intercom SDK version 15.9.1. Stack Trace:Failed to build unique file: /storage/emulated/0/DCIM/vr-unit.gif bucket_display_name=DCIM volume_name=external_primary date_modified=null date_expires=null _display_name=vr-unit.gif mime_type=image/gif _data=/storage/emulated/0/DCIM/vr-unit.gif _size=null is_trashed=0 is_pending=0 bucket_id=-2075821635 relative_path=DCIM/ android.content.ContentResolver.update (ContentResolver.java:2318)arrow_rightio.intercom.android.sdk.ui.preview.viewmodel.PreviewViewModel.saveImageOnApi29Above (PreviewViewModel.kt:201)io.intercom.android.sdk.ui.preview.viewmodel.PreviewViewModel.access$saveImageOnApi29Above (PreviewViewModel.kt:35)io.intercom.android.sdk.ui.preview.viewmodel.PreviewViewModel$saveImage$1.invokeSuspend (PreviewViewModel.kt:92)kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith (ContinuationImpl.kt:33) Device : Mostly Google PixelAndroid Version: 11, 12

Hi,  So I’ve been working on setting up my account and I’m stuck at this for over a week now.  I’ve got a lead form and these leads are being sent to Intercom, with custom lead data (attributes) such as event date and event type. This is all sent through zapier and Intercom API.  However, when a lead already exists, it’s not updating the lead with these custom attributes. All API work, I get the right 200 response, I do not get duplicated leads and so on. Mapping is all correct and we tested via Postman and via Intercom test enviroment, here it all works, yet sending real data via Zapier to Intercom does not update the lead.  We’ve checked with both support teams and lead data is sending through zapier to Intercom. However Intercom support mentioned they do not receive the body call, while the zapier logs show this is being sent correctly.  What is going wrong here, is this just a bug? I can’t believe no one is using the API on zapier to update lead profiles. I’ve spent 10 hours + ever

Hi Intercom team,I’m Romain from Ringover, a partner working with clients on Intercom integrations. I’d like to submit a feature request regarding the ability to ⭐ update internal notes ⭐ via your API.Currently, instead of updating the original internal note with new content (e.g. an AI-generated call summary), the API creates multiple separate notes for each update. Since Ringover also sends additional after-call events such as updated notes and tags, this results in a cluttered view within the Intercom workspace.Being able to update an existing note via API would significantly improve clarity and user experience for our shared clients.Could you please forward this request to the product team?Thank you for your collaboration.Best regards,Romain 

Hi Team,Is there a way / specific webhook one could use to subscribe to events when a Linear ticket is created from an Intercom conversation? I was unable to identify any specific one - as far as I can tell the only way to check from Intercom side is to loop through the conversation parts looking for the note signifying the connection.Thank you in advance!

It appears that the only opportunities for aggregation are Average, Median, Minimum, and Maximum but I want a Sum of all the time spent handling tickets for the last three months. How can I aggregate by Sum instead? How can I either remove the aggregation options so I can see a total sum, or get a full list of all the conversations and all of their handling time so I can sum it myself? Thanks!

Noticed an issue with the conversation search API, specifically on boolean fields when coupled with the != operator.For example the below query (even when run from the “Try it” button on the docs page) returns the same exact response as when using the = operator.  POST https://api.intercom.io/conversations/searchBody: {    "query": {        "operator": "AND",        "value": [{      "field": "read",      "operator": "!=",      "value": "true"    }]  }}I tested with different value types (string, boolean), other boolean fields (ex: open), as well as with “false” values. The behavior is the same.Please assist.

Hello everyone, I have been receiving this error when the app initialize on the mobile. @intercom/intercom-react-native is at 8.5.0, which seems to be the latest. iOS version is at 17.2   

Dear Team,I’m Prakash Hinduja from Switzerland, I'm a Consultant and Advisor, I’m exploring ways to sync my website with my social media accounts to streamline content sharing and enhance engagement. As part of this initiative, I would appreciate your suggestions on the most effective methods or tools you’ve used or come across. RegardsPrakash Hinduja Switzerland 

Release Date: 11-06-2025 🐛 Bug Fixes Fixes a bug where articles could render in the incorrect interface style.

Hello,When I query the conversation_tag_history table, I noticed there can be multiple conversation_updated_at values for the same tag_id and conversation_id.Usually the MIN(conversation_updated_at) value is accurate, but I wonder how this can be the case?It happens frequently so I don’t think it’s because someone is removing a tag and adding it again, but I can be mistaken.Thanks in advance!

Hello All,As I continue scaling tiered support, I’m working to improve how we monitor both real-time and historical trends. Specifically, I’m trying to track: Time from conversation start to first assignment (Time in Unassigned) Time from first assignment to reassignment (Time in Tier 1) Time from reassignment to first close (Time in Tier 2) I also want to make sure we’re capturing the entire lifespan of the ticket, including both open and snoozed time.Right now, inbox views are the only way to surface aging tickets—but they aren’t designed for this kind of analysis. They don’t function like reports, and they don’t allow us to layer in the conversation attributes we’ve added, such as product area or difficulty level.That makes it tough to proactively support aging tickets, coach the team in real time, or dig into specific themes during 1:1s—especially when trying to identify which product areas need more targeted coaching.I’d love any ideas on how we can bring better visibility to