The 2025 Customer Service Transformation Report is live! 🚀
Engage users of your mobile app with an onboarding and support experience powered by Intercom
Recently active
I'm using Intercom Android SDK And when I'm using the old version, like 12.5.3 I'm able to displayHelpCenter page with the Messenger launcher button in bottom right But when I upgrade to newer version, not sure which version exactlyex : newest version 15.6.3 I call displayHelpCenter and setLauncherVisibility VISIBLE with the same code The launcher icon cannot show above the Help Center home screen (It seems like displayed below the Help Center activity page) In old version 12.5.3 my old code : Intercom.client().displayHelpCenter()Intercom.client().setLauncherVisibility(Intercom.Visibility.VISIBLE)After upgrade to version 15.6.3 my code : Intercom.client().present(IntercomSpace.HelpCenter)Intercom.client().setLauncherVisibility(Intercom.Visibility.VISIBLE)Is it possible to display launcher icon above the Help Center activity page?
Hello Dear Intercom-Support-Team, as of recently we noticed a strange behavior in our application and it is no longer possible to start a conversation programmatically from our application. The server returns 400 http error on request.We have not changed anything in the intercom settings (I have asked the entire support team) SDK Keys are not expired or so, and have been never changed. Other functions of Intercom Messenger are not affected.Could You please help here, as we use this functionality to provide our customers the possibility to send us Device Logs.Mobile Platforms affected: iOS, Android (both native Apps)Intercom SDK Version: 15.5.0 (also tested with 15.6.2 the same behaviour) POST https://jabaugui-android.mobile-messenger.intercom.com/messenger/mobile/conversationsRequest:{ "body" : "App: lexoffice Android, Version 267 ….", "from" : { "id" : "{id here}", "type" : "user" }, "app_id" : "{app id here}", "hmac" : "{hmac string here}", "user" : { "email" : "{my em
I’m using Android SDK version 14.0.0 and I got this crash in intercom.Inconsistency detected. Invalid view holder adapter positionPartViewHolderCompose{5687a3 position=24 id=-1, oldPos=23, pLpos:23 scrap [attachedScrap] tmpDetached no parent} androidx.recyclerview.widget.RecyclerView{acb0621 VFED..... ......I. 0,109-720,762 #7f0a0212 app:id/conversation_list}, adapter:io.intercom.android.sdk.conversation.ConversationPartAdapter@1f9fbdb, layout:androidx.recyclerview.widget.LinearLayoutManager@88f2678, context:io.intercom.android.sdk.activities.IntercomConversationActivity@4ee8fa7androidx.recyclerview.widget.RecyclerView$Recycler in validateViewHolderForOffsetPosition at line 6156androidx.recyclerview.widget.RecyclerView$Recycler in tryGetViewHolderForPositionByDeadline at line 6339androidx.recyclerview.widget.RecyclerView$Recycler in getViewForPosition at line 6300androidx.recyclerview.widget.RecyclerView$Recycler in getViewForPosition at line 6296androidx.recyclerview.widget.LinearLayo
Hello,The latest Intercom iOS SDK version (15.0.0) has an integration of the Lottie Animation framework. This dependency seems integrated statically. Unfortunately if the host app also integrates Lottie, we now are flooded with following warnings from the System when running the app: ...objc[69173]: Class _TtC6Lottie14AnimatedButton is implemented in both /Users/username/Library/Developer/CoreSimulator/Devices/BFEE2DFC-C11E-470B-B711-48A3266380E2/data/Containers/Bundle/Application/B04B0D15-DDBA-4889-BE53-1EB98904A186/HOSTAPP.app/Frameworks/Lottie.framework/Lottie (0x1055dc0b0) and /Users/username/Library/Developer/CoreSimulator/Devices/BFEE2DFC-C11E-470B-B711-48A3266380E2/data/Containers/Bundle/Application/B04B0D15-DDBA-4889-BE53-1EB98904A186/HOSTAPP.app/Frameworks/Intercom.framework/Intercom (0x104d407e0). One of the two will be used. Which one is undefined. ...(One of each for each Lottie class)It is too risky for us to go to production with the version 15.0.0 of the Intercom SDK
iOS SDK version 16.5.5Crash on startup with the message:NSInvalidArgumentException +[ICMBridge startMonitoringCrashes]: unrecognized selector sent to class 0x10748b618We’re unable to reproduce this issue, but we see in Crashlytics that 2% of our users experience this issue.
My users are reporting that is not possible to send photos. I tried giving all permissions, but still not work. I saw this response:But my question is if Cordova is no longer supported by Intercom. Or how to enable that photopicker in Cordova SDK
App is crashing on startup with the following error: [ICMBridge startMonitoringCrashes]: unrecognized selector sent to class 0x104edb618I’ve tried, reseting cache etc, it fails even on clean CI builds.RN intercom version: 6.4.0 (latest)I tried manually upgrading the iOS sdk (on the rn podspec) to 16.5.5 but same result.If I downgrade to latest 5.x it works, and no logs are output as expected, so seems to be that Intercom is now using sentry, but it conflicts with the version we use.Please provide the Sentry version used, atleast as a quick fix, or make it a dependency of the native iOS podspec objc[56543]: Class SentrySwiftAsyncIntegration is implemented in both /private/var/containers/Bundle/Application/85C2B49D-90F0-4323-B115-A5533DE1419F/[Redacted].app/Frameworks/Intercom.framework/Intercom (0x104ed7de0) and /private/var/containers/Bundle/Application/85C2B49D-90F0-4323-B115-A5533DE1419F/[Redacted].app/[Redacted] (0x101b45590). One of the two will be used. Which one is undefined.objc
Hi everyone, since SPM loads a full mirror of the repository it needs to fetch ~1.5GB of data before a build can start. On a developer machine I don't care to much about that. A lot of it is cached, so its not like I have to pull the repo every time.BUT:The loading of the Intercom SDK SPM on our CI takes a very long time, since it needs to pull a fresh repo mirror everytime it runs. By far the most time of any of our packages which we load. And since we pay per minute this really increases our costs. Other SDKs like Stripe (https://github.com/stripe/stripe-ios-spm and Klarna (https://github.com/klarna/klarna-mobile-sdk-spm have created lightweight mirrors of the SDK that just contain the Sources and Binaries in tagged releases. Would this be a something you could consider?This would save us a lot of time and money during our CI runtime.
Hi!We’ve started seeing crashed on the Intercom version 15.4.0 on an Android 14 device (SM-S918B). We’re updating to the latest 15.5.0 version of the Intercom SDK, but it’s release notes don’t mention if this is fixed there or not.I’m attaching the exception’s stacktrace below, please let me know if you need any additional information. java.lang.IllegalArgumentException: Targeting U+ (version 34 and above) disallows creating or retrieving a PendingIntent with FLAG_MUTABLE, an implicit Intent within and without FLAG_NO_CREATE and FLAG_ALLOW_UNSAFE_IMPLICIT_INTENT for security reasons. To retrieve an already existing PendingIntent, use FLAG_NO_CREATE, however, to create a new PendingIntent with an implicit Intent use FLAG_IMMUTABLE. at android.os.Parcel.createExceptionOrNull(Parcel.java:3073) at android.os.Parcel.createException(Parcel.java:3053) at android.os.Parcel.readException(Parcel.java:3036) at android.os.Parcel.readException(Parcel.java:2978) at android.app.IActivi
Using latest version of sdk 15.6.0, there is a crash by clicking on the new button Take a photo in the message redaction.The device is on Android 14, here is the stack trace. Fatal Exception: java.lang.SecurityException: Permission Denial: starting Intent { act=android.media.action.IMAGE_CAPTURE flg=0x3 cmp=com.google.android.GoogleCamera/com.android.camera.activity.CaptureActivity clip={text/uri-list hasLabel(0) {U(content)}} (has extras) } from ProcessRecord{31fdd92 30802:com.kiplin.app.staging/u0a483} (pid=30802, uid=10483) with revoked permission android.permission.CAMERA at android.os.Parcel.createExceptionOrNull(Parcel.java:3057) at android.os.Parcel.createException(Parcel.java:3041) at android.os.Parcel.readException(Parcel.java:3024) at android.os.Parcel.readException(Parcel.java:2966) at android.app.IActivityTaskManager$Stub$Proxy.startActivity(IActivityTaskManager.java:2086) at android.app.Instrumentation.execStartActivity(Instrumentation.j
Hello, is the only current way of initializing Intercom still through the native codes of both Android and IOS?If so, how would you suggest retrieving the API Keys for them? We currently use AWS Secrets Manager but I’m not exactly sure how to retrieve it inside the native codes of Android and IOS or if that would even work.Having another way of initializing Intercom would be great, if not, how would you suggest doing that? Is there a recommended way from the Intercom team?Exposing the API Keys and APP ID doesn’t seem like a good idea
Some of our users are facing this crash in DocumentPreview.OS version: android8.0.0devices_otherModel:Galaxy A5(2017)I think its reasonable to expect some error handling instead of crash, so user knows that file is not supported or is corrupted.
I'm trying to integrate the SDK's with our react native app that uses expo. The only comment about it on this forum is to try this Expo Config Plugin. I've followed the directions like so:I have Expo SDK 45.I Installed expo-cli@4.4.4I Installed @intercom/intercom-react-native@3.0.4 I followed this article which explained how to get my keys and run it in the app with this import. import Intercom from '@intercom/intercom-react-native'; But I get this error: TypeError: null is not an object (evaluating 'IntercomEventEmitter.UNREAD_COUNT_CHANGE_NOTIFICATION') I searched this error and found a discussion where the only person who said they could get things to work ended up ejecting expo. This is something we are unwilling to do. If we cant get this to work we cant use intercom. Do I have to eject expo to get this to work?With this package installed, how do I access and initialize intercom?
We are seeing the following crashes on Android only when upgrading to Version 6 of the React Native SDK. iOS works fine: 1-07 12:50:31.668 21555 21555 D AndroidRuntime: Shutting down VM11-07 12:50:31.672 21555 21555 E AndroidRuntime: FATAL EXCEPTION: main11-07 12:50:31.672 21555 21555 E AndroidRuntime: Process: com.neuropeakpro, PID: 2155511-07 12:50:31.672 21555 21555 E AndroidRuntime: java.lang.IllegalStateException: No OnBackPressedDispatcherOwner was provided via LocalOnBackPressedDispatcherOwner11-07 12:50:31.672 21555 21555 E AndroidRuntime: at androidx.activity.compose.BackHandlerKt.BackHandler(BackHandler.kt:97)11-07 12:50:31.672 21555 21555 E AndroidRuntime: at androidx.navigation.compose.NavHostKt.NavHost(NavHost.kt:212)11-07 12:50:31.672 21555 21555 E AndroidRuntime: at androidx.navigation.compose.NavHostKt.NavHost(NavHost.kt:129)11-07 12:50:31.672 21555 21555 E AndroidRuntime: at io.intercom.android.sdk.m5.helpcenter.HelpCenterScreenKt.HelpCenter
Hello, I wanted to report to you a problem we faced recently.Our application is crashing when it's starting on iOS 13.We are using the Intercom SDK version 16.1.2.We installed this one with Cocoapod.It seems the SDK is referencing one Library that is available for iOS14+UniformTypeIdentifiershttps://developer.apple.com/documentation/uniformtypeidentifiersDid you also experience the same issue?I noticed the SDK should support iOS 13 in the podspec file: https://github.com/intercom/intercom-ios/blob/master/Intercom.podspecCrash log:Termination Description: DYLD, dependent dylib '/System/Library/Frameworks/UniformTypeIdentifiers.framework/UniformTypeIdentifiers' not found for '/private/var/containers/Bundle/Application/33855C68-5037-413A-B790-77EB65129A22/Qonto.app/Frameworks/Intercom.framework/Intercom', tried but didn't find: '/System/Library/Frameworks/UniformTypeIdentifiers.framework/UniformTypeIdentifiers' '/System/Library/Frameworks/UniformTypeIdentifiers.framework/UniformTypeIdenti
Integration with the sdk seems to work but when I navigate to the messaging screens it crashes immediately java.lang.NoClassDefFoundError: Failed resolution of: Landroidx/compose/ui/platform/LocalSoftwareKeyboardController; at io.intercom.android.sdk.m5.conversation.ui.ConversationScreenKt.ConversationScreenContent(ConversationScreen.kt:240) at io.intercom.android.sdk.m5.conversation.ui.ConversationScreenKt.ConversationScreen(ConversationScreen.kt:119) at io.intercom.android.sdk.m5.navigation.ConversationDestinationKt$conversationDestination$5.invoke(ConversationDestination.kt:79)
Hi, After updating to latest android sdk version (15.6.0), there's a crash when user clicks 'Send us a message' or 'Messages' Button. I attach crash logs below java.lang.NoClassDefFoundError: Failed resolution of: Landroidx/paging/Pager; at io.intercom.android.sdk.m5.inbox.InboxViewModel.<init>(InboxViewModel.kt:44) at io.intercom.android.sdk.m5.inbox.InboxViewModel.<init>(InboxViewModel.kt:30) at io.intercom.android.sdk.m5.inbox.InboxViewModel$Companion$factory$1.create(InboxViewModel.kt:109) at androi
I’m trying to find documentation on how to trigger a workflow from within the mobile app, more specifically when a specific page in my application is viewed. I see lots of information on how to build the flows, but I can’t seem to find any documentation on how to update my application to enable this.
When going through Xcode’s Organizer window you can see a breakdown of energy logs. In there Intercom-related calls and processes are listed as high impact.Here are couple of examples:48 seconds cpu time over 51 seconds (94% cpu average), exceeding limit of 80% cpu over 60 seconds 48 seconds cpu time over 59 seconds (81% cpu average), exceeding limit of 80% cpu over 60 seconds48 seconds cpu time over 59 seconds (81% cpu average), exceeding limit of 80% cpu over 60 secondsThe rest of the reports is quite similar in the stack traces and impact.Is there anything that Intercom could do to help with the battery impact? Maybe by exposing methods to stop listening for websocket messages? Some additional information:We’re utilizing bluetooth-central background execution mode to listen to BLE device, which means that the app in some circumstances may never go to terminated/suspended state App is built with Flutter Intercom SDK version used 16.3.0
