Mobile SDKs

Hello,We are currently migrating our react-native app to Expo and we are facing some issues with Intercom push notifications.We are using:"@intercom/intercom-react-native": "8.1.0","expo": "52.0.28",And in app.config.ts, this is our intercom setup:'@intercom/intercom-react-native',{ appId: process.env.EXPO_PUBLIC_SECRETS_INTERCOM_APP_ID, androidApiKey: process.env.EXPO_PUBLIC_SECRETS_INTERCOM_ANDROID_API_KEY, iosApiKey: process.env.EXPO_PUBLIC_SECRETS_INTERCOM_IOS_API_KEY}We have followed the rest of the setup mentioned on github.It seems that the chat works when we open it from the app. The user can send and receive messages as expected.The problem is that the push notifications don’t seem to work at all. We don’t receive any notification when the app is on the background or closed.Could you please advice on what we can check? Thank you,Nikos

Hey, After migrating from "@intercom/intercom-react-native": "^3.0.5",to latest version "@intercom/intercom-react-native": "^4.0.1",the displaying of specific helpcenter collections does not work anymore.Old code: Does not work after updating the SDKconst res = await Intercom.displayHelpCenterCollections([‘1234567’])// trueNew code: Also does not work with the latest SDKconst collections = await Intercom.fetchHelpCenterCollections();/**[ { "id": "1234567", "title": "FAQ" }]*/const collectionIds = collections.map(_ => _.id);// [ "1234567" ]const collectionContent = IntercomContent.helpCenterCollectionsWithIds(collectionIds);/**{ "type": "HELP_CENTER_COLLECTIONS", "ids": [ "1234567" ]}*/const res = await Intercom.presentContent(collectionContent);// trueThe problem is the same for both methods:displayHelpCenterCollections and presentContent return true, but no Intercom popup is opened.

In the last version 15.15.0 of Android you updated androidx.activity:activity-compose to 1.10.1, which now requires to compile against version 35 of the Android APIs.Error below:```Execution failed for task ':app:checkDebugAarMetadata'.> A failure occurred while executing com.android.build.gradle.internal.tasks.CheckAarMetadataWorkAction   > 3 issues were found when checking AAR metadata:            1.  Dependency 'androidx.activity:activity-ktx:1.10.1' requires libraries and applications that           depend on it to compile against version 35 or later of the           Android APIs.                :app is currently compiled against android-34.                Also, the maximum recommended compile SDK version for Android Gradle           plugin 8.2.1 is 34.                Recommended action: Update this project's version of the Android Gradle           plugin to one that supports 35, then update this project to use           compileSdk of at least 35.                Note that upd

I need "content-available": 1 added to the payload, so we can handle the badge counter at our application

Hi,We are developing a React Native app with Intercom integration using the https://www.npmjs.com/package/@intercom/intercom-react-native package. We want to get the unread message count for a user to show a notification when the app is open and the user receives a new Intercom message.We have tried using the addEventListener with IntercomEvents.IntercomUnreadCountDidChange but the passed in callback does not get invoked when new messages are received. We also tried calling the getUnreadConversationCount method and that returns the initial count of messages when our app starts and the user is logged in into Intercom, but subsequent calls always returns the initial value event when new messages are received in Intercom. Calling logout and login again in Intercom and then calling getUnreadConversationCount returns an updated count, so it looks like a bug in your code, or are we doing something wrong on our end?Thank you,Mikael Amborn

Package: @intercom/intercom-react-native: ^3.0.3 When a push notification is sent via Intercom, with a deep link, the deep link opens correct on android (it opens to the correct in-app page when the app is in the background and the notification is clicked, as well as when the app is closed and the notification is clicked). However, on iOS, if the notification is clicked while the app is closed, the notification does not send the user to the correct page, it simply sends them to the home page (the page they would have landed on if they had simply opened the app by itself). If the notification is clicked while the app is backgrounded however, it does send them to the correct page. Anyone have any idea why this behaviour might be happening? 

Hello,I am experiencing an issue with the Intercom SDK on Android. When I initialize Intercom at app startup, I set the current language using:UserAttributes.Builder().withLanguageOverride(currentLanguage) After changing the system language and reinitializing Intercom with the updated language, most of the content updates correctly. However, the "Send us a message" text remains in the original language.It seems that this specific text does not update after reinitialization. Is there a way to ensure that all content, including this text, is fully updated after a language change?Thank you for your help. 

We upgraded the Android Intercom SDK from version 15.7.1 to 15.9.1. After pushing out a new release of our app, we noticed that we were not getting crash reports from Sentry. We use Sentry as well as Firebase Crashlytics to analyze crash reports.After investigation, we determined that the Intercom Android SDK also uses Sentry. Updating the Intercom SDK had overwritten our configuration. This resulted in Sentry being turned off for our app.Manifest merger failed : Attribute meta-data#io.sentry.auto-init@value value=(true) from AndroidManifest.xml:45:55-75 is also present at [io.intercom.android:intercom-sdk-base:15.10.3] AndroidManifest.xml:25:13-34 value=(false). Suggestion: add 'tools:replace="android:value"' to <meta-data> element at AndroidManifest.xml to override.Sentry discourages usage in third-party SDKs (e.g. the Intercom Android SDK).“It's considered bad practice to use Sentry SDKs in third-party plugins, packages, and libraries (such as payment SDKs or embeddable widget

I am using the @intercom/messenger-js-sdk SDK.It successfully records new users.The problem is that I cannot find how to set custom attributes for that user. I have the custom attribute `is_admin`. Here are the approaches I’ve tried:Basic objectIntercom({ app_id: APP_ID, api_base: process.env.NEXT_PUBLIC_INTERCOM_API_BASE_URL, user_id: user.id, email: user.email, user_hash: hash, is_admin: user.role.includes('admin'),});Object with custom_attributesIntercom({ app_id: APP_ID, api_base: process.env.NEXT_PUBLIC_INTERCOM_API_BASE_URL, user_id: user.id, email: user.email, user_hash: hash, custom_attributes: { is_admin: user.role.includes('admin'), }});Post instance update methodIntercom({ app_id: APP_ID, api_base: process.env.NEXT_PUBLIC_INTERCOM_API_BASE_URL, user_id: user.id, email: user.email, user_hash: hash,}

Hi Intercom Support Team,We're currently experiencing an issue with the Intercom chat widget in our React Native application built with Expo. While most functionalities are working seamlessly, our iOS users are unable to upload photos taken directly with the camera through the chat interface (specifically the camera option within the chat buttons).Here are the details of our setup:Platform: iOSExpo Version: 52.0.29React Native Version: 0.76.6Intercom React Native SDK Version: @intercom/intercom-react-native 8.1.0 and tested with 8.2.0New Architecture: DisabledWe've ensured that the necessary permissions are set as per your documentation:"NSCameraUsageDescription": "This app uses the camera to scan payment cards and take photos for support messaging." Despite upgrading to @intercom/intercom-react-native version 8.2.0, the issue persists. Our customers can access other features without any problems, but the inability to use the camera for uploading photos is causing some confusion.Our qu

We’re experiencing a slow launch time in our SwiftUI app, about 35% of the slow launch time is caused by Intercom initialization.  The stack trace indicates that multiple functions within the Intercom SDK, especially the initialization processes involving IMCCrashHandler, IMCConfig, HomeConfig, and HomeHeader, are contributing significantly to app launch latency. The UIKitCore and CoreImage components (like UIGraphicsImageRenderer and CIImage) invoked through ICAssets.backgroundImageViewWith also add processing overhead, which may impact the performance during launch.Here is the full stack trace given by XCodes tools:dyld start1. App.main() - SwiftUI2. AppDelegate.application(_:didFinishLaunchingWithOptions:) - SwiftUI3. IMCCrashHandler swizzleDidFinishLaunchingWithOptions - Intercom └ IMCCrashHandler sharedConfig - Intercom4. IntercomSDK_SentrySDK startWithConfigureOptions - Intercom5. IMCCrashHandler configureTags - Intercom6. IMCConfig sharedConfig - Intercom7. IMCConfig configFr

Hey! We updated our Intercom Android SDK and noticed that since version 15.5.1 (the one that uses Media3, Release notes), our minifyReleaseWithR8 Gradle task fails. In 15.5.0 it still worked. The error output is:Missing classes detected while running R8. missing_rules.txt contains this:# Please add these rules to your existing keep rules in order to suppress warnings.# This is generated automatically by the Android Gradle plugin.-dontwarn com.google.android.exoplayer2.ExoPlayerLibraryInfo-dontwarn com.google.android.exoplayer2.ParserException-dontwarn com.google.android.exoplayer2.decoder.DecoderException-dontwarn com.google.android.exoplayer2.extractor.ExtractorInput-dontwarn com.google.android.exoplayer2.extractor.FlacStreamMetadata-dontwarn com.google.android.exoplayer2.extractor.SeekMap$SeekPoints-dontwarn com.google.android.exoplayer2.extractor.SeekPoint-dontwarn com.google.android.exoplayer2.util.LibraryLoader-dontwarn com.google.android.exoplayer2.util.Util We use the newest med

Release Date: 25-02-2025 🐛 Bug Fixes Fixed a bug where some users were unable to add a phone number in the attribute collector.

iOS crashed randomly (18.5 version of SDK).Stacktrace: Thread 25 name:Thread 25 name:Thread 25 Crashed:0   libsystem_kernel.dylib            0x00000001e3b572d4 __pthread_kill + 8 (:-1)1   libsystem_pthread.dylib           0x000000021d08d59c pthread_kill + 268 (pthread.c:1721)2   libsystem_c.dylib                 0x000000019a2a0b08 abort + 128 (abort.c:122)3   libsystem_malloc.dylib            0x00000001a2a54b74 malloc_vreport + 896 (malloc_printf.c:251)4   libsystem_malloc.dylib            0x00000001a2a7dc00 malloc_zone_error + 100 (malloc_printf.c:319)5   libsystem_malloc.dylib            0x00000001a2a72c30 nanov2_guard_corruption_detected + 44 (nanov2_malloc.c:2496)6   libsystem_malloc.dylib            0x00000001a2a53c6c nanov2_allocate_outlined + 460 (nanov2_malloc.c:2989)7   libsystem_malloc.dylib            0x00000001a2a53a18 nanov2_calloc_type + 568 (nanov2_malloc.c:1247)8   libobjc.A.dylib                   0x000000018f9a8b04 class_createInstance + 72 (objc-runtime-new.mm:9183)9

In our app, when I type a link in the intercom chat (https://example.com/list), it opens in the Safari browser. However, when the same link is triggered from a notification or from another app like WhatsApp or Messages, it works fine.Based on the article about deep linking (https://developers.intercom.com/installing-intercom/ios/deep-linking/), I added the following configuration:<key>IntercomUniversalLinkDomains</key><array>    <string>example.com</string>    <string>https://example.com/help</string>    <string>https://www.example.com/help</string>    <string>https://example.com</string>    <string>https://www.example.com</string></array>Additionally, in my AppDelegate I have implemented:func application(_ application: UIApplication,                 continue userActivity: NSUserActivity,                 restorationHandler: @escaping ([UIUserActivityRestoring]?) -> Void) -> Bool {    print("breakp

Hello everyone,I see that there are several possibilities for Intercom onboarding on the web. Among them is a checklist. For mobile, we basically have the carousel, which makes the experience very limited.Is there any plans to add more mobile onboarding features to Intercom or could someone recommend tools to add a better onboarding experience on mobile?Thank you.

mpty input (after ) at line 1, column 1 [parse.c:1062] in '<HTML> <HEAD> <TITLE>INVALID_KEY</TITLE> </HEAD> <BODY BGCOLOR="#FFFFFF" TEXT="#000000"> <!-- GSE Default Error --> <H1>INVALID_KEY</H1> <H2>Error 401</H2> </BODY> </HTML>

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:override fun onResume() { super.onResume() Intercom.client().handlePushMessage()}It is reproducible using latest version 15.10.3 and previous v15.9.1 as well.Has anyone encountered a similar issue? A

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 let me know if I can send other information about this issue.Best,Adam

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_OBSERVER__ CoreFoundation 0x187e0a390 ___CFXRegistrationPost_block_invoke

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 view a screen shot of the issue here: Intercom UI Issue android 15 on at

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.