Mobile SDKs

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! 

I’m using Android SDK version 14.0.0 and I got this crash in intercom. Fatal Exception: java.lang.IllegalStateException: ViewTreeLifecycleOwner not found from android.widget.FrameLayout{61dc520 V.E...... ......ID 0,0-1080,2180 #7f0a0389 app:id/intercom_overlay_root}       at androidx.compose.ui.platform.WindowRecomposer_androidKt.createLifecycleAwareWindowRecomposer(WindowRecomposer.android.kt:349)       at androidx.compose.ui.platform.WindowRecomposer_androidKt.createLifecycleAwareWindowRecomposer$default(WindowRecomposer.android.kt:324)       at androidx.compose.ui.platform.WindowRecomposerFactory$Companion$LifecycleAware$1.createRecomposer(WindowRecomposer.android.kt:168)       at androidx.compose.ui.platform.WindowRecomposerPolicy.createAndInstallWindowRecomposer$ui_release(WindowRecomposer.android.kt:224)       at androidx.compose.ui.platform.WindowRecomposer_androidKt.getWindowRecomposer(WindowRecomposer.android.kt:299)       at androidx.compose.ui.platform.AbstractComposeView.re

If starting the app in CarPlay, Intercom causes the app to crash:[CPTemplateApplicationScene windows]: unrecognized selector sent to instanceTerminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[CPTemplateApplicationScene windows]: unrecognized selector sent to instance 0x103386dc0'terminating with uncaught exception of type NSException​Previously we haver setup Intercom in AppDelegate, but in preparation for CarPlay, we moved Intercom setup to SceneDelegate, as per the documentation.​Currently the only way to have Intercom be stable, is to uninstall the app and reinstall. But that user experience is terrible.

Hi, the SDK crash if I try to start a CarPlay app. The error is [CPTemplateApplicationScene windows]: unrecognized selector sent to instance 0x1228ef470 The error is thrown from login method: Intercom.loginUser(with: attributes, completion: nil)

We are encountering an issue where the messenger displays “Content could not be loaded” to newly created users in our app and initially calling loginUserWithUserAttributes method. After re-opening the app  the messenger works.Issue is only encountered in released versions (Test flight and App store) and we can’t replicate in debug/local.  

*Environment:*iOS 17.0.3, iPhone 11 Pro.*Steps to reproduce:*Open intercome chat Tap ‘send us a message’ Send twice message ‘hey’*Actual result:*The app crashes Fatal Exception: NSInternalInconsistencyExceptionFatal: supplied item identifiers are not unique. Duplicate identifiers: {( IntercomSDKPrivate.ConversationCollectionViewCellType.message(<ICMConversationPart: 0x1092344d0>) )}

We use the Intercom Client within our app for customer support. I’ve found some strange behaviour which may be a bug. The symptom is that pressing X to close the Intercom client appears to close the entire app under certain circumstances.To recreate:Open Intercom client from within our app.Navigate to an item such as a FAQ item which launches a page separately in the phone browser (Chrome in this case)Use the app drawer to switch back to the Intercom ClientPress X to close Intercom ClientThe client closes and the phone Home Screen is shownIt appears that the app is closed as well but if you were to go back to the browser and press back, our app appears there as if the Intercom Client has been disassociated from the [App → Client → Browser] stack.If I do not use the app drawer and just press Back from the browser, it all behaves as expected.Seen in Android SDK 15.0.0 and 15.5.0Was wondering if this a known bug or is there anything we can do with our integration to avoid this?

java.lang.ClassCastException: androidx.compose.animation.AnimatedContentTransitionScopeImpl cannot be cast to androidx.compose.animation.AnimatedContentScope at com.google.accompanist.navigation.animation.AnimatedNavHostKt$AnimatedNavHost$7$1.invoke(AnimatedNavHost.kt:198)This is due to Compose animation change in Compose 1.5Instead of using `AnimatedContentScope` Intercom needs to update and use `AnimatedContentTransitionScope`

I was able to trigger a workflow from my mobile application based on a logEvent that shows in the form of a popup notification to the user. This requires the user to click on that popup, which opens the messenger, then the user can interact with the rest of the workflow. Is it possible to trigger a workflow which shows the message within the Intercom messenger, not within a popup?For example: I have a button in my mobile app. When the user taps that button, I would like to show the messenger with a workflow. Is that possible? If so, can you point me in the right direction? Thanks!

Hello,We've recently enabled in-app messages using setInAppMessagesVisible in our iOS app. However, we've noticed that messages in English appear to be right-aligned in the small post popup. Is there a way to control the text alignment (RTL/LTR) for these in-app messages based on the text language?Your assistance is greatly appreciated.Best regards,

Hey there, first I'd like to give a s/o to the creator of the Expo config plugin for Intercom here, and say that this is something the Intercom could pickup as well ;) That said, the way the RN SDK is initialized is thru the native code in both Android and iOS, and unless I am mistaken, there is no way to initialize it from the SDK itself. Would be good to have a way to start it programmatically from the code as right now it is required for us to provide the API keys at build time and this makes it much harder to load those keys dynamically for example at our CI workflows. Since the RN SDK is a wrapper of the native libraries, I could recommend to follow the approach that Segment and Sentry used on their SDKs as those also are wrappers and allow the initialization to be done at run time. Thank you!

Not able to present overCurrentContext. Need ModalPresentationStyle Support   

Hello, The Intercom iOS SDK (16.2.2) is configured and integrated as per the documentation steps. Everything works except the Push Notifications.The push notifications are receiving both within the app and when it’s in background. But once you tap on the notification, you’re presented with an empty Intercom’s conversation modal screen.Tested it on iOS 16 and iOS 17 devices.What could be the reason? 

Another way of asking this question is: Is the result of loginIdentifiedUser() persisted across app launches and device reboots?My assumption is that I only need to call this method once when my user logs in to my app and I need to call logout() when the user logs out. I don’t need to worry about updating a registration each time the app launches.However, this section in the docs are throwing me off. It asks to call loginIdentifiedUser() twice: Once on successful login (private fun successfulLogin()) and again “anywhere they sign in”. Is this second call supposed to be when we relaunch the app and detect that the user is logged in or not?