Mobile SDKs

Bug Report: Unrecognized selector sent to CPTemplateApplicationScene (CarPlay) — iOS 27 Summary The Intercom iOS SDK crashes the host app with an **unrecognized selector** exception when aCarPlay scene is involved in scene lifecycle. Intercom sends a `UIWindowScene`-only selector to`CPTemplateApplicationScene`, which is a sibling of `UIWindowScene`, not a subclass — so themessage is unhandled and the app terminates. This is the same long-standing defect previously reported as`-[CPTemplateApplicationScene windows]: unrecognized selector`( and )On **iOS 27** the selector has changed to a different `UIWindowScene`-only API: -[CPTemplateApplicationScene _enhancedWindowingEnabled]: unrecognized selector sent to instance Environment Intercom SDK | 19.3.2 (intercom-ios-sp, SPM). Also reproduces on latest 19.6.3 — updating does not fix it.iOS 27 (also historically reproduced on earlier iOS with the `windows` selector variant)SwiftUI/UIKit app with a separate CarPlay scene (`CPTemplateApplicati

Hello everyone,I am facing an issue with Intercom Push Notification when it is a cold start (App is terminated, you receive a Push Notification and this notification will wake the App). While testing on Simulator that, if i am running my app from Xcode, terminate the App (on Simulator, not on Xcode), send a message to my test user, wait the push notification, receive it, tap on it but when i tap on it, Intercom Messenger does not opens the modal chat, it keeps me on my WorkListView (WorkList is a subview of RootView, that appears after SplashViews finish animation and transit to WorkListView).I have already made installation (API Key, API ID and Push Notifications are enabled on Settings > Channel > Messenger > Install > Install for Mobiles), Apple Developer is already configured, when i open the Messenger on my App, i can send and receive messages. When App is open but in background i am able to receive and wake the app in the correct modal Intercom window chat, but only t

We're experiencing an issue with iOS SDK where AI agent responses are not immediately visible in the chat interface. When a user sends a question and the agent responds right away, the message doesn't appear on screen unless the user navigates back to the dashboard and returns to the chat. This same issue previously occurred in the Android SDK but was resolved with a version update. I attached a video of it. We are using 19.4.1 swift package version.

Release Date: 25-05-2026 🐛 Bug Fixes Fixed an issue where the status bar could display the incorrect text colour.

Release Date: 14-05-2026 🚀 Enhancements Users can now send multiple images and files in a single message, with a preview of selected media in the composer. 🐛 Bug Fixes Fixed an issue where login-triggered notes may not appear when logging in mid-session. Fixed an issue where the Fin typing avatar could display the brand color as its background in the inbox. Fixed an issue where images in multi-block message bubbles could display with incorrect corner radii. Fixed an issue where isUserLoggedIn could return false despite a successful login. Fixed an issue where GIF timestamps and attributions may not align with the image width. Fixed an issue where short article URLs could open the Help Center home screen instead of the article.

The intercom-android Github repo includesSamples on how to use the Intercom Android SDK Changelog JavadocsHowever, the Javadocs seem to be very old (last updated 6 years ago). Is there a way to find the javadocs for a specific version of the SDK?

Hi,We are experiencing bugs with the Intercom SDK when using voice-to-text (speech-to-text / dictation) to compose support chat messages in the Intercom Messenger on both iOS and Android.Environment:- @intercom/intercom-react-native v9.8.0 (latest)- React Native 0.79, Expo SDK 53- iOS and Android (tested on multiple devices)- Intercom Messenger presented via setLauncherVisibility / presentIntercom- Old Architecture (New Architecture / TurboModules disabled, RCT_NEW_ARCH_ENABLED=0)Bug 1 — iOS: Sent message text not cleared from input fieldWhen a user composes a message using iOS voice-to-text (dictation) and taps Send, the message is successfully delivered to the conversation. However, the sent text remains in the text input field instead of being cleared.Steps to reproduce (iOS):1. Open the Intercom Messenger on iOS2. Tap the text input field3. Activate voice-to-text (dictation) via the microphone icon on the iOS keyboard4. Dictate a message5. Tap the Send buttonExpected behavior:The m

Hi guys, I recently integrated intercom in our app React Native app running Expo 54. @intercom/intercom-react-native (^9.6.3). I noticed whenever I build on EAS, calling present() or presentMessageComposer() opens two instances of the messenger bottomsheet in our app. Doesn’t happen whenever I try to build locally using prebuild tho. Has anyone encountered this before? 

With Intercom Android SDK, we call Intercom.initialize in the Application sub-class.We only login a user when they login to our app. On our login screen, we have a button that should open an intercom help article. We just call Intercom.client().presentContent(myId) when the user clicks this button.Recently, this leads to “Something wen wrong. Try again” message. Logging in and logging out fixes the problem.My question is: Is it required to have a registered user (perhaps an unidentified one) before calling presentContent()?

Hi. I tested this on both android and ios and it seems to me that setting languageOverride on android doesn’t work whereas on ios it does. I tested this on both platforms with same userChanged language from english to french on androidRestarted app and help center was still in englishChecked that user in intercom and language override was still englishI then changed language on iosChecked that user in intercom and language override was now frenchRestarted Android app and both apps now show help center in french We are using React native 

Two issues specific to android:Issue building with expo 55, any version greater than 9.6.3 fails the prebuild step with:- Creating native directory (./android)✔ Created native directory- Updating package.json✔ Updated package.json | no changes- Running prebuild✖ Prebuild failedTypeError: [android.manifest]: withAndroidManifestBaseMod: f.action?.some is not a functionTypeError: [android.manifest]: withAndroidManifestBaseMod: f.action?.some is not a function at /home/expo/workingdir/build/node_modules/@intercom/intercom-react-native/lib/commonjs/expo-plugins/withAndroidPushNotifications.js:96:149 at Array.some (<anonymous>) at /home/expo/workingdir/build/node_modules/@intercom/intercom-react-native/lib/commonjs/expo-plugins/withAndroidPushNotifications.js:96:129 at Array.some (<anonymous>) at /home/expo/workingdir/build/node_modules/@intercom/intercom-react-native/lib/commonjs/expo-plugins/withAndroidPushNotifications.js:96:58 at action (/home/expo/workingdi

Release Date: 23-03-2026 🐛 Bug Fixes Fixed an issue where the composer attachment menu could render as plain text instead of a proper menu. Fixed an issue where the typing indicator may not appear when admin details are unavailable. Fixed an issue where the help center search bar placeholder could appear in English regardless of the workspace locale. Fixed an issue where device tokens could be mistakenly deleted impacting push notification delivery. Fixed an issue where workflows would sometimes not match for a user.