Mobile SDKs

I'm upgrading to React Native 0.77.2 and using Intercom SDK version @intercom/intercom-react-native 8.5.0. While most features work correctly, the app freezes and crashes on iOS after I open an in-app Intercom message and tap either the close button or interact with a Reaction within the message. Reproduction Steps Launch the app on iOS. Trigger an in-app Intercom message. Tap the "Close" button or interact with a React component rendered within the message. App becomes unresponsive and eventually crashes (ANR).  Relevant Logs (Xcode + Sentry)  Sentry Breadcrumbs show lifecycle events for multiple Intercom-related view controllers: ICMNoteViewController

Hi. We have a crash in our app when pushing a survey to some of our users. We are using version 17.1.0 (latest)This is the crash log → io.intercom.android.sdk.survey.SurveyViewModel.buildContentState (SurveyViewModel.kt:215)io.intercom.android.sdk.survey.SurveyViewModel.access$submitSurvey (SurveyViewModel.kt:83)io.intercom.android.sdk.survey.SurveyViewModel.access$buildContentState (SurveyViewModel.kt:83)io.intercom.android.sdk.survey.SurveyViewModel$submitSurvey$1.invokeSuspend (SurveyViewModel.kt:388)kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith (ContinuationImpl.kt:34)kotlinx.coroutines.DispatchedTask.run (DispatchedTask.kt:100)kotlinx.coroutines.internal.LimitedDispatcher$Worker.run (LimitedDispatcher.java:124)kotlinx.coroutines.scheduling.TaskImpl.run (Tasks.kt:89)kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely (CoroutineScheduler.java:586)kotli

Fatal Exception: java.lang.IllegalArgumentExceptionKey "" was already used. If you are using LazyColumn/Row please make sure you provide a unique key for each item. This is the crash, all I can see in firebase is that we have a screen viewed event for “firebase_screen_class: IntercomRootActivity” and then the crash. I’m on 17,1.0

HelloAfter upgrading my app to Expo SDK 53 (React Native 0.79), the iOS build fails when using @intercom/intercom-react-native.Error message:❌  (ios/Tikin/AppDelegate.swift:1:2)> 1 | #import <IntercomModule.h>    |  ^ no macro named 'import'  2 | import Expo  3 | import React  4 | import ReactAppDependencyProvider› 1 error(s), and 3 warning(s)This line appears in the generated AppDelegate.swift:#import <IntercomModule.h>But #import is not valid in Swift files — this causes the build to fail.Environment: Expo SDK: 53 React Native: 0.79 @intercom/intercom-react-native version: [insert version if known] Build: EAS Build for iOS

We have recently implemented the SDK in our iOS app. Everything works fine but some users report that content can not be loaded? Not sure what is causing this?  

When trying to log event with `Intercom.client().logEvent` I’m displaying the survey with intercom, the ui contains close button in the right top corner. When try dismissing it with “back” navigation, I go back and then being brought again into the intercom window. Is there a way to dismiss the intercom window? Intercom.client().hideIntercom() does not seem to work

Hi,We added the Intercom Android SDK into our app.implementation 'io.intercom.android:intercom-sdk:15.6.3'When clients click these auto-reply conversations, the app crashed: Recently, we received many crash report:Parameter specified as non-null is null: method io.intercom.android.sdk.m5.conversation.states.ConversationHeaderV2.<init>, parameter subtitle Did some nearby updates at the back-end removing the ‘subtitle’ parameter? I tested with all 15.6.* version SDKs and they all have this problem.  Starting from SDK 16, a targetSDK version of 35 is required. Migrating our app to 35 will take a significant amount of time, and app crashes severely

Hi there,The latest version of React Native, 0.77.0, migrates the iOS AppDelegate to Swift. Currently the intercom-react-native module only seems to support set up in Objective C, will this be changing soon?Many thanks, Lydia

I am getting a crash when using the Android SDK via a Flutter-based application. This crash is occurring on a Pixel 8 running Android 14.intercom_flutter 8.1.1 This uses Android SDK 15.6.3 Also tested against intercom 8.0.9, which uses SDK 16.5.1 Built using minSdkVersion 21, compileSdkVersion being Flutter’s compile SDK version.  Java compatibility set to JavaVersion.VERSION_1_8This crash occurs when clicking to access recent messages.E/AndroidRuntime(32192): java.lang.NullPointerException: Parameter specified as non-null is null: method io.intercom.android.sdk.m5.conversation.states.ConversationHeaderV2.<init>, parameter subtitleE/AndroidRuntime(32192):     at io.intercom.android.sdk.m5.conversation.states.ConversationHeaderV2.<init>(Unknown Source:8)E/AndroidRuntime(32192):     at io.intercom.android.sdk.m5.conversation.reducers.HeaderReducerKt.reduceHeaderV2(HeaderReducer.kt:48)

We’re using Intercom Android SDK 15.1.3. We use the Intercom.client().present() API to show the help center in our app.Our app currently requires READ_EXTERNAL_STORAGE permission and the only reason for this permission is for Intercom’s image attachments feature.From Android documentation, on API 33, READ_EXTERNAL_STORAGE is replaced with more granular permissions like READ_MEDIA_IMAGES etc. However, it also states that you can use the PhotoPicker to get the same behaviour without any permissions; and with the jetpack library PhotoPicker is available all the way back to API 19.My question is: Does Intercom Android SDK use PhotoPicker? What about on pre-API 33?The only reference to this I see is in the

Fatal Exception: java.lang.IllegalArgumentException: Missing keys: [timestamp] in '{teammate} moved ticket into {status} {timestamp}'       at io.intercom.android.sdk.utilities.Phrase.format(Phrase.java:189)       at io.intercom.android.sdk.m5.notification.InAppNotificationCardKt.TicketInAppNotificationContent(InAppNotificationCard.kt:180)       at io.intercom.android.sdk.m5.notification.InAppNotificationCardKt.InAppNotificationCard(InAppNotificationCard.kt:124)       at io.intercom.android.sdk.m5.notification.InAppNotificationCardKt$addInappNotificationCardToView$1$1$1.invoke(InAppNotificationCard.kt:75)       at io.intercom.android.sdk.m5.notification.InAppNotificationCardKt$addInappNotificationCardToView$1$1$1.invoke(InAppNotificationCard.kt:74)       at androidx.compose.runtime.internal.ComposableLambdaImpl.invoke(ComposableLambda.jvm.kt:109)       at androidx.compose.runtime.internal.ComposableLambdaImpl.invoke(ComposableLambda.jvm.kt:3

Android API 36 is ignoring the orientation configuration. The Android SDK is fixing the orientation as portrait. We have got the following warning on Google Play: From Android 16, Android will ignore resizability and orientation restrictions for large screen devices, such as foldables and tablets. This may lead to layout and usability issues for your users.We detected the following resizability and orientation restrictions in your app:<activity android:name="io.intercom.android.sdk.activities.IntercomCarouselActivity" android:screenOrientation="PORTRAIT" />To improve the user experience for your app, remove these restrictions and check that your app layouts work on various screen sizes and orientations by testing on Android 16 and below.Would it be possible to avoid orientation restrictions in the SDK?

Hello, I’m experiencing a problem where the Intercom chat does not open when a user taps on a push notification on iOS. I have implemented the Intercom React Native plugin as per the documentation, and the messaging functionality works perfectly. Notifications are received correctly, but tapping on them does not open the chat as expected. Environment Details: • Platform: iOS• React Native Version: 0.74• Intercom React Native Plugin Version: 8.1.0 Problem Description: • The Intercom messenger is fully integrated into my app, and users can send and receive messages without any issues.• Push notifications from Intercom are successfully delivered to the device.• According to the documentation, tapping on a push notification should automatically open the relevant chat within the app. However, this is not hap

Hello, I need to integrate Intercom into react-native app. I’m using official wrapper intercom/intercom-react-native. Android works as expected. On iOS I’m always getting `BadDeviceToken` listed as an issue in Intercom panel (website). I tried both ways to send the token to the intercom, first is native code (option 2 from here) and later tried JS option with token coming from @react-native-firebase/messaging `getToken` method.APN configuration is uploaded to Intercom and same values works properly when sending push messages from Firebase (both their website and java/nodejs SDK).I’m testing on the simulator (again messages from Firebase and our backend works fine).

Recently, we have a lot of Fatal Exception: Java.lang.illeglegalstateexception.v15.15.0 and v16.3.0I attach the entire stack trace errors:          Fatal Exception: java.lang.IllegalStateException: The specified child already has a parent. You must call removeView() on the child's parent first.       at android.view.ViewGroup.addViewInner(ViewGroup.java:5401)       at android.view.ViewGroup.addView(ViewGroup.java:5216)       at android.view.ViewGroup.addView(ViewGroup.java:5156)       at android.view.ViewGroup.addView(ViewGroup.java:5128)       at androidx.compose.ui.viewinterop.AndroidViewHolder.<init>(AndroidViewHolder.android.kt:99)       at androidx.compose.ui.viewinterop.ViewFactoryHolder.<init>(AndroidView.android.kt:332)       at androidx.compose.ui.viewinterop.ViewFactoryHolder.<init>(AndroidView.android.kt:323)       at androidx.compose.ui.viewinterop.ViewFactoryHol

In our app we are sending Intercom Posts with universal links in them and opening a link from a post within the app does both - triggers the deeplink action and also opens Safari. In our AppDelegate we return true from application:continueUserActivity:restorationHandler: and even when we completely remove all deeplink related logic and the method contains nothing but return true it still opens Safari, this behavior contradicts to what's written here. We have IntercomUniversalLinkDomains configured in the Info.plist file. Expected behavior: Do not open Safari when a url is matched with an entry from IntercomUniversalLinkDomains  and application:continueUserActivity:restorationHandler: returns true.iOS SDK versio

Seeing a new crash on Samsung Galaxy S24 Ultra (in the field)  Android 15At least 3 different users all with this same device.  java.lang.IllegalStateException (crashed)ViewTreeLifecycleOwner not found from android.widget.FrameLayout{ff120ae V.E...... ........ 0,0-1080,2340 #7f0a04d4 app:id/intercom_overlay_root}androidx.compose.ui.internal.InlineClassHelperKt.throwIllegalStateExceptionForNullCheck (SourceFile:34)androidx.compose.ui.platform.WindowRecomposer_androidKt.createLifecycleAwareWindowRecomposer (SourceFile:455)androidx.compose.ui.platform.AbstractComposeView.ensureCompositionCreated (SourceFile:250)androidx.compose.ui.platform.AbstractComposeView.onMeasure (SourceFile:285)android.view.View.measure (View.java:29591)android.view.ViewGroup.measureChildWithMargins (ViewGroup.java:7383)android.widget.FrameLayout.onMeasure (FrameLayout.java:207)android.view.View.measure (View.java:29591)android.vie

Hello Intercom Team,We are using @intercom/intercom-react-native for in-app support, which is a core feature of our app. Users often need to attach screenshots when contacting support.According to the official documentation, the SDK requires storage permission. On Android 13+, this maps to READ_MEDIA_IMAGES.However, Google Play has rejected our app, even after appeal, because this permission is considered sensitive. They are asking us to justify its usage, and one-time photo pickers are not accepted since the Intercom SDK manages its own gallery internally.This is now blocking our app release. We saw

This was reported 4 years ago in another post here:and supposed to have been fixed in Intercom’s iOS SDK 17.0.4:but unfortunately we’re seeing it again. This started happening after we turned on push notification integration for our app, and seems related to calling Intercom.setDeviceToken when iOS gives us an APNS token.In case it’s relevant, we have IntercomAutoIntegratePushNotifications turned off because it caused problems with Firebase Cloud Messaging’s similiar swizzling. 

My Flutter application has reported a crash in the Google Play Console. The crash is a java.lang.RuntimeException with an underlying ClassNotFoundException, specifically because the Android runtime is unable to find the io.maido.intercom.PushInterceptReceiver class.Crash Stack Trace (Core):Fatal Exception: java.lang.RuntimeException: Unable to instantiate receiver io.maido.intercom.PushInterceptReceiver: java.lang.ClassNotFoundException: Didn't find class "io.maido.intercom.PushInterceptReceiver" on path: DexPathList[...]My Project Configuration:  Intercom Plugin Version: intercom-android: 17.0.2 ProGuard/R8 Rules: I have already added a keep rule for the Intercom SDK in my proguard-rules.pro file: -keep class io.intercom.android.** {

Hi team,I'm using @intercom/intercom-react-native with Expo bare workflow and the plugin is generating hardcoded API keys in my AppDelegate.swift Is there a proper way to configure the plugin to use environment variables at runtime rather than hardcoding them during build? I want to avoid committing secrets to my repository.Thanks!

Despite the fact that mobile SDK does not support dark mode, the articles and some parts of the help center use dark mode features. SDK Android 16.3.0 (changelog) iOS 18.8.0 (changelog)    

Fatal Exception: java.lang.IllegalArgumentException: Missing keys: [timestamp] in '{teammate} moved ticket into {status} {timestamp}'       at io.intercom.android.sdk.utilities.Phrase.format(Phrase.java:189)       at io.intercom.android.sdk.m5.notification.InAppNotificationCardKt.TicketInAppNotificationContent(InAppNotificationCard.kt:180)       at io.intercom.android.sdk.m5.notification.InAppNotificationCardKt.InAppNotificationCard(InAppNotificationCard.kt:124)       at io.intercom.android.sdk.m5.notification.InAppNotificationCardKt$addInappNotificationCardToView$1$1$1.invoke(InAppNotificationCard.kt:75)       at io.intercom.android.sdk.m5.notification.InAppNotificationCardKt$addInappNotificationCardToView$1$1$1.invoke(InAppNotificationCard.kt:74)       at androidx.compose.runtime.internal.ComposableLambdaImpl.invoke(ComposableLambda.jvm.kt:109)       at androidx.compose.runtime.internal.ComposableLambdaImpl.invoke(ComposableLambda.jvm.kt:3

I'm trying to install the iOS SDK and have been following the provided guide. However, when I click the "Check Installation" button at the end, it doesn't seem to register as installed. I'm currently using Xcode 16.4 with an iOS 18.5 simulator.I noticed that the SDK's README mentions Xcode 15 as a requirement. Is this version required only for installation, or is it also necessary for Intercom to function correctly? Additionally, will support for Xcode 16 be available soon?This could be a blocker for us, as Xcode 15 isn't compatible with macOS Sequoia 15.5. 

Intercom is showing the notifications behind the navigation bar in Android 15+ even using latest SDK version and latest compose BOM