Mobile SDKs

Since the upgrade to 9.*.* of version for React Native Intercom (https://github.com/intercom/intercom-react-native), we can no longer build and compile our Expo React Native app for iOS.Somehow the Intercom upgrade introduces a failure where C++ files are not correctly mapped during compiling. This is only when combined with other packages (in our case UserCentrics for RN).It is important to highlight that although other third party apps are involved, Intercom’s upgrade breaks the building process. Compiling fails with: 13 | 14 | #ifndef __cplusplus> 15 | #error This file must be compiled as Obj-C++. If you are importing it, you must change your file extension to .mm. | ^ This file must be compiled as Obj-C++. If you are importing it, you must change your file extension to .mm. 16 | #endif 17 | 18 | // Avoid multiple includes of IntercomReactNativeSpec symbolsand 'optional' file not found'tuple' file not found'utility' file not foundI’ve added a minimal reproducible

When using `Intercom.presentContent(.article(id: articleId))` with the current version of the iOS SDK (19.3.0), the app presents an empty view for a second or two and then crashes after outputting the following.*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[IntercomSDKPrivate.ArticleHostingController setContentDelegate:]: unrecognized selector sent to instance 0x12aeec000'*** First throw call stack:(0x1863e28c8 0x1833597c4 0x18647e838 0x18cfb1484 0x18635f4f8 0x1863673a0 0x10915b2f4 0x18645dd64 0x10913e12c 0x10787c63c 0x1078962d0 0x1078b74c0 0x10788c778 0x10788c6b4 0x186384520 0x186336d14 0x186335c44 0x225726498 0x18bcb0ddc 0x18bc55b0c 0x18bd91860 0x10bad5448 0x10bad53bc 0x10bad7308 0x1833aee28)Exception received: NSInvalidArgumentException - -[IntercomSDKPrivate.ArticleHostingController setContentDelegate:]: unrecognized selector sent to instance 0x12aeec000 

Hi Intercom team, we receive several errors after trying to login a user with attributes using react-native sdk.We check if the user is logged in before making a Intercom.loginUserWithUserAttributes call.A short stack-trace for the error we receive: code: 102,domain: io.intercom.ios.error.network,message: Error in loginUserWithUserAttributes,name: Error,NSLocalizedDescription: HTTP Error: 400 bad requestWe send email and userId to the method call, like this: Intercom.loginUserWithUserAttributes({ email, userId }) Could you help us understand why we still get an error, I’ve run a console.log for both email and userId and both seem legit.

On the intercom landing page, we have some pinned articles. If you open the pinned article, and try to tap the "X" button, it will not close the article. However, swiping down will still allow you to close that article. This behavior only occurs on iOS - it does not occur on Android.Some notes:If you go from the landing page and select the "Help" to go to the collection of articles (rather than the pinned article on the landing page), then those articles CAN be closed via the "X" button. This behavior occurred on the latest react native SDK version, 19.1.2 We checked and found we had to regress to 19.0.3 to resolve the problem - however we cannot use this older version, otherwise we will lose the iOS 26 changes.

Can I please have a code sample on how to implement dark mode (or switch themes) for Android. E.g. something likeimport io.intercom.android.sdk.ui.theme.ThemeMode;Intercom.client().setThemeMode(ThemeMode.DARK);I noted that Dark Mode was enabled on Android SDK v17.0.0

The 19.3.0 release introduced a bug where opening articles could sometimes crash, reported here. That was fixed in 19.3.1, but at the same time or possibly earlier, it seems another issue was introduced and the articles now aren’t loading at all.When calling Intercom.presentContent(.article(id: “123456”)), while the app no longer crashes, I’m instead stuck on a blank screen that can’t be dismissed.The close button on that page also does not do anything. I believe this bug was introduced with version 19.2.0. It has already been reported multiple times, but seemingly with little response, here and here.

Fatal Exception: java.net.MalformedURLException: unknown protocol: content at java.net.URL.<init>(URL.java:608) at java.net.URL.<init>(URL.java:498) at java.net.URL.<init>(URL.java:447) at io.intercom.android.sdk.ui.preview.ui.PreviewUriKt$loadFilesAsBitmaps$1$1.invokeSuspend(PreviewUri.kt:252) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:101) at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:113) at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:89) at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:589) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:823) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:720) at kotlinx.coroutines.scheduling

Hi Intercom team,After updating our app to Intercom iOS SDK 19.2.1, several developers on our team started facing issues where Swift methods (like loginUser(with:), logout(), etc.) are no longer properly inferred or recognized by the compiler.Details Integration: Swift Package Manager (official repo intercom-ios-sp) Project type: Pure Swift (no Objective-C bridging) Issue: For some developers, Xcode shows only Objective-C versions of methods (e.g. loginUserWithUserAttributes:success:failure:). Error: Cannot infer type of function call or No exact matches in call to function 'loginUser' Behavior: Happens inconsistently across machines — some developers see the correct Swift interface and can compile fine, others cannot. We already tried: Clearing DerivedData & SPM caches Re-adding the Intercom package Confirmed same SDK version (19.2.1) Still, the issue reappears randomly on some environments  ObservationWhen we “Jump to Definition,” for working setups i

Fatal Exception: java.lang.NoSuchMethodError: No virtual method close()V in class Landroid/media/MediaMetadataRetriever; or its super classes (declaration of 'android.media.MediaMetadataRetriever' appears in /system/framework/framework.jar) at io.intercom.android.sdk.m5.conversation.utils.URIExtensionsKt.getVideoData(URIExtensions.kt:146) at io.intercom.android.sdk.m5.conversation.utils.URIExtensionsKt.getMediaData(URIExtensions.kt:51) at io.intercom.android.sdk.m5.conversation.ui.ConversationScreenKt.ConversationScreen$lambda$29(ConversationScreen.kt:286) at io.intercom.android.sdk.m5.conversation.ui.ConversationScreenKt.$r8$lambda$l4hfoRjJBkYl_jEYY6YWj7rurp4() at io.intercom.android.sdk.m5.conversation.ui.ConversationScreenKt$$ExternalSyntheticLambda2.invoke(D8$$SyntheticClass) at io.intercom.android.sdk.m5.conversation.ui.ConversationScreenKt$ConversationScreenContent$35.invoke$lambda$3$lambda$0(ConversationScreen.kt:572) at io.intercom.and

We are using Intercom React Native 7.1.0 (Intercom Android 15.8.+) with iOS working fine except for Android. and it keeps crashing.“Something Went Wrong”“Content Cannot Be Loaded”This has been happening for a long time, this doesn’t happen on iOS or the Web.I have tried this solution:We already have this option enabled, and still doesn’t work.I don’t know what is causing this issue as we already have loginUserWithAttributes() in our app and iOS is not breaking with this error message either.We use it like this in our code:await Intercom.setUserHash(user_hash);await Intercom.loginUserWithUserAttributes({ email: user_email, userId: uid,});We want to support lower versions of users on iOS and Android so upgrading is a not an option.Is there a way we can resolve this.

Bug Report: Android crash due to setNeedsStatusBarAppearanceUpdate in @intercom/intercom-react-nativePackage: @intercom/intercom-react-nativeVersion: 9.2.0React Native: (e.g. 0.81.0)Platform: AndroidReact Native CLIDescription  The Android build crashes on startup due to a null reference to the property setNeedsStatusBarAppearanceUpdate in IntercomModule. Additional Notes Crash reproducible in RN 0.81.0  Occurs on both emulators and physical Android devices. Works fine on iOS. Cleaning android/build or reinstalling pods does not resolve it. Everything worked as expected when I had intercom version 8.8.0

We are seeing quite a few crashes for the latest Intercom SDK. Older SDKs do not crash.  OS Version: iOS 26.0.1 (23A355)Report Version: 104Exception Type: EXC_BREAKPOINT (SIGTRAP)Exception Codes: 0 at 0x00000001077393e8Crashed Thread: 0Application Specific Information:Exception 6, Code 1, Subcode 4419982312Thread 0 Crashed:0   Intercom                        0x1077393e8         ListBlockView.configure1   Intercom                        0x107738d40         ListBlockView.init2   Intercom                        0x10773f1c0         closure in BlockViewFactory.getViewsForBlocks3   Intercom                        0x10773efc4         BlockViewFactory.getViewsForBlocks4   Intercom                        0x1077432cc         BlockPartView.addBlocks5   Intercom                        0x107744a3c         BlockPartView.configureLayout6   Intercom                        0x10774ec1c         PartViewFactory.getView7   Intercom                        0x107754034         ConversationCellViewFactory.getV

Hi,I’ve found an issue with the in-app message preview on Android where the actual message content is not visible, I assume because the text color matches the background color.You can see this issue replicated in your expo-example app from https://github.com/intercom/intercom-react-native/tree/main/examples/expo-example in the screenshot below.I can’t find anything obvious on the Native Android app settings that is causing this issue, so perhaps there is a styling issue in the Intercom SDK?Thanks for your help  

Hey! I’m facing an issue with intercom-sdk version 17.2.0.The in-app message doesn’t display any message text when it’s a new message in an existing conversation. I’ve attached a Layout Inspector screenshot for more details.Compose version in the app: composeBom = "2025.09.01"  At the same time, if you start a new conversation from the Intercom web interface, the very first message is visible in the app — but from the second message onward, it disappears again. 

When updating to io.intercom.android:intercom-sdk version 17.2.0If R8/Proguard is enabled the following error occurs on the build:Missing class lombok.Generated (referenced from: io.ably.lib.network.HttpBody io.ably.lib.network.HttpResponse$HttpResponseBuilder.body and 94 other contexts) This does not happen on version 17.1.1  It looks like maybe something changed in the build but didn’t include a rule in it’s consumer-rules.pro?  gemini says: -dontwarn lombok.** may fix it?

Hello Intercom Community,I'm encountering a persistent issue with retrieving and listening for unread conversation counts in my React Native application using the Intercom SDK. Neither Intercom.getUnreadConversationCount() nor the IntercomUnreadConversationCountDidChangeNotification event listener seems to be working as expected.Goal: My objective is to display the current unread message count from Intercom within my app's UI (outside of the Intercom messenger itself).Expected Behavior: When new messages arrive in Intercom conversations, the IntercomUnreadConversationCountDidChangeNotification listener should fire with the updated count. Intercom.getUnreadConversationCount() should return the correct number of unread conversations at the time of the call. Actual Behavior: Intercom.getUnreadConversationCount() consistently returns 0 (or null/undefined, please specify) even when there are clearly unread messages visible when I manually open the Intercom messenger. The Intercom.addEve