Mobile SDKs

Unable to verify JWT with @intercom/intercom-react-native in Expo

Hi, I’ve been having a helluva time trying to get JWT verification working with `@intercom/intercom-react-native`. For context, we have JWT working with our website, and the API secret is enabled for all platforms. We’re reusing the same endpoint we use for web to get the JWT for mobile. Our mobile app is built with: expo: @53.0.23 @intercom/intercom-react-native: 9.1.2 react-native: 0.79.5 I have been testing the app in development mode, with `expo run:ios`. So far, I’ve been able to get Intercom working if JWT is not enforced. But once I activate “Enforce Messenger Security” in the Security Settings, Intercom views start returning “Something’s gone wrong” with a reload button. Here’s our JWT code: // Verified that `intercomToken` is valid, in Intercom’s online JWT decoder// // Token payload looks like:// {// "user_id": 3, // << Does this need to be a string?// "email": "person@place.com",// "name": "John Smith",// "exp": 1759892398// } await Intercom.setUserJwt(intercomToken)await In

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.

iOS SDK version 19.2.0 has broken the close button on our carousels

SDK version 19.2.0 has broken the close button on our carousels, and it's still broken on 19.2.1It would be good if we could update our SDK version for Intercom because Intercom have also fixed UI issues on iOS 26 (new iOS version) :(

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

We are having issues when using presentContent for presenting an article, the close button does not close the modal, though it can be closed with a drag down. any workaround?

iOS SDK 19.2.0 / intercom-react-native 9.1.0 causes weird app crashes

Hello, We are currently using Intercom in our Expo React Native app for customer service messaging. We have previously been using Expo SDK 53 and React Native 0.79.5 with the react native intercom package 9.0.3 and all has been working well. However upgrading Intercom to 9.1.0 or higher is causing some very weird issues for us. Our app streams HLS video where the HLS playlist contains 10s chunks of video which is presented to the user as one long continuous clip. When scrubbing forward in the clip further than what’s been buffered the stream will obviously need to buffer. Our player is using the expo-video package, but we’ve tried with other packages as well such as react-native-video. Now to the issue; Intercom 9.1.0 and higher causes the app to crash when scrubbing forward quickly in the video stream, this problem is only present there and when downgrading Intercom to 9.0.3 it’s working fine again and I can scrub and pause/forward/rewind with no problem and the app is not crashing. I

I’m trying to integrate Intercom push notifications into my React Native app built with Expo (using a custom dev client). I’m using @intercom/intercom-react-native (latest version) and JWT authentication. I can successfully: Generate a valid JWT (confirmed via jwt.io) with user_id and email. Log in the user in Intercom with matching userId and email. Verify that Intercom.isUserLoggedIn() returns true. Fetch the logged-in user attributes from Intercom, which match the JWT payload. Here’s the code I’m using to set up push notifications: export const setupIntercomPushNotifications = async (): Promise<boolean> => { try { const { status: existingStatus } = await Notifications.getPermissionsAsync(); let finalStatus = existingStatus; if (existingStatus !== "granted") { const { status } = await Notifications.requestPermissionsAsync(); finalStatus = status; } if (finalStatus !== "granted") { console.log("❌ Push notification permissions not granted"); return false; } // Get device token (native

Hi, Push notification handling does not work at all on Android + Expo - When opening a push notification from either a terminated, or backgrounded app, the message does not open in Intercom, as it does on iOS, and as is expected. This issue can be replicated in your ‘expo-example’ at https://github.com/intercom/intercom-react-native/tree/main/examples/expo-example I have tested using the Expo SDK version in the your `expo-example`, and using the latest Expo version. I have also attempted to fix this issue with some native Android code as suggested by ‘Fin’:In MainNotificationService.java package com.example; // Replace with your package import com.google.firebase.messaging.FirebaseMessagingService; import com.google.firebase.messaging.RemoteMessage; import com.intercom.reactnative.IntercomModule; public class MainNotificationService extends FirebaseMessagingService { @Override public void onNewToken(String refreshedToken) { IntercomModule.sendTokenToIntercom(getApplication(), refreshed

Intercom React Native Unread Count Issues: getUnreadConversationCount and Listener Not Updating

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.addEven

When updating to io.intercom.android:intercom-sdk version 17.2.0 If 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?

Close button non-responsive for intercom-react-native 9.x

We’re presenting Intercom articles with Intercom.presentContent(content) . Everything was working well in version 8.8.0 but after bumping to 9.x, the close button at the top article header is broken in iOS and doesn’t respond to taps. The only way to close the article is to drag the overlay down (which is something that might not be obvious for every user). It is working correctly on Android.

The app freezes and crashes on iOS after opening an in-app message and swiping left to right to dismiss the UI

I'm using React Native 0.78.3 and using Intercom SDK version @intercom/intercom-react-native 8.6.0. While most features work correctly, the app freezes and crashes on iOS after I open an in-app Intercom message and swipe left to right (from the left edge of the device) to close the Intercom UI View. Reproduction Steps Launch the app on iOS. Trigger an in-app Intercom message. Try to swipe left to right (from the left edge of the device) to close the Intercom UI View. App becomes unresponsive and eventually crashes. We’ve tried on other apps that are using the Intercom SDK and see that the issue is happening. The issue was fixed in @intercom/intercom-react-native 7.2.1 https://github.com/intercom/intercom-react-native/releases/tag/7.2.1 but it happens again on later versions. Updated I’ve tried to upgrade to the latest version of @intercom/intercom-react-native 9.1.1 and the issue frozen whole app does not happen anymore but all the buttons in the intercom window are still frozen and we

Intercom changing SwiftUI app's accent color?

I am working on a SwiftUI iOS app. Building with the latest SDK (Xcode 15.4) to run on iOS 16 and above. We set our App’s accent color using the Global Accent Color Name build setting. As soon as I include the Intercom Package via SPM our accent color is changed to the default blue. Why is Intercom changing the accent color?

❗️Issue with @intercom/intercom-react-native and app.config.ts in Expo

Hello! Has anyone run into this error when using the Intercom Expo plugin (@intercom/intercom-react-native@9.1.1) with an app.config.ts setup? PluginError: Package "@intercom/intercom-react-native" does not contain a valid config plugin.Learn more: https://docs.expo.dev/guides/config-plugins/#creating-a-plugin Unexpected token 'typeof'SyntaxError: Unexpected token 'typeof' at compileSourceTextModule (node:internal/modules/esm/utils:344:16) at ModuleLoader.moduleStrategy (node:internal/modules/esm/translators:105:18) at ModuleLoader.#translate (node:internal/modules/esm/loader:534:12) Not sure if this is an issue with the way the plugin is authored or how Expo expects config plugins to behave in a .ts setup. Would appreciate any insight or workarounds others may have found!

[Android][Intercom SDK - 15.9.0] PdfRender crash

I want to report an issue we have encountered with the Intercom SDK on Android. When a user attempts to open a password-protected PDF sent by the support team, the application crashes with the following error: Fatal Exception: java.lang.SecurityException: password required or incorrect password at android.graphics.pdf.PdfRenderer.nativeCreate(PdfRenderer.java) at android.graphics.pdf.PdfRenderer.<init>(PdfRenderer.java:172) at io.intercom.android.sdk.ui.preview.ui.PreviewUriKt$loadFilesAsBitmaps$1.invokeSuspend(PreviewUri.kt:269) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:104) at androidx.compose.ui.platform.AndroidUiDispatcher.performTrampolineDispatch(AndroidUiDispatcher.android.kt:81) at androidx.compose.ui.platform.AndroidUiDispatcher.access$setScheduledFrameDispatch$p(AndroidUiDispatcher.android.kt:41) at androidx.compose.ui.platform.AndroidUiDispatcher.access$performTrampolin

Android SDK Callback for Dismissal of Intercom Messages Screen

We are using the Intercom Android SDK in our android app to provide customer support. Specifically, we are presenting the Messages space using the following code in Kotlin: Intercom.client().present(space = IntercomSpace.Messages) We're interested in knowing if there's a callback or event triggered when the user dismisses the Messages space by clicking the back button. Our application has specific action that need to be executed when the user returns to our UI, and it would be extremely useful to have this kind of event available. I noticed that on the iOS SDK, there are IntercomWindowWillHideNotification and IntercomWindowDidHideNotification callbacks for similar functionality. Are these iOS callbacks triggered when the Intercom message space is closed? If so, is there an equivalent on the Android SDK? If such functionality is not currently available for Android, are there plans to introduce this feature in a future update?

[Android] NullPointerException in extractErrorString due to null Throwable in setAuthTokens API call

A NullPointerException is occurring in the Intercom Android SDK, specifically within the extractErrorString function. The crash happens when the SDK attempts to call getMessage() on a null Throwable object. Stack Trace: Fatal Exception: java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.String java.lang.Throwable.getMessage()' on a null object referenceat io.intercom.android.sdk.api.ErrorStringExtractorKt.extractErrorString(ErrorStringExtractor.kt:16)... Root Cause Analysis: Upon decompiling the SDK's code, we've identified the root cause in the onResponse method of the setAuthTokens API call. In the onResponse method, when an API response is not successful (!response.isSuccessful()), an ErrorObject is created with a Throwable that is explicitly passed as null. ErrorObject errorObject = new ErrorObject((Throwable)null, response); This ErrorObject is then passed to extractErrorString, which, within its catch block (specifically when parsing the error JSON fails)

The app freezes and crashes on iOS after opening an in-app message and tapping either the close button or the React component.

I'm upgrading to React Native 0.77.2 and using Intercom SDK version @intercom/intercom-react-native 8.5.0. While most features work correctly, the app freezes and crashes on iOS after I open an in-app Intercom message and tap either the close button or interact with a Reaction within the message. Reproduction Steps Launch the app on iOS. Trigger an in-app Intercom message. Tap the "Close" button or interact with a React component rendered within the message. App becomes unresponsive and eventually crashes (ANR). Relevant Logs (Xcode + Sentry) Sentry Breadcrumbs show lifecycle events for multiple Intercom-related view controllers: ICMNoteViewController ICMFullScreenInAppViewController ICMInAppHeaderViewController IntercomSDK_ITBBlockListViewController A user touch event was captured: [SentryBreadcrumb] category = touchmessage = closeview = <UIButton frame=(317 4; 44 44)> Multiple slow frame detections logged by SentryFramesTracker: [SentryFramesTracker] Detected slow frame starting at …