Mobile SDKs

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?

Hi! Evaluating Intercom now as a potential replacement for my previous support system. Setup has been great so far! However, I do see one potential showstopper in the Android SDK. When receiving a push notification it is possible to open the intercom messages directly from the notification, and then have a permanent “chat bubble” on the home screen. We are a very small team with a large userbase, and can’t have a direct line to support available on users home screens. Is there a way to disable this? I do want users to get notified when there is a new message, and it could be fine to open the messenger directly. However, to show a permanent chat bubble on the home screen is not something I am comfortable with. Can you disable this in some way?

Hi. This is on both Android (1.16.0) and iOS (18.7.2). When I start a conversation with the AI chatbot and use one of our predefined quick replies I need to wait until the textfield appears and then send a new text message or send a GIF before the AI reacts to the first quick replie I sent. This feels like a bug in the implementation and of course the chat should start right away if the user uses the quick replie feature, 

We are utilising the 6.0.2 version of the capacitor-community/intercom package, which is using a 12.x version of the Intercom Android SDK internally.What seems to be happening is that when the plugin registers it is making an initial call to Intercom (probably for the reasons outlined in this thread: Our JS implementation code does not do anything until the user logs in. At which point we call `setUserHash` and `registerIdentifiedUser` respectively. We then have a button that launches the intercom bubble (displayMessenger).On a fresh install an Android 15 this works fine. We can login, click the button and intercom launches. On Android 16 it doesn’t. If you exit the app and restart it works fine from that point onwards.When monitoring the logs on the Android 16 device, with a release build, we get this error immediately upon app launch, before the user has a chance to interact (or even grant permissions for things like push notifications):Failed to register or update user: {"type":"err

This is specifically for the followup camera request (“<app> does not have access to your camera”) after declining the first camera request. From Apple:Guideline 5.1.1 - Legal - Privacy - Data Collection and StorageThe app encourages or directs users to allow the app to access the camera. Specifically, the app directs the user to grant permission in the following way(s):- A custom message asks users to reconsider their decision after they deny the permission request.Permission requests give users control of their personal information. It is important to respect their decision about how their data is used.Next StepsTo resolve this issue, please revise the permission request process in the app to not ask the user to reconsider denying permission.

Hello,It seems that the @intercom/intercom-react-native is not compatible with Expo SDK 53. it fails to build with the following error:> 1 | #import <IntercomModule.h> | ^ no macro named 'import' 2 | import Expo 3 | import FirebaseCore 4 | import ReactAre there any plans to support it?

 Intercom SDK version: 16.0.3 Xcode: 15.0 UIGraphicsBeginImageContext() failed to allocate CGBitampContext: size={0, 0}, scale=3.000000, bitmapInfo=0x2002. Use UIGraphicsImageRenderer to avoid this assert.0CoreFoundation __exceptionPreprocess 1libobjc.A.dylib objc_exception_throw 2Foundation -[NSMutableDictionary(NSMutableDictionary) initWithContentsOfFile:] 3UIKitCore _UIGraphicsBeginImageContextWithOptions-[Ullmage(ICM|mageUtils) icm_resizelmageToSize:]_51-[ICMReactionsViewController displayOption:inView:]_block_invoke_2

Hello Team,We recently updated to the Intercom iOS SDK 17.0.1 and started getting a crash in the SDK with the following stacktrace.  Crashed: nexus.reachability0  libobjc.A.dylib                0x4e30 lookUpImpOrForward + 881  libobjc.A.dylib                0x34c4 _objc_msgSend_uncached + 682  Intercom                       0x50cf4 -[IntercomSDK_IntercomNexusSocket isConnected] + 201563  Intercom                       0x50ef8 -[IntercomSDK_IntercomNexusSocket reconnect] + 206724  Intercom                       0x4db48 -[IntercomSDK_IntercomNexusConnection reconnectSockets] + 74405  Network                        0x83844c __nw_path_necp_update_evaluator_block_invoke + 3166  libdispatch.dylib              0x213c _dispatch_call_block_and_release + 327  libdispatch.dylib              0x3dd4 _dispatch_client_callout + 208  libdispatch.dylib              0xb400 _dispatch_lane_serial_drain + 7489  libdispatch.dylib              0xbf30 _dispatch_lane_invoke + 38010 libdispatch.dylib          

Hi, we’re running into an issue with ANRs on our application stemming from the initialize call on the Intercom SDK.We are currently using 15.1.4 of the Android SDK with the following code used for initialization:Intercom.initialize( application, apiKey, appId)The following is the stacktrace we’re seeing in Firebase for a number of our users: io.intercom.android.sdk.Injector.getMetricTracker (Injector.java:255)io.intercom.android.sdk.Injector.getOverlayPresenter (Injector.java:279)io.intercom.android.sdk.Injector.getResetManager (Injector.java:333)io.intercom.android.sdk.Injector.getLifecycleTracker (Injector.java:311)io.intercom.android.sdk.Injector.initWithAppCredentials (Injector.java:135)io.intercom.android.sdk.Intercom$Companion.create (Intercom.kt:1092)io.intercom.android.sdk.Intercom$Companion.initialize (Intercom.kt:1005)com.<redacted>.android.util.IntercomUtil.initialize (IntercomUtil.kt:38)  When looking at the releases, we’re currently 2 patch versions behind b

Hello ,while init intercom sdk in App.kt which is app launch class ANR is produced please find the error belowmain (runnable):tid=1 systid=8183 at io.intercom.android.sdk.identity.AppConfig.<init>(AppConfig.java:125) at io.intercom.android.sdk.Injector.initWithAppCredentials(Injector.java:104) at io.intercom.android.sdk.RealIntercom.create(RealIntercom.java:80) at io.intercom.android.sdk.Intercom.initialize(Intercom.java:73) at yourpakagename.com.manager.IntercomManager.configure(IntercomManager.java:24) at yourpakagename.com.App.onCreate(App.kt:95) at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1277) at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6771) at android.app.ActivityThread.-$$Nest$mhandleBindApplication(unavailable) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2129) at android.os.Handler.dispatchMessage(Handler.java:106) at