Mobile SDKs

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 be

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

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

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  libdispa

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

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

As of @intercom/intercom-react-native v8.2.0 the back button after presenting content using Intercom.presentContent(IntercomContent.helpCenterCollectionsWithIds([id]))is broken on Android devices.Screenshot attached. Any help appreciated.  

Hi Intercom team,We're encountering a crash in our production app related to the Intercom SDK when processing push notifications. The error occurs in TaskStackBuilder.getPendingIntent() with the following stack trace:  Fatal Exception: java.lang.IllegalStateException: No intents added to TaskStackBuilder; cannot getPendingIntent at androidx.core.app.TaskStackBuilder.getPendingIntent(TaskStackBuilder.java:333) at androidx.core.app.TaskStackBuilder.getPendingIntent(TaskStackBuilder.java:313) at io.intercom.android.sdk.m5.push.ConversationDeepLinkRouterKt.buildBasePendingIntent(ConversationDeepLinkRouter.kt:85) at io.intercom.android.sdk.m5.push.ConversationDeepLinkRouterKt.buildIntentForDeepLinkScreen(ConversationDeepLinkRouter.kt:42) at io.intercom.android.sdk.m5.push.ui.DeepLinkStylePushUIKt.buildDeepLinkNotification(DeepLinkStylePushUI.kt:44) at io.intercom.andr

Release Date: 16-05-2025 🐛 Bug Fixes Fixes a bug that could cause a crash when dismissing multiple in app notifications. Fixes a bug that could cause a crash when trying to close a note using the x button.

Hi! I have the “Prevent users from opening multiple conversations” option enabled in Intercom settings, but when calling Intercom.presentMessageComposer(); from my React Native app, it always creates a new conversation instead of navigating to the existing one.Is this the expected behavior, a known issue, or am I missing something in the implementation?What’s the best way to handle this scenario?Thanks!

Release Date: 11-04-2025 🚀 Enhancements We've added a new API to enable setting JWTs in the Messenger. This should be called before any user login. To learn more go here. Resolved some differences between the registration of unidentified and identified users of iOS and Android. Both platforms now have matching implementations.

Hi, So I’ve implemented the Intercom SDK into our Android app the past few days and stumbled in to a strange thing. The SDK crash as I’m trying to open the write message view with this error.java.lang.NoSuchMethodError: No static method FlowRow(Landroidx/compose/ui/Modifier;Landroidx/compose/foundation/layout/Arrangement$Horizontal;Landroidx/compose/foundation/layout/Arrangement$Vertical;IILandroidx/compose/foundation/layout/FlowRowOverflow;Lkotlin/jvm/functions/Function3;Landroidx/compose/runtime/Composer;II)V in class Landroidx/compose/foundation/layout/FlowLayoutKt; or its super classes (declaration of 'androidx.compose.foundation.layout.FlowLayoutKt' appears in /data/app/~~MDeJzUHvf74b7jpNmGq6Rw==/com.*.staging-7N_jvukfhGCaqNo-t2IqvQ==/base.apk)    at io.intercom.android.sdk.m5.conversation.ui.components.row.QuickRepliesKt.QuickReplies(QuickReplies.kt:38)    at io.intercom.android.sdk.m5.conversation.ui.components.row.QuickRepliesKt.Compose

Hi, using the latest version i manage to build the app on IOS (your last update fixed the expo plugin swift headers) but didn’t fix the sdk. now on ios presenting intercom shows a loading error (was working fine before the update to new arch and expo 53) and on android nothing happens when i call intercom.present() expo 53react 19react-native 0.79.2@intercom/intercom-react-native 8.4.0

Release Date: 01-11-2024 📱 New Feature Added the ability to upload files to a conversation. 🚀 Enhancements Added new API isUserLoggedIn. This enables developers to determine if a user is currently logged in to Intercom. Added new API fetchLoggedInUserAttributes. This enables developers to retrieve the attributes of the currently logged in user. 🐛 Bug Fixes Fixed some layout issues in the conversation view. Improvements to the photo previewer. Fixes some colour accessibility issues throughout the SDK. Fixes issue where clicking on the CTA in a post would not dismiss it.

We did implement the intercom Integration with our mobile app and everything works like a charm BUT we realised we are sending communications to our clients over the chat but they don't seem to realise messages are waiting for them since the app badge count is zero. I'd tried to increase the value over the AppDelegate methods but can't make it increase the count when the app is not running or in background. Also tried to create a Notification Extension for the app but the criteria for the modifications won't meet since the payload of the notifications has the value mutable content set to false (mutableContent: NO)  Another way to make this work would be to send notifications as silent ones but don't know if the payload from Intercom's notifications is customisable. Any help with this subject would be much appreciated. Bests.

Presenting secondary-level collections doesn't work on iOS SDK (opens the root help center) but works fine on Android SDK.Presenting top-level collections works as expected on both platforms.

Hello,We have successfully integrated your Android SDK (version 15.16.0) into our application. However, we are currently seeing a significant number of crashes reported in Firebase. Unfortunately, we haven’t been able to reproduce the issue on our side so far.Could you please help us investigate this further? Let us know if you need any additional information or logs to assist in the debugging process.Thank you in advance for your support.This is the crash:          Fatal Exception: java.lang.NullPointerException:       at androidx.compose.ui.platform.AndroidComposeView.<init>(AndroidComposeView.android.kt:788)       at androidx.compose.ui.platform.Wrapper_androidKt.setContent(Wrapper.android.kt:77)       at androidx.compose.ui.platform.AbstractComposeView.ensureCompositionCreated(ComposeView.android.kt:258)       at androidx.compose.ui.platform.AbstractComposeView.onAttachedToWindow(ComposeView.androi