Mobile SDKs

As of @intercom/intercom-react-native v8.2.0 the back button after presenting content using Intercom.presentContent(IntercomContent.helpCenterCollectionsWithIds([id]))is broken on Android devices.Screenshot attached. Any help appreciated.  

Hi Intercom team,We're encountering a crash in our production app related to the Intercom SDK when processing push notifications. The error occurs in TaskStackBuilder.getPendingIntent() with the following stack trace:  Fatal Exception: java.lang.IllegalStateException: No intents added to TaskStackBuilder; cannot getPendingIntent at androidx.core.app.TaskStackBuilder.getPendingIntent(TaskStackBuilder.java:333) at androidx.core.app.TaskStackBuilder.getPendingIntent(TaskStackBuilder.java:313) at io.intercom.android.sdk.m5.push.ConversationDeepLinkRouterKt.buildBasePendingIntent(ConversationDeepLinkRouter.kt:85) at io.intercom.android.sdk.m5.push.ConversationDeepLinkRouterKt.buildIntentForDeepLinkScreen(ConversationDeepLinkRouter.kt:42) at io.intercom.android.sdk.m5.push.ui.DeepLinkStylePushUIKt.buildDeepLinkNotification(DeepLinkStylePushUI.kt:44) at io.intercom.android.sdk.m5.push.IntercomNotificationHandler$processDeepLinkPushNotification$1.in

Release Date: 16-05-2025 🐛 Bug Fixes Fixes a bug that could cause a crash when dismissing multiple in app notifications. Fixes a bug that could cause a crash when trying to close a note using the x button.

Hi! I have the “Prevent users from opening multiple conversations” option enabled in Intercom settings, but when calling Intercom.presentMessageComposer(); from my React Native app, it always creates a new conversation instead of navigating to the existing one.Is this the expected behavior, a known issue, or am I missing something in the implementation?What’s the best way to handle this scenario?Thanks!

Release Date: 11-04-2025 🚀 Enhancements We've added a new API to enable setting JWTs in the Messenger. This should be called before any user login. To learn more go here. Resolved some differences between the registration of unidentified and identified users of iOS and Android. Both platforms now have matching implementations.

Hi, So I’ve implemented the Intercom SDK into our Android app the past few days and stumbled in to a strange thing. The SDK crash as I’m trying to open the write message view with this error.java.lang.NoSuchMethodError: No static method FlowRow(Landroidx/compose/ui/Modifier;Landroidx/compose/foundation/layout/Arrangement$Horizontal;Landroidx/compose/foundation/layout/Arrangement$Vertical;IILandroidx/compose/foundation/layout/FlowRowOverflow;Lkotlin/jvm/functions/Function3;Landroidx/compose/runtime/Composer;II)V in class Landroidx/compose/foundation/layout/FlowLayoutKt; or its super classes (declaration of 'androidx.compose.foundation.layout.FlowLayoutKt' appears in /data/app/~~MDeJzUHvf74b7jpNmGq6Rw==/com.*.staging-7N_jvukfhGCaqNo-t2IqvQ==/base.apk)    at io.intercom.android.sdk.m5.conversation.ui.components.row.QuickRepliesKt.QuickReplies(QuickReplies.kt:38)    at io.intercom.android.sdk.m5.conversation.ui.components.row.QuickRepliesKt.ComposerSuggestions(QuickReplies.kt:88)    at io.

Hi, using the latest version i manage to build the app on IOS (your last update fixed the expo plugin swift headers) but didn’t fix the sdk. now on ios presenting intercom shows a loading error (was working fine before the update to new arch and expo 53) and on android nothing happens when i call intercom.present() expo 53react 19react-native 0.79.2@intercom/intercom-react-native 8.4.0

Release Date: 01-11-2024 📱 New Feature Added the ability to upload files to a conversation. 🚀 Enhancements Added new API isUserLoggedIn. This enables developers to determine if a user is currently logged in to Intercom. Added new API fetchLoggedInUserAttributes. This enables developers to retrieve the attributes of the currently logged in user. 🐛 Bug Fixes Fixed some layout issues in the conversation view. Improvements to the photo previewer. Fixes some colour accessibility issues throughout the SDK. Fixes issue where clicking on the CTA in a post would not dismiss it.

We did implement the intercom Integration with our mobile app and everything works like a charm BUT we realised we are sending communications to our clients over the chat but they don't seem to realise messages are waiting for them since the app badge count is zero. I'd tried to increase the value over the AppDelegate methods but can't make it increase the count when the app is not running or in background. Also tried to create a Notification Extension for the app but the criteria for the modifications won't meet since the payload of the notifications has the value mutable content set to false (mutableContent: NO)  Another way to make this work would be to send notifications as silent ones but don't know if the payload from Intercom's notifications is customisable. Any help with this subject would be much appreciated. Bests.

Presenting secondary-level collections doesn't work on iOS SDK (opens the root help center) but works fine on Android SDK.Presenting top-level collections works as expected on both platforms.

Hello,We have successfully integrated your Android SDK (version 15.16.0) into our application. However, we are currently seeing a significant number of crashes reported in Firebase. Unfortunately, we haven’t been able to reproduce the issue on our side so far.Could you please help us investigate this further? Let us know if you need any additional information or logs to assist in the debugging process.Thank you in advance for your support.This is the crash:          Fatal Exception: java.lang.NullPointerException:       at androidx.compose.ui.platform.AndroidComposeView.<init>(AndroidComposeView.android.kt:788)       at androidx.compose.ui.platform.Wrapper_androidKt.setContent(Wrapper.android.kt:77)       at androidx.compose.ui.platform.AbstractComposeView.ensureCompositionCreated(ComposeView.android.kt:258)       at androidx.compose.ui.platform.AbstractComposeView.onAttachedToWindow(ComposeView.android.kt:290)       at android.view.View.dispatchAttachedToWindow(View.java:22479) 

Are there any plans to have macOS SDK in the near future? Specifically I want to use it for embedding the help center inside the app.

Please help. I cannot build a release apk/aab, I’m getting the following error: > Task :app:compileReleaseKotlin FAILEDe: Incompatible classes were found in dependencies. Remove them from the classpath or use '-Xskip-metadata-version-check' to suppress errorse: file:///Users/builder/.gradle/caches/transforms-4/a23eb7edad52ffdf2e2ff09828f4ac13/transformed/jetified-intercom-sdk-base-15.15.1-api.jar!/META-INF/intercom-sdk-base_release.kotlin_moduleModule was compiled with an incompatible version of Kotlin. The binary version of its metadata is 2.1.0, expected version is 1.9.0.Classes that weren't resolved: > com.google.common.util.concurrent.ListenableFuture I’m using the latest version of the library (8.3.0), and my build.gradle is: buildToolsVersion = "35.0.0"minSdkVersion = 23compileSdkVersion = 35targetSdkVersion = 35ndkVersion = "26.1.10909125"kotlinVersion = "1.9.22" 

Hi - We exprience a crash in the latest version of the iOS SDK version 18.6.3 The way to reproduce the crash:1. Open Intercom in the app, start a new chat (or existing one).2. In the conversation choose to add a photo (from library or from camera)3. Before choosing to send - take the internet off (by turning on airplane mode)4. Add the photo5. Tap the ! to try again - but take no action.6. Restore the internet by disable airplane mode7. Wait for Intercom to restore the connection and send the image automatically and after the image is shown as sent (not grayed out) - Tap Try again8. crash!Reproduced 100% of the times. ScreenReco...3-39_1.MP4   

We are facing following issue in our iOS Native app:When the app is closed and the user clicks on the Intercom’s Push Notification, the app opens up but the chat/post opens momentarily and closes. This only happens when the app is closed and notification is clicked, it works fine if the app is in the background/active state.In our case when the app is opened via Push Notification in the app's closed state, main view get refreshed after data fetching.I have done all the Push Notification configuration as per the doc: https://developers.intercom.com/installing-intercom/ios/push-notificationsWe are using iOS SDK Intercom version: 17.1.2 Similar kind of issue was resolved by our Android Team by using Intercom.client().handlePushMessage() . However, such a method does not exist in the iOS Intercom SDK.

Hi there,I've just installed the latest version of the Expo plugin (6.8.1). Everything is mostly working, but there are some issues. I've noticed problems with push notifications, and I'm unsure if they are related to the following:1. We're unable to retrieve the unread message count correctly. The listener isn't working, and even when the app is open, new messages aren't being fetched.2. In chat, replies from an "agent" aren't showing up in real-time. To see new messages, we have to close and reopen the conversation, which disrupts the chat experience.Any advice on these issues would be appreciated.Thank you

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

Hello Intercom team,I’m reaching out regarding an issue where videos uploaded to chat lose their audio during processing. The preview of the video shows sound, but once uploaded, the audio is missing. The issue occurs consistently, regardless of the video source (recorded directly or uploaded from the gallery).Could you please help us investigate if this is a known issue or if there’s something we’re missing? Any guidance or steps to resolve this would be greatly appreciated.Thank you in advance for your support!

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