Mobile SDKs

In Android SDK version 15.7.1, the "Recent Message" and "Start Conversation" sections fail to appear on the Home Page when the device's language is set to Turkish.Screenshots are attached, taken on the same device, demonstrating the issue by only changing the language setting.Could anyone help us identify the potential cause of this problem or suggest any solutions? Any advice or insights would be greatly appreciated. 

I'm seeking assistance with a problem we've encountered after updating our application to Android SDK version 15.8.x. Previously, under SDK version 15.7.1, users were able to take photos and send them as attachments without any issues. However, following the upgrade to SDK 15.8.x, the functionality to take and send photos as attachments no longer works. This issue has been observed across devices running Android Version 14.Could anyone help us identify the potential cause of this problem or suggest any solutions? Any advice or insights would be greatly appreciated.

When submitting our app to App Store Connect I am still receiving some warnings about missing required reasons. Using the binary-based scanner script located here I am seeing the following:Used symbols in binary ./Debug.app/Frameworks/Intercom.framework/Intercom: NSFileCreationDate, NSFileModificationDate, NSFileSystemFreeSize, NSFileSystemSize, NSURLContentModificationDateKey, NSURLCreationDateKey, NSUserDefaults, statLooking at the Intercom PrivacyInfo.xcprivacy as of version 17.0.0 I see entries for UserDefaults and SystemBootTime, but not FileTimestamp even though the script shows there are references within the framework to NSFileCreationDate, NSFileModificationDate, NSURLContentModificationDateKey, NSURLCreationDateKey and stat.Is this something you are aware of? Do you intend to add the appropriate reason to your privacy manifest?Thanks!

I've noticed that carousels (the automatic ones, meaning one controlled by our marketing team triggered based off user properties) render in our android app before app loading is completed. When app loading does complete, they dismiss themselves. So, they become basically unusable.We use the react native SDK.I didn't see any methods that I could use to control the lifecycle to disable it until app loading has completed. I don't want to have to rely on programmatically launching them since it kind of limits our growth team's capabilities.Any recommendations? I know that there’s a way to manually show articles by using the ID, but I’d love to be able to use this out-of-the-box platform-y set up that can enable our marketing team to use articles without engineering’s involvement. Haven’t been able to figure out from the documentation whether there’s a way to control the lifecycle.

I am unable to run any lldb debugger commands with intercom because I get the following error: warning: Swift error in scratch context: error: compiled module was created by a different version of the compiler '5.9.0.128.108'; rebuild 'Intercom' and try again: Intercom Aside from this, the app builds fine. Its just super annoying because I can no longer debug I am using Intercom 16.6.0

Hello Intercom Team. On iOS, since Friday April 5th, we are experiencing the following error when trying to add Intercom dependency through Swift Package Manager. We are using the last version of the SDK. 17.0.0Error:```xcodebuild: error: Could not resolve package dependencies:checksum of downloaded artifact of binary target 'Intercom' (5ed58eb8dd4392896a2b3e56c5c66fd862c2f3d29fb6d575d6a98a276cf944f7) does not match checksum specified by the manifest (d874522d04ed130894ca7026021151465b1d5a77fdb96a7ba905aea36260dce3)```Thanks in advance.

It seems that the new Intercom SDK is not working on Android Lollipop as there’s no minSdkVersion field in the ApplicationInfo class. This happened after the DeviceUtils.getAppMinSdkVersionVersion method was added in 15.6.2.Fatal Exception: java.lang.NoSuchFieldError: No instance field minSdkVersion of type I in class Landroid/content/pm/ApplicationInfo; or its superclasses (declaration of 'android.content.pm.ApplicationInfo' appears in /system/framework/framework.jar) at io.intercom.android.sdk.utilities.commons.DeviceUtils.getAppMinSdkVersionVersion(DeviceUtils.java:32) at io.intercom.android.sdk.metrics.MetricTracker.<init>(MetricTracker.java:608) at io.intercom.android.sdk.metrics.MetricTracker.<init>(MetricTracker.java:597) at io.intercom.android.sdk.Injector.getMetricTracker(Injector.java:249) at io.intercom.android.sdk.Injector.getOverlayPresenter(Injector.java:272) at io.intercom.android.sdk.Injector.getResetManager(Injector.java:

Whenever we schedule a post from Intercom, user receives a push notification and opening it leads to a crash.It was working before we updated Intercom to 17.0.0, previous version we were on was 16.5.5. We are wondering if it's related to the change introduced in 16.6.0.iOS version we tested with: iOS 17.3.1, 17.4.1, 17.5Here's the stack trace: Last Exception Backtrace:0 CoreFoundation 0x1949cbf24 __exceptionPreprocess + 164 (NSException.m:249)1 libobjc.A.dylib 0x18c862018 objc_exception_throw + 60 (objc-exception.mm:356)2 Foundation 0x193897fe8 -[NSConcreteMutableAttributedString initWithString:attributes:] + 356 (NSAttributedString.m:1029)3 Intercom 0x105be84fc -[ICMActionButton initWithTitle:style:backgroundColor:foregroundColor:] + 3764 Intercom 0x105be82c4 -[ICMActionButton initFilledButtonWithTitle:] + 1405 Intercom 0x105c3cd24 -[ICMClosedConversationVie

All xcFrameworks on Intercom github have invalid signature hence apps using Intercom SDK can not compile at all  

Fatal Exception: android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.intent.action.VIEW dat=https://example.com/... } at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:2031) at android.app.Instrumentation.execStartActivity(Instrumentation.java:1686) at android.app.Activity.startActivityForResult(Activity.java:4506) at androidx.activity.ComponentActivity.startActivityForResult(ComponentActivity.java:780) at android.app.Activity.startActivityForResult(Activity.java:4464) at androidx.activity.ComponentActivity.startActivityForResult(ComponentActivity.java:761) at android.app.Activity.startActivity(Activity.java:4829) at android.app.Activity.startActivity(Activity.java:4797) at io.intercom.android.sdk.blocks.messengercard.MessengerCardWebViewInterface.openUrl(MessengerCardWebViewInterface.java:141) at io.intercom.android.sdk.blocks.messengercard.MessengerCardWebVie

I’m writing a SwiftUI app. I need to detect when user close an Intercom window.Is that even possible?

We’ve been getting crash reports that the app is failing to start on iOS 16. Upon further investigation, we got to this stack trace. You can see that the culprit seems to be a method swizzling you’re doing on applicationDidFinishLaunching. We’ve already tried to opt out of swizzling by setting IntercomAutoIntegratePushNotifications in Info.plist but no luck. 

Hello, I’m trying to integrate Intercom push notifications into my react-native app. I’m using official wrapper in version 6.8.1 (most up to date one). I did all of the steps from iOS setup section and configured Push Notifications on intercom website - https://app.intercom.com/a/apps/myapp/settings/ios. I’m sure that uploaded .p8 key, bundle id, key id and apple team id are correct because I uploaded the same version to firebase console and I’m able to send notifications from there and using their HTTP API. On intercom I’m all the time getting BadDeviceToken. On Android everything works properly. Am I missing something on iOS? I tried both ways of sending token to Intercom - javascript version and Obj-C version.For js version I’m using `@react-native-firebase/messaging` and call `await messaging().getToken()`. Using this token I’m getting BadDeviceToken 

Intercom Android sdk 2.17.0 adds the support to voice to text input in Messenger.There is a bug on clicking on the new microphone button, a warning message with unexpected title appears. And the description of the message suggests to enable a permission not present in our application.Is it possible to deactivate the feature voice to text input? 

Please, do not call UIApplication.shared.registerForRemoteNotifications() inside Intercom iOS SDK.This causes application(_:didRegisterForRemoteNotificationsWithDeviceToken:) to be called twice if you call registerForRemoteNotifications when you need in you app.I can’t disable this. Also IntercomAutoIntegratePushNotifications: NO don’t disable registerForRemoteNotifications() call.

Current behavior:When tapping a deep link from within a conversation inside of the Intercom messenger, the modal is not closed, but the navigation is still happening in the background. Expected behavior:When tapping a deep link from within a conversation inside of the Intercom messenger, the Intercom modal should close, and the app should handle the navigation. Notes:This issue was not happening on version 5.1.2.It’s affecting only iOS.Tested on the following versions:https://github.com/intercom/intercom-react-native/releases/tag/5.3.1https://github.com/intercom/intercom-react-native/releases/tag/6.1.0

When I integrate intercom sdk 15.0.1 or higher, my application will crash immediately upon launch without calling any command from intercom.From SDK version 15.0.0 and earlier, the problem does not occur.Crash log image as attached file.Hope everybody help please 

Hello,I am using the React Native SDK.Since the last upgrades (from 4 to 6), I get this type of error when calling Intercom.sendTokenToIntercom in JS side. WARN [Error: Error in sendTokenToIntercom] ERROR Invariant Violation: No callback found with cbID 31610 and callID 15805 for IntercomModule.sendTokenToIntercom - most likely the callback was already invoked. Args: '[true]', js engine: hermesI did : - Full cleaning of cache (node_modules, xcode...etc)- downgrading from 4 to 6.0.1.No success.I don’t know if it comes after upgrades of another packages.But the rest works well (messenger...etc). Except this call.If you have any idea?​​​​​​​Thank you ! React Native 0.72.5Xcode 15iOS 17

Hi IntercomI installed @intercom/intercom-react-native with my expo sdk, working on iOS.I used expo prebuild to be able to add intercom following the installation instruction provided for iOS, and it’s working correctly using iOS simulator or a dev environment.But when we distributed the release using Testflight, the app crash while initializing Intercom. It is not happening when we deactivate intercom.Please find below my settings : Package.json{ "dependencies": { "@expo/webpack-config": "^0.17.2", "@gorhom/bottom-sheet": "^4", "@hookform/resolvers": "^2.9.10", "@intercom/intercom-react-native": "^5.1.0", "@notifee/react-native": "^7.8.0", "@react-native-async-storage/async-storage": "^1.17.11", "@react-native-community/datetimepicker": "6.5.2", "@react-native-firebase/app": "18.0.0", "@react-native-firebase/messaging": "18.0.0", "@react-navigation/material-bottom-tabs": "^6.2.15", "@react-navigation/native": "^6.1.1", "@react-navigation/native-sta

I updated in my application the sdk from version 15.0.0 to the newest version 15.7.0 and I notice that I’m getting crash when I open my application by deep link and then by pressing back button. The crash: I notice that the handleExtras method was added in version 15.1.3  and there is bug:  activity.getIntent() can return null and than it throw NPE Please add null checking to avoid crashing users applications:Intent intent = activity.getIntent();if (intent == null){ return;}String instanceId = intent.getStringExtra(.... 

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.