Mobile SDKs

Hello, I wanted to report a crash that we have in our application.I don’t know when it happens but it seems to be caused when the SDK try to download an attachment and the file isn’t available.Stacktrace: Fatal Exception: java.io.FileNotFoundException: https://xxx-support.intercom-attachments.eu/i/o/file.pdf at com.android.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:255) at com.android.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:211) at com.android.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:30) at io.intercom.android.sdk.ui.preview.ui.PreviewUriKt$loadFilesAsBitmaps$1$1.invokeSuspend(PreviewUri.kt:252) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:34) at kotlinx.coroutines.D

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  

Hi. We have a crash in our app when pushing a survey to some of our users. We are using version 17.1.0 (latest)This is the crash log → io.intercom.android.sdk.survey.SurveyViewModel.buildContentState (SurveyViewModel.kt:215)io.intercom.android.sdk.survey.SurveyViewModel.access$submitSurvey (SurveyViewModel.kt:83)io.intercom.android.sdk.survey.SurveyViewModel.access$buildContentState (SurveyViewModel.kt:83)io.intercom.android.sdk.survey.SurveyViewModel$submitSurvey$1.invokeSuspend (SurveyViewModel.kt:388)kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith (ContinuationImpl.kt:34)kotlinx.coroutines.DispatchedTask.run (DispatchedTask.kt:100)kotlinx.coroutines.internal.LimitedDispatcher$Worker.run (LimitedDispatcher.java:124)kotlinx.coroutines.scheduling.TaskImpl.run (Tasks.kt:89)kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely (CoroutineScheduler.java:586)kotli

Hi there! We’ve recently recieved reports from our support team that carousels aren’t displaying within the app. In our android code, we initialize intercom, and then if we are authenticated, we call loginIdentifiedUser after. This logic has been unchagned for a while and had worked for well over a year. Through debugging we have found that adding an artifical delay (9 seconds) between initialize and loginIdentifiedUser results in the carousesl to show again. Without the delay, login completes successfully (the callback returns a success), but the carousels don’t show.Is this expected behavior, or something on our end? Guidance would be greatly appreciated here  We’re using version 17.4.0 of intercom. 

We are using @intercom/intercom-react-native v9.4.0 with Expo.When we send mobile push notifications, we can track:    •    How many users received the push    •    Which users opened it (tap on the push)  However, we also use POST messages, and inside those POST we include deeplinks to redirect users to specific screens in the app.Here’s the issue:    •    We can track how many users opened the POST message    •    But we cannot track link interactions inside the POST    •    The “Clicked” metric is always empty, even when users tap the deeplinkIs there any workaround or recommended approach to track when users tap deeplinks or links inside POST messages? 

Hi Intercom Team,We are currently integrating the Intercom SDK into our application and have encountered the following three issues that are affecting the user experience:1. Partial Language Update via updateUser Issue: When calling Intercom.updateUser({ languageOverride: Language }) to switch the UI language, the change is inconsistent. Sometimes only a portion of the Intercom UI updates, while other elements remain in the previous language.     Workaround: A full and correct language switch only occurs after calling Intercom.logout() and re-initializing, which is not ideal for user experience. Expected Behavior: The entire Intercom UI should refresh to the target

Hey! I’m facing an issue with intercom-sdk version 17.2.0.The in-app message doesn’t display any message text when it’s a new message in an existing conversation. I’ve attached a Layout Inspector screenshot for more details.Compose version in the app: composeBom = "2025.09.01"  At the same time, if you start a new conversation from the Intercom web interface, the very first message is visible in the app — but from the second message onward, it disappears again.

Hi, we tried to integrate the voice transcription feature in our iOS application but we encountered an issue with the SDK. We have a HTTP Error: 401 unauthorized, with message “Tried to transcribe audio but there was a network error”All other features (message, document, photos) work correctly and our Android version succeed to use voice transcription.We check this list and seems ok in our side : Verify iOS preprod Identity Verification secret in Intercom dashboard (Security Settings → Identity Verification → iOS → Preprod) Ensure backend generates ios_user_hash with correct iOS preprod secret Upgrade Intercom SDK to latest version both apps Add NSSpeechRecognitionUsageDescription permission in Info.plist files Ensure setUserHash is called before any other Intercom methodI extract the intercom log : [Intercom] Push Notifications Handler: AUTO[Intercom] INFO - Checking if user ident

I’m seeing an issue with a “blur” overlay being left on top of the conversation window when Intercom loads after calling [Intercom presentMessageComposer:NULL] or [Intercom presentMessageComposer:@”text”]This only happens when building on XCode and only when running on iOS 26. Any other combination (e.g. XCode 16 on iOS 26 or XCode 26 on an older iOS version) worksFeels like a race condition in the loading logic perhaps? But hard to investigate as it’s closed source.This happens on intercom-ios versions 16.6.2, 19.4.1 and several in betweenDoes anyone have any information or a workaround?  

I am using Intercom.presentMessageComposer(initialMessage) to show Intercom with a pre-filled message in my React Native app like this:await Intercom.presentMessageComposer(‘An initial message.’);I’m using this version: "@intercom/intercom-react-native": "^9.3.2"This launches the Intercom messenger on iOS with pre-filled message.On Android, this launches the Intercom messenger but there’s no pre-filled message. Also the message input is not visible on Android.Is this an expected behavior on Android or is it a bug?

Hello community, I am responsible for a project that requires a technical expert. I am seeking out a qualified professional to assist with implementation efforts. We are looking for a developer with technical proficiency in the Intercom SDK. This is for a defined scope of work to support a critical business function. The project has defined deliverables and milestones. I welcome all inquiries and recommendations.

  SDK Version: Intercom iOS SDK 19.4.1  Platform: iOS 26.1 Integration: Flutter (via intercom_flutter wrapper) Description:  The close button (X) on surveys does not respond to touch events on iOS. Users cannot dismiss surveys by tapping the close button and must complete the survey to proceed. Swiping down to dismiss still works.  Steps to Reproduce:  1. Initialize Intercom with valid credentials  2. Trigger an Intercom Survey (programmatically via presentContent:surveyWithId: or via auto-targeting)  3. Attempt to tap the close button (X) on the survey modal  4. Observe that the tap is ignored and the survey remains open  Expected Behavior:  The survey should close immediately when the close button is tapped.  Actual Behavior:  The close button does not respond to touch events. No c

Android API 36 is ignoring the orientation configuration. The Android SDK is fixing the orientation as portrait. We have got the following warning on Google Play: From Android 16, Android will ignore resizability and orientation restrictions for large screen devices, such as foldables and tablets. This may lead to layout and usability issues for your users.We detected the following resizability and orientation restrictions in your app:<activity android:name="io.intercom.android.sdk.activities.IntercomCarouselActivity" android:screenOrientation="PORTRAIT" />To improve the user experience for your app, remove these restrictions and check that your app layouts work on various screen sizes and orientations by testing on Android 16 and below.Would it be possible to avoid orientation restrictions in the SDK?

Hello, I’ve got a crash using the Android SDK but can’t say more than the device details and the stacktrace, which I report here.Hope you know more and got to fix it.Intercom Android SDK: v17.3.0Device: Samsung Galaxy A13 - Android 14Fatal Exception: java.lang.RuntimeException: Unable to destroy activity {myapppackagename/io.intercom.android.sdk.survey.ui.IntercomSurveyActivity}: java.lang.IllegalArgumentException: Detected multithreaded access to SnapshotStateObserver: previousThreadId=1163), currentThread={id=2, name=main}. Note that observation on multiple threads in layout/draw is not supported. Make sure your measure/layout/draw for each Owner (AndroidComposeView) is executed on the same thread. at android.app.ActivityThread.performDestroyActivity(ActivityThread.java:6149) at android.app.ActivityThread.handleDestroyActivity(ActivityThread.java:6181) at android.app.servertransaction.DestroyActivity