Mobile SDKs

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

We’re seeing the following log when running our iOS app:“Your app will be rejected from the AppStore unless you add NSCameraUsageDescription and NSMicrophoneUsageDescription to your Info.plist. More information is available here: https://developers.intercom.com/installing-intercom/ios/installation/#step-2---update-info.plist” The linked doc has no mention of these two usage descriptions. Are these still required?

Only my “Test workspace” crashes, the production one works fine.The code I’m calling is the following when opening the Help Center:Intercom.present(Space.helpCenter)--The uncaught exception that is being thrown is:Terminating app due to uncaught exception 'NSUnknownKeyException', reason: '[<IntercomSDKPrivate.ErrorViewController ...> setValue:forUndefinedKey:]: this class is not key value coding-compliant for the key closeImageView.'Which often means the `ErrorViewController.xib `(or storyboard?) had a property set in a XIB which longer exists in ErrorViewController.--The expected behaviour is that if an error needs to display (because I’m using a test workspace) that the error shows rather than the app crashing.

Hi,I use this sdk: https://github.com/intercom/intercom-ios-spversion: 16.2.1The issue - The SDK is leaking data!It seam like on each time I open a chat with a representative, the entire content is being downloaded, including images shared in that conversation. EACH TIME. So if I open a chat with image it will download the full size of the image.Close the window, reopen it again - the full image is downloaded again. This is problematic- we had a user that complain his cellular data plan was exhausted in matter of days.I've verified it by using Proxyman tool - sniffing the network and seeing it.I tried also a different app in my phone to see if it happens to them as well. It does (Wolt app).I’ve asked a support representative in private and his response was:“… I can confirm that's the expected behaviour for images in conversations. And at the moment, we don't have any alternatives to cache those images to optimise network data ...”Does anyone else exprience it?Does it make sense this is

Hi all,Could you please share your apps with integrated Intercom mobile SDK?I want to test user flow - how user reaches messenger in apps, how does it look like, and so forth.Would be great if you send screenshots, or if you share you mobile apps names - I will download and test it on my ownThank you  

We have Enabled Push Messaging being set to True or Unknown correctly when a user creates an account and opts in to notifications (True) or skips it (Unknown). However, if a user turn off notifications via their phone settings (not via the app) Enabled Push Messaging is not updated. How is this supposed to work?

Hello Intercom team,We are experiencing the following crash after updating to the latest Intercom SDK version 15.1.5.It happened on production on 3 users (for now), all of them on iOS 16 but on different devices.Are you aware of this crash / do you know where it can come from ?Thank you in advance,Have a good dayLogs coming from Firebase:1/2Crashed: com.apple.main-thread0 Intercom 0x2ab028 IntercomSDK_PINRemoteImageManagerSubclassOverridesSelector + 11445481 Intercom 0x2aae18 IntercomSDK_PINRemoteImageManagerSubclassOverridesSelector + 11440202 Intercom 0x2a9098 IntercomSDK_PINRemoteImageManagerSubclassOverridesSelector + 11364683 Intercom 0x2a9e14 IntercomSDK_PINRemoteImageManagerSubclassOverridesSelector + 11399204 CoreFoundation 0x37590 __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 1485 CoreFoundation 0xdb828 ___CFXRegistrationPost_block_invoke + 8

Dear Intercom Devs,After a new Intercom 15.0.2 SDK release, we have updated it on our end and released a new version of our app last week. Unfortunately, we started getting a new crashes from Intercom on Firebase. Here are the details of them.Crashed: nexus.reachability0  libobjc.A.dylib                0x3a7c objc_retain + 161  libobjc.A.dylib                0x3a7c objc_retain_x0 + 162  Intercom                       0x5d424 -[IntercomSDK_IntercomNexusSocket resetSocket] + 186763  Intercom                       0x5d4a0 -[IntercomSDK_IntercomNexusSocket reconnect] + 188004  Intercom                       0x5a5e0 -[IntercomSDK_IntercomNexusConnection reconnectSockets] + 68325  Network                        0x7f2e5c __nw_path_necp_update_evaluator_block_invoke + 4566  libdispatch.dylib              0x2320 _dispatch_call_block_and_release + 327  libdispatch.dylib              0x3eac _dispatch_client_callout + 208  libdispatch.dylib              0xb534 _dispatch_lane_serial_drain + 6689  l

We are using @intercom/intercom-react-native@4.0.1. The stack trace a user is running into is below. Can you let me know what the minimum version we need to upgrade to?java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String io.intercom.android.sdk.models.CustomizationColorsModel.getBackgroundColor()' on a null object reference at io.intercom.android.sdk.views.TextAttributeView.updateSubmitButtonColor(TextAttributeView.java:122) at io.intercom.android.sdk.views.holder.AttributeCollectorViewHolder.addAttributeView(AttributeCollectorViewHolder.java:115) at io.intercom.android.sdk.views.holder.AttributeCollectorViewHolder.renderAttributes(AttributeCollectorViewHolder.java:80) at io.intercom.android.sdk.views.holder.AttributeCollectorViewHolder.bind(AttributeCollectorViewHolder.java:57) at io.intercom.android.sdk.conversation.ConversationPartAdapter.onBindViewHolder(ConversationPartAdapter.java:234) at androidx.recyclerview.widget.RecyclerView$Ad

*Environment:*iOS 17.0.3, iPhone 11 Pro.*Steps to reproduce:*Open intercome chat Take a look at the partner icon*Actual result:*       

Updated to the (almost)latest react native intercom version a month ago. Pods are on 16.1.1.We get these crashes:IntercomSDK_MethodSwizzleEXC_BAD_ACCESS (KERN_INVALID_ADDRESS)Crashed: com.apple.NSURLSession-delegate0  libobjc.A.dylib                0x32f8 objc_release + 161  libobjc.A.dylib                0x32f8 objc_release_x0 + 162  Intercom                       0x5e904 IntercomSDK_MethodSwizzle + 94883  Intercom                       0x618bc IntercomSDK_MethodSwizzle + 217044  CFNetwork                      0x133c8 _CFNetworkSetHSTSStoragePath + 429045  libdispatch.dylib              0x26a8 _dispatch_call_block_and_release + 326  libdispatch.dylib              0x4300 _dispatch_client_callout + 207  libdispatch.dylib              0xb894 _dispatch_lane_serial_drain + 7488  libdispatch.dylib              0xc3f8 _dispatch_lane_invoke + 4329  libdispatch.dylib              0x17004 _dispatch_root_queue_drain_deferred_wlh + 28810 libdispatch.dylib              0x16878 _dispatch_workloop_w

iOS Intercom SDK: 15.0.3Steps: - Present the messenger view from source app `Intercom.present()`- Dismiss the Messenger viewIssue:  - When we dismiss the `Messenger View`, we see a white background for a second.We’ve been investigating this issue for past few days and require your support to close it.Note: Attaching the video for your reference. Thanks!