Mobile SDKs

Hello! I’m the RN (react-native) developer and integrated your mobile SDK in my app for both platforms.  I used 8.6.0 version of this package RN-Intercom. I found a bug related to the launcher icon background color. This issue appears only in the current version. I tested the previous four versions, and the bug was not present in any of them. I double-checked the mobile SDK style configuration in the web settings, and everything looks correct to me.Important note:This issue occurs only on the first launch of Intercom in the app.I would be very grateful for a solution to this problem.

 Hi Intercom Support Team,We’re encountering a runtime crash in our Android application after integrating the latest version of the Intercom SDK.Although our app is developed using Kotlin with traditional View-based UI (not Jetpack Compose), the crash appears to be originating from Compose-related code within the Intercom SDK.Crash Details (from Firebase Crashlytics): java.lang.IllegalStateException: ViewTreeLifecycleOwner not found from android.widget.FrameLayout{654c395 V.E...... ........ 0,0-2171,1080 #7f0b04aa app:id/intercom_overlay_root viewInfo = } at androidx.compose.ui.internal.InlineClassHelperKt.throwIllegalStateExceptionForNullCheck(InlineClassHelper.kt:32) at androidx.compose.ui.platform.WindowRecomposer_androidKt.createLifecycleAwareWindowRecomposer(WindowRecomposer.android.kt:455) at androidx.compose.ui.platform.WindowRecomposer_androidKt.createLifecycleAwareWindowRecomposer$default(WindowRecomposer.android.kt:321) Environment:Language: Kotlin UI Framework: View-based (n

Hey everyone,I'm running into a frustrating issue with the Intercom SDK (iOS and Android) and wondering if anyone has seen this before. Ever since switching to the Intercom SDK, I've noticed way fewer support requests coming in. At first I thought maybe that was a good thing, but then users started emailing me directly saying they can't access support through the app.The error they're seeing is "something's gone wrong. Content could not be loaded" - both in the messenger and when trying to view help articles. I've attached a screenshot from one Android user. The weird thing is that if they sign out and back in, it starts working again temporarily.I initially suspected JWT validation issues, so I disabled that completely for both iOS and Android, but the problem persists. When I contacted support about this, they suggested it might be network issues, but that doesn't make sense to me since signing out/in fixes it for that specific user.The really annoying part is that the SDK doesn't se

Hi Intercom Support,I would like to report an issue encountered on Android devices when handling push notifications from Intercom. Specifically, the main application crashes upon tapping a push notification if the sender has an avatar (image_url is not empty).Reproduction Steps:Create a trial Intercom conversation. Configure the Intercom Android SDK with the app ID and push notification settings. Use the main app to initiate a first message to Intercom. From the Intercom admin interface, send a reply message from an agent account that has no avatar set (i.e., image_url is empty). Receive the push notification on the Android device and tap on it.Observed Behavior:If the sender has an avatar (image_url is set): Tapping the push notification opens the Intercom conversation. However, the main app process is killed. Pressing “Back” returns to the Android home screen. The user must relaunch the app manually. If the sender does not have an avatar: Tapping the notification opens the Interco

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

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 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.

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

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

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

Hello everyone; When the iOS app launches, we log in our Intercom user as an undefined user. Later, when the user log in or creates an account with a JWT token and we login them in as an identified user through Intercom, we can't see the undefined user's messages. When we try to send a message, we get an error. I did the SDK integration correctly and the JWT token is working properly. But it's not automatically merging users' messages. How can I solve this problem? SDK Version; 18.8.0iOS: 18.4, 18.5UI Error;Something’s gone wrongCouldn’t load the conversation Intercom Request Error;Path: https://<app-id>-ios.mobile-messenger.intercom.com/messenger/mobile/conversations/215469369303322Code: 404{ "type": "error.list", "request_id": "004gb7n4n158kmpf4qeg", "errors": [ { "code": "not_found", "message": "Resource Not Found" } ]}  ​

Hello, we've recently updated our SDK to the latest version (16.0.0) and we've been seeing a few crashes in production related to the in app notification. This seems to happen when showing the Full notification, as there seems to be something missing in the layout that intercom uses internally. We've just bumped to the latest version, but looking at the code, that doesn't seem to solve this particular issue.This is the stack trace we're getting:Fatal Exception: java.lang.NullPointerExceptionParameter specified as non-null is null: method io.intercom.android.sdk.m5.notification.InAppNotificationCardKt.addInappNotificationCardToView, parameter composeViewio.intercom.android.sdk.m5.notification.InAppNotificationCardKt.addInappNotificationCardToView (InAppNotificationCard.kt:3)io.intercom.android.sdk.overlay.ChatNotification.populateViewsWithData (ChatNotification.java:90)io.intercom.android.sdk.overlay.ChatNotification.display (ChatNotification.java:64)io.intercom.android.sdk.overlay.InAp

Hey! We have started getting this crash recently and switching to the latest sdk(16.1.0) didnt help. Can you please help me with this? Thanks! Missing keys: [timestamp] in '{teammate} flyttet saken til {status} {timestamp}'Full crash log: java.lang.IllegalArgumentException: Missing keys: [timestamp] in '{teammate} flyttet saken til {status} {timestamp}' at io.intercom.android.sdk.utilities.Phrase.format(Phrase.java:0) at io.intercom.android.sdk.utilities.Phrase.format(Phrase.java:189) at io.intercom.android.sdk.m5.notification.InAppNotificationCardKt.TicketInAppNotificationContent(InAppNotificationCard.kt:180) at io.intercom.android.sdk.m5.notification.InAppNotificationCardKt.InAppNotificationCard(InAppNotificationCard.kt:124) at io.intercom.android.sdk.m5.notification.InAppNotificationCardKt$addInappNotificationCardToView$1$1$1.invoke(InAppNotificationCard.kt:75) at io.intercom.android.sdk.m5.notification.InAppNotificationCardKt$addInappNotificationCardToView$1$1$1.i

I'm currently integrating Intercom into my React Native Android Expo app and running into some build issues that I haven't been able to resolve. I’ve followed the official setup guide and installed @intercom/intercom-react-native, but the build fails when running the Android version of the app.Details:React Native version: 0.74.5   Intercom SDK version: @intercom/intercom-react-native@8.3.0"   Java version: Java 17 on M1 Mac   Error message: TypeError: null is not an object (evaluating 'IntercomEventEmitter.UNREAD_COUNT_CHANGE_NOTIFICATION')

Hola comunidad,Estoy integrando Intercom en una app React Native (bare, usando EAS Build, no Expo Go) y tengo el siguiente problema:Uso el método Intercom.getUnreadConversationCount() para mostrar un badge de mensajes no leídos.El usuario está correctamente identificado (userId y email coinciden con los del panel web).Desde el panel web de Intercom, envío mensajes al usuario (tanto desde un agente humano como desde el bot).En el panel web, los mensajes aparecen como “Not seen” para el usuario.Sin embargo, en la app, el método getUnreadConversationCount() siempre retorna 0, incluso después de recibir mensajes nuevos y refrescar el conteo.Ya probé con mensajes automáticos/bot y tampoco se refleja el conteo.No necesito push notifications, solo quiero mostrar el número de mensajes no leídos.Estoy usando la última versión de @intercom/intercom-react-native y la integración nativa está bien (la mensajería funciona).¿Alguien ha tenido este problema?¿Hay alguna limitación conocida en el SDK de

We're experiencing an issue where the mobile carousel feature gets dismissed automatically on app start for logged-in users. Our app is built with React Native and Expo.To isolate the issue, we tested with a minimal project containing only an empty screen and Intercom login. The issue does not occur on the first app launch (since Intercom login hasn't been triggered yet). However, once the user is logged in and we send a carousel from Intercom, reopening the app causes the carousel to briefly appear before getting dismissed.We also ensured that Intercom login is only called on the first launch, as a support ticket suggested that calling it repeatedly might be causing the issue. Despite this, the problem persists. Additionally, we've attached a video demonstrating the issue: The splash screen appears first The carousel appears briefly The carousel gets dismissed Our white screen is displayed Similar issue is mentioned in  

Hi Intercom We are trying to update the Intercom SDK for our app to the latest version, currently still on version 2.0.1 We are using React Native with Expo (version 51.0.39), and it works fine with version 2.0.1 (we are using the Expo plugin from version 8 of the React Native package), but if we try to update to the latest version, we get strange behaviors on iOS:For some users, during testing, some buttons are missing (for example the “close” button on the top left is missing, you can actually touch it but the icon is missing) Can’t send messages Can’t upload files from Google Drive   Other users had a black screen that went away after restarting the app (all of these tests were made with a release build deployed to TestFlight for iOS and Play Store as closed beta) This issue is not happening on all devices and not for all users (we had issues on iPhone 11 Pro with iOS 18.3.1, but was working fine on an iPhone 16 Pro with iOS 18.2.0)This is how we have configured the Explo plugin:[

If we click to “Help” and select one of articles, we see in navigation bar only cross button on Android and if we click on it intercom will close. Also if we click to system back button on article screen intercom also will close. For example on iOS we have two navigation buttons on article screen, back button and close button.Is it possible to change the behavior for the cross button on Android so that it returns back to the article selection or add a back button like on iOS? 

Hello,We started to see a new crash in our production app since bumping the Android SDK to version 16.0.0. We've tried bumping it to 16.1.0 but still see this issue. It seems there's something missing in the layout of one of the in-app notification types which is causing this crash.Would you be able to take a look into this, please? Fatal Exception: java.lang.NullPointerException: Parameter specified as non-null is null: method io.intercom.android.sdk.m5.notification.InAppNotificationCardKt.addInappNotificationCardToView, parameter composeView at io.intercom.android.sdk.m5.notification.InAppNotificationCardKt.addInappNotificationCardToView(InAppNotificationCard.kt:3) at io.intercom.android.sdk.overlay.ChatNotification.populateViewsWithData(ChatNotification.java:90) at io.intercom.android.sdk.overlay.ChatNotification.display(ChatNotification.java:64) at io.intercom.android.sdk.overlay.InAppNotificationPresenter.addNewNotifications(InAppNotificationPresen

Release Date: 03-06-2025 📱 New Feature: Conversational Fin We’re making conversations more natural and reducing the need for escalations. More human, less rigid: We’ve removed quick reply buttons so Fin can respond fluidly—no decision trees, just natural conversation. Sources, now inline: Fin now includes source links directly in replies, so customers can verify info at a glance.

I have a problem where I’m using expo-splash-screen to show a splash screen while I do loading tasks before presenting the application. The problem is that when the app receives a push notification from Intercom and we open the app from that notification Intercom presents the chat UI before the splash screen has been dismissed and the app UI has been shown. I imagine this is happening because `intercom-ios` does the handling of its push notifications internally and has not knowledge of whether the app is “ready” or not. How can we fix this?