Mobile SDKs

I'm having trouble with handling push notifications from Intercom. When a push notification is received and selected, it opens the message conversation view momentarily, but then immediately redirects to the app's home screen.I am calling Intercom.client().handlePushMessage() in onResume() of the HomeActivity, but it seems like the Intercom SDK is not waiting for this method call. The issue is reproducible on the latest version (15.10.3) and the previous version (v15.9.1).Here’s the code snippet:Firebase Messaging Service class:override fun onMessageReceived(remoteMessage: RemoteMessage) {     val extras = remoteMessage.data     if (intercomPushClient.isIntercomPush(extras)) {         intercomPushClient.handlePush(application, extras)     } else {         …      } }HomeActivity class:

Has anyone set up intercom in a react-native app built with expo without having to eject? In the instillation guide, there is a section that says you must edit your AppDelegate:@import UIKit;#import <IntercomModule.h>@implementation AppDelegate- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions { [IntercomModule initialize:@"ios_sdk-500cd3ead0b8b44660787a98816eddbf36a36945" withAppId:@"j1flec5a"]; return YES;} If I do not want to eject from the app, can I still use the react-native-expo plugin on IOS?

Since the Intercom iOS SDK began utilizing WebSockets, we have noticed that on occasion, CPU usage jumps to over 100% and there are deadlocks resulting from the Intercom SDK.When this happens, the lock is due to: `[IntercomSDK_IntercomNexusSocket sendWebSocketMessage:]` as seen here: I am now able to reproduce this reliably with the latest release (and previous), 16.4.0, of the Intercom iOS SDK.To reproduce on an app set up with the Intercom iOS SDK (I’m doing this on iOS 17.2.1 but it happens on other versions):Login a user with `Intercom.loginUser(with:)` Logout the user with `Intercom.logout()` Login again using the same call in #1CPU usage will jump up over 100%.  If you pause the debugger at this point, you’ll see a stack trace like the image above.Please

Hi everyone, I’ve reached out via support but in the meantime wanted to ask if anybody is experiencing this same issue in the community.Platform: iOS (expo react-native)Package: @intercom/intercom-react-native v. 8.1.0Lately, we are seeing spike in the error `App Hanging +[ICMHTTPBridge submitMetrics]This seems to be happening in intercom-ios. Below is a portion of stacktrace:```CoreFoundation 0x187de7518 -[NSDictionary isEqualToDictionary:] CoreFoundation 0x187de7514 -[NSDictionary isEqualToDictionary:] CoreFoundation 0x187de75b4 -[NSDictionary isEqualToDictionary:] CoreFoundation 0x187dfe538 ____NSSetI_new_block_invoke CoreFoundation 0x187dfe4a0 __NSSetI_new Foundation 0x186a7ba88 -[NSSet(NSKeyValueCoding) valueForKey:] Intercom 0x1037f3e34 +[ICMHTTPBridge submitMetrics] CoreFoundation 0x187e0a474 __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBS

We are currently working on our upcoming release to the Google Play Store, ensuring compatibility with Android 15. As part of this effort, we have recently updated our app to use the latest version of the Intercom SDK (15.9.1).During our testing phase, we encountered an issue specific to devices running Android 15. The problem pertains to the UI when attaching a video or image in the Intercom messenger.The "X" close button overlaps with the status bar, making it difficult to close the attachment preview.This behavior is observed only on Android 15 and seems related to the new edge-to-edge enforcement introduced in this version of Android.Here are the steps to reproduce the issue:1. Open the Intercom messenger in our app.2. Click on the attachment icon and choose Gallery.3. Select an image or video.4. Observe that the close ("X") button overlaps with the status bar, making it difficult to close the preview. You can vi

Release Date: 15-01-2025 🚀 Enhancements Added support for Fin for Platforms. Special notice view now supports links. Note This release contains some beta features.

Release Date: 09-01-2025 🚀 Enhancements Added privacy policy to conversation screen. Updated icons in the more menu when you launch directly into a conversation. Updates to the Powered By Intercom view in conversations. 🐛 Bug Fixes Fixes issue around tapping on a message in a conversation to display timestamps. Fixes accessibility issue with icon colour in special notice view. Fixes an issue that could cause the typing indicator to continue displaying after a message was received. Note This release contains some beta features.

Release Date: 17-12-2024 🐛 Bug Fixes Resolves an issue with Fin streaming replies. Note This release contains some beta features.

   Intercom crashes every time you try to attach any type of content (even embedded gifs) on Android 9java.lang.NullPointerException at androidx.compose.ui.node.LayoutNodeDrawScope.drawContent(LayoutNodeDrawScope.kt:49) at io.intercom.android.sdk.m5.conversation.ui.ConversationScreenKt$ConversationScreenContent$32$1$1.invoke(ConversationScreen.kt:581) at io.intercom.android.sdk.m5.conversation.ui.ConversationScreenKt$ConversationScreenContent$32$1$1.invoke(ConversationScreen.kt:580) at androidx.compose.ui.graphics.drawscope.DrawScope$record$1.invoke(DrawScope.kt:1077) at androidx.compose.ui.graphics.drawscope.DrawScope$record$1.invoke(DrawScope.kt:941) at androidx.compose.ui.graphics.layer.GraphicsLayer$clipDrawBlock$1.invoke(And

I notice that we get a crash from intercom sdk. It was found in the version 15.8.3 but I notice that I can reproduce this issue from 15.8.0 to the latest version 15.9.1 I down the version to 15.7.1 and that version works.  FATAL EXCEPTION: main                                                                                                     Process: com.xxxxxxxxxxxx.grocery.staging, PID: 32714                                                                                                    java.lang.NoSuchMethodError: No static method rememberModalBottomSheetState(ZLkotlin/jvm/functions/Function1;Landroidx/compose/runtime/Composer;II)Landroidx/compose/material3/SheetState; in class Landroidx/compose/material3/ModalBottomSheet_androidKt; or its super classes (declaration of 'androidx.compose.material3.ModalBottomSheet_androidKt' appears in /data/app/~~elspeVOmvltIcyF5hM5qXg==/com.xxxxxxx.grocery.staging-ezzAuVmfBiFxmCt3v8dawA==/base.apk)

When running unit tests in Xcode Cloud we often get a test failure because the tests failed to start. In those cases we get a spindump indicating that there is a deadlock caused by something Intercom does as a result of [UIBarAppearance init] being called. Anyone seen something similar? It seems to be related to a global initializer so just linking against Intercom will cause the problem.  Just to be sure I’ve changed our code to not call any Intercom methods when running as part of XCTests but it appears to still be happening.

Edit: Title should be “Intercom working fine on Xcode Simulator builds but not loading on testflight builds” but I can't edit it or delete this.I have added the camera privacy reason. Yet on TestFlight builds Intercom does not load. I am wondering if the SDKs access to a certain URL is being blocked because it needs to be manually allowlisted somewhere in the privacy configuration? But not sure on that. Documentation does not say anything about this.Are there other reasons this may happen?

Seems that when installed Intercom overrides the tint color for the whole app. There are ways around that of course but this is likely causing unexpected repercussions for SwiftUI apps using tints.

I wanted to know if you have any solution regarding this error?buildscript { ext { buildToolsVersion = "34.0.0" minSdkVersion = 23 compileSdkVersion = 34 targetSdkVersion = 34 ndkVersion = "26.1.10909125" kotlinVersion = "1.9.22" } repositories { google() mavenCentral() } dependencies { classpath("com.android.tools.build:gradle:4.0.1") classpath("com.facebook.react:react-native-gradle-plugin") classpath("org.jetbrains.kotlin:kotlin-gradle-plugin") }}apply plugin: "com.facebook.react.rootproject"gradlew propertiesdistributionBase=GRADLE_USER_HOMEdistributionPath=wr

Hi!We’re experiencing a non negligible amount of crashes with our iOS app. We’re using the Intercom iOS SDK v18.2.0 (AKA the latest). As far as we can see, the user goes into the intercom integration, and at some point it crashes.Here is the crash-logs from Sentry: OS Version: iOS 18.0.1 (22A3370)Report Version: 104Exception Type: EXC_CRASH (SIGABRT)Crashed Thread: 0Application Specific Information:Expected dequeued view to be returned to the collection view in preparation for display. When the collection view's data source is asked to provide a view for a given index path, ensure that a single view is dequeued and returned to the collection view. Avoid dequeuing views without a request from the collection view. For retrieving an existing view in the collection view, use -[UICollectionView cellForItemAtIndexPath:] or -[UICollectionView supplementaryViewForElementKind:atIndexPath:]. Dequeued view: <IntercomSDK_IT

Execution failed for task ':app:mergeExtDexDevelopmentDebug'.> Could not resolve all files for configuration ':app:developmentDebugRuntimeClasspath'.   > Failed to transform intercom-sdk-base-15.11.3.aar (io.intercom.android:intercom-sdk-base:15.11.3) to match attributes {artifactType=android-dex, asm-transformed-variant=developmentDebug, dexing-enable-desugaring=true, dexing-enable-jacoco-instrumentation=false, dexing-is-debuggable=true, dexing-min-sdk=24, org.gradle.category=library, org.gradle.dependency.bundling=external, org.gradle.libraryelements=aar, org.gradle.status=release, org.gradle.usage=java-runtime}.

Hi!We’re using the Intercom SDK on our iOS app, currently using version 18.1.0. We’ve been getting a lot of crash reports and it seems to mostly happen to users on iOS 15.8, looking into it we found a stack trace that points to swizzling done by the Intercom SDK: Any ideas on how to fix this?

I have determined that Our iPad app is experiencing Airplay issues that are being caused by the Intercom API. Setup:Intercom.setApiKey(apiKey, forAppId: appId)let userAttributes = ICMUserAttributes()userAttributes.userId = user.userIDIntercom.setUserHash(userHash)Intercom.loginUser(with: userAttributes) Steps to reproduce:cold launch the app Have above code run for Authenticated users Turn on Airplay to TV or Apple TV Issue: External screen is blackNote: Turning airplay off and back on solves the issue. Troubleshooting:Commenting the following lines of code solves the issue:Intercom.setUserHash(userHash)Intercom.loginUser(with: userAttributes)I have tried disabling Intercom swizzling as per your doc

Release Date: 11-12-2024 🐛 Bug Fixes Solves a crash in carousels. Addressed issue where video input wasn’t available in a conversation. Fixes issue where first part in a conversation would fail to show as failed in the scenario where it didn’t send. Resolved some layout issues in the conversation screen for users with large font sizes enabled. Note This release contains some beta features.

Hello, I was wondering if there is a way to listen to the “Send Us Messages” event to track the click?SDK is used on Android - its version is 12.5.3  

Hello,I faced with unexpected experience when I cannot to capture video in Intercom messenger using iOS SDK since 17.2.0. Could you please help me to resolve this issue?My steps:Update iOS SDK to 18.2.0. Run the app, check that there is Intercom’s warning “Add NSMicrophoneUsageDescription...”  in Xcode console. Add NSMicrophoneUsageDescription to Info.plist according to Installation guide, step 2.  Run the app again, check the message is not printed. Open Intercom messenger, start a new conversation. Press a green plus icon. It opens an action sheet, choose Camera. The app asks only for camera permission, not microphone. Allow camera usage. Camera opens → only photo capturing is available, not video. Change

A Mobile Software Development Kit (SDK) is a collection of tools, libraries, and APIs that help developers create apps for platforms like Android or iOS. It simplifies app development by providing pre-built components for features such as user authentication, payment systems, and analytics.Benefits of Mobile SDKs:Faster Development: Reduces coding effort with ready-to-use tools. Consistency: Ensures reliable implementation across apps. Scalability: Supports growing user bases and feature additions. Enhanced Experience: Enables features like push notifications and smooth integrations.Popular SDKs:Firebase: For analytics and crash reporting. Facebook SDK: For social login and ad integration. Apple iOS SDK & Android SDK: Native

Starting Android intercom SDK 15.10.2 and even in Latest 15.10.3 and 15.11.0, In Andorid messenger if a Workflow has been already triggered, it always remain there, No other Workflows get triggered afterwards.Eg. If Workflow-1 is trigger, then Workflow-2 is never triggered, even for the Rules of Workflow-2, We always see Workflow-1.This was fine until 15.10.1.  Kindly resolve this ASAP.

The app sometimes crashes when adding video content, even after adding Media3 alongside the existing com.google.android.exoplayer:exoplayer. Crashes have reduced but still occur on various devices. Intercom SDK version is 15.11.0

Android app crashes on launching the messenger with following logLibrary versions used:implementation 'io.intercom.android:intercom-sdk:15.9.1'implementation 'com.google.firebase:firebase-messaging:24.0.0'coreLibraryDesugaring 'com.android.tools:desugar_jdk_libs:2.0.4' Process: org.secondfloor, PID: 2558                                                                                                    java.lang.IncompatibleClassChangeError: Class 'android.content.res.XmlBlock$Parser' does not implement interface 'o8.a' in call to 'int o8.a.next()' (declaration of 's0.a' appears in base.apk)                                                                                                        at s0.a.a(SourceFile:1)                                                                                                        at H0.e.c(SourceFile:41)