Mobile SDKs

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  

 Please help to check 

Using latest Android SDK with RN wrapper (tested 15.14.0 and 15.15.0), navigating to any article renders only an empty page (along with the emoji feedback footer). Video capture:https://www.dropbox.com/scl/fi/dqbc23sucijn5juajx9vd/intercom-android-article.mov?rlkey=ve8k12jphvlgizheo2qxr5bmv&dl=0

Hello! I’m the RN (react-native) developer and integrated your mobile SDK in my app for both platforms.  I used 8.6.0 version of this package RN-Intercom. I found a bug related to the launcher icon background color. This issue appears only in the current version. I tested the previous four versions, and the bug was not present in any of them. I double-checked the mobile SDK style configuration in the web settings, and everything looks correct to me.Important note:This issue occurs only on the first launch of Intercom in the app.I would be very grateful for a solution to this problem.

 Hi Intercom Support Team,We’re encountering a runtime crash in our Android application after integrating the latest version of the Intercom SDK.Although our app is developed using Kotlin with traditional View-based UI (not Jetpack Compose), the crash appears to be originating from Compose-related code within the Intercom SDK.Crash Details (from Firebase Crashlytics): java.lang.IllegalStateException: ViewTreeLifecycleOwner not found from android.widget.FrameLayout{654c395 V.E...... ........ 0,0-2171,1080 #7f0b04aa app:id/intercom_overlay_root viewInfo = } at androidx.compose.ui.internal.InlineClassHelperKt.throwIllegalStateExceptionForNullCheck(InlineClassHelper.kt:32) at androidx.compose.ui.platform.WindowRecomposer_androidKt.createLifecycleAwareWindowRecomposer(WindowRecomposer.android.kt:455) at androidx.compose.ui.platform.WindowRecomposer_androidKt.createLifecycleAwareWindowRecomposer$default(WindowRecomposer.android.kt:321)

Hey everyone,I'm running into a frustrating issue with the Intercom SDK (iOS and Android) and wondering if anyone has seen this before. Ever since switching to the Intercom SDK, I've noticed way fewer support requests coming in. At first I thought maybe that was a good thing, but then users started emailing me directly saying they can't access support through the app.The error they're seeing is "something's gone wrong. Content could not be loaded" - both in the messenger and when trying to view help articles. I've attached a screenshot from one Android user. The weird thing is that if they sign out and back in, it starts working again temporarily.I initially suspected JWT validation issues, so I disabled that completely for both iOS and Android, but the problem persists. When I contacted support about this, they suggested it might be network issues, but that doesn't make sense to me since signing out/in fixes it for that specific user.The really an

I recently updated my intercom version from v15.10.0 to v15.11.2 because my app started to crash whenever a user tries to type a message. After upgrading, my app crashes whenever a user opens a chat or tries to start a new chatError log for v15.10.0java.lang.IllegalArgumentException: offset(1) is out of bounds [0, 0] at androidx.compose.ui.text.MultiParagraph.requireIndexInRangeInclusiveEnd(MultiParagraph.kt:913) at androidx.compose.ui.text.MultiParagraph.getCursorRect(MultiParagraph.kt:748) at androidx.compose.ui.text.TextLayoutResult.getCursorRect(TextLayoutResult.kt:553)Error log for v15.11.2java.lang.Ill

Hi Intercom Support,I would like to report an issue encountered on Android devices when handling push notifications from Intercom. Specifically, the main application crashes upon tapping a push notification if the sender has an avatar (image_url is not empty).Reproduction Steps:Create a trial Intercom conversation. Configure the Intercom Android SDK with the app ID and push notification settings. Use the main app to initiate a first message to Intercom. From the Intercom admin interface, send a reply message from an agent account that has no avatar set (i.e., image_url is empty). Receive the push notification on the Android device and tap on it.Observed Behavior:If the sender has an avatar (image_url is set): Tapping the push notification opens the Intercom conversation. However, the main app proce

Howdy!We're experiencing this issue after updating from 3.x SDK to 4.0.1 (https://github.com/intercom/intercom-react-native react-native version: 0.70.5  Code sample (which is basically the same that you have in docs):  useEffect(() => { const subscription = Intercom.addEventListener( IntercomEvents.IntercomUnreadCountDidChange, (response) => { setCount(response.count); } );   return () => { try { subscription.remove(); } catch (e) { console.log(e); } }; }, []); Calling subscription.remove on line 11 during effect cleanup triggers an exception. Line 13 prints:[RangeError: Maximum call stack size exceeded]Without try/catch block the call just fails silently due to this -

Hello Intercom team,I am encountering a Gradle build error when integrating the intercom-react-native library into my React Native project. The issue seems related to an implicit task dependency conflict.Error details:A problem was found with the configuration of task ':intercom-react-native:copyDebugJniLibsProjectAndLocalJars' (type 'LibraryJniLibsTask').Gradle detected a problem with the following location: '[project path]/node_modules/@intercom/intercom-react-native/android/build/intermediates/stripped_native_libs/debug/stripDebugDebugSymbols/out'.Reason: Task ':intercom-react-native:copyDebugJniLibsProjectAndLocalJars' uses output from ':intercom_intercom-react-native:stripDebugDebugSymbols' without declaring a dependency.Attempted solutions: Cleaned Gradle build and cache. Added explicit task dependencies using afterEvaluate

Release Date: 03-07-2025 🐛 Bug Fixes Fixes a bug that could cause a crash when trying to resend a failed media message. Fixes a bug that could cause a crash during complex gradient background processing.

Hi guys, I am having problems to upgrade from expo 52 to expo 53 due to intercom issues.In version 8.0.0, ios is not working due to  ❌ (ios/TakenosDevelop/AppDelegate.swift:1:2)> 1 | #import <IntercomModule.h> | ^ no macro named 'import' 2 | import Expo 3 | import React 4 | import ReactAppDependencyProvider This is fixed on 8.5.0 but this version uses sentry Android SDK >= 8 and clashes with sentry-react-native that uses sentry Android SDK >=7.  I am using @sentry/react-native version 6.14.0(recommended by expo)Here is a conversation related to the issue on sentry github: https://github.com/getsentry/sentry-react-native/issues/4688The error i am seeing:Error: Exception in HostFunction: No d

Hello! We recently integrated Intercom into our iOS app (currently using Intercom 18.7.3 SDK for iOS). As I’ve been monitoring the releases, I have seen in the Xcode Organizer → Metrics → Memory a BIG spike in our app’s memory use. We have changed little in the app itself since integrating Intercom, so my investigation of the memory spike focused on Intercom.I started with the simplest exploration: use Instruments with the Allocations tool, Mark Generations, and see what happens. In my case, I tested our invocation of the Messages UX. Our app code in question looks like this (simplified): // In the ViewControlleroverride func tableView(_ tableView: UITableView, didSelectRowAt indexPath: IndexPath) { tableView.deselectRow(at: indexPath, animated: true) let action = self.sections[indexPath.section].rows[indexPath.row] switch action { case .emailfeedback: self.v

Here are the errors:  jetified-intercom-sdk-base-15.10.3-runtime.jar: D8: java.lang.NullPointerException: Cannot invoke "String.length()" because "<parameter1>" is nullWhat I’ve Tried: Checked build.gradle for SDK version compatibility Cleaned and rebuilt project (./gradlew clean && ./gradlew build) Searched through Intercom docs and changelogs Looked at open issues in the GitHub repo My Setup: React Native version: 072 Intercom SDK version: 15.10.3   Gradle: 8.0.1 Questions: Are these methods deprecated or moved to a different namespace? Is there a recommended way

*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[__NSArrayM insertObject:atIndex:]: object cannot be nil'*** First throw call stack:(0   CoreFoundation                      0x00000001804ae0f8 __exceptionPreprocess + 1721   libobjc.A.dylib                     0x0000000180087db4 objc_exception_throw + 562   CoreFoundation                      0x0000000180393044 -[__NSArrayM insertObject:atIndex:] + 12523   Intercom                            0x00000001060eb528 IntercomSDK_saveViewHierarchy + 4969884   Intercom                            0x00000001060eadec IntercomSDK_saveViewHierarchy + 4951365   Foundation                          0x0000000180d54084 -[NSObject(NSKeyValueCoding) setValuesForKeysWithDictionary:] + 1846   Int

We are encountering crashes on Android devices related to Intercom SDK version 15.9.1. Stack Trace:Failed to build unique file: /storage/emulated/0/DCIM/vr-unit.gif bucket_display_name=DCIM volume_name=external_primary date_modified=null date_expires=null _display_name=vr-unit.gif mime_type=image/gif _data=/storage/emulated/0/DCIM/vr-unit.gif _size=null is_trashed=0 is_pending=0 bucket_id=-2075821635 relative_path=DCIM/ android.content.ContentResolver.update (ContentResolver.java:2318)arrow_rightio.intercom.android.sdk.ui.preview.viewmodel.PreviewViewModel.saveImageOnApi29Above (PreviewViewModel.kt:201)io.intercom.android.sdk.ui.preview.viewmodel.PreviewViewModel.access$saveImageOnApi29Above (PreviewViewModel.kt:35)io.intercom.android.sdk.ui.preview.viewmodel.PreviewViewModel$saveImage$1.invokeSuspend (PreviewV