Mobile SDKs

Phone details:iOS 26.2.1 iPhone 17 Pro MaxIntercom SDK details:Intercom (19.4.1) @intercom/intercom-react-native (9.5.0)The survey opens, we can go through and fill out the entire survey just fine.Swiping down to dismiss works just fine.However, the dismiss button DOES NOT work.I’ve seen other topics talking about this exact issue but none of them are resolved and just pass the blame to the customer:See images below showing that dimiss button is actually reacting to touch events as proof that it’s not some “overlay issue” and we are using Intercom’s latest 

There has a crash happened when opening preview for an uploading file in conversation, this only happened on vivo V1963A.  I'm using the latest version 17.4.2, and the crash still occurs. This was the crash: java.lang.RuntimeException: Failure delivering result ResultInfo{who=null, request=xxx, result=-1, data=Intent { (has extras) }} to activity {xxx/io.intercom.android.sdk.m5.IntercomRootActivity}: android.database.CursorIndexOutOfBoundsException: Index 0 requested, with a size of 0 The crash only happened on vivo V1963A with a specific path. Open the directory from the top left, select file manager, then documents, and then select any file, the crash will then occur. Thank you

All of sudden today our native Android crash started crashing whenever a user tried to access Intercom. This was the crash:java.lang.ClassNotFoundException - org.msgpack.core.buffer.MessageBufferUThe crash only happened with builds obfuscated by ProGuard. The crash still happened even after adding the keep rules according to the documentation:-keep class io.intercom.android.** { *; }-keep class com.intercom.** { *; } We solved the crash by adding the following to our proguard-rules.pro file: -keep class org.msgpack.** { *; }I have a couple of questions:Why did the crash start happening all of a sudden? Why is it not mentioned in the documentation that we need to keep org.msgpack classes unobfuscated? How can we be sure to prevent similar cr

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.

  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

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?  

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

There is a vulnerability not fixed even in latest Intercom Android SDK 17.4.2:org.msgpack:msgpack-core should be 0.9.11 or greater|    +--- io.intercom.android:intercom-sdk-base:17.4.2|    |    +--- io.ably:ably-android:1.5.0|    |    |    +--- io.ably:network-client-okhttp:1.5.0|    |    |    |    +--- io.ably:network-client-core:1.5.0|    |    |    |    \--- com.squareup.okhttp3:okhttp:4.12.0 (*)|    |    |    +--- org.msgpack:msgpack-core:0.8.11Could you please update io.ably:ably-android to latest 1.6.1 to see if it fixes the vulnerability?Thanks!More Infoorg.msgpack:msgpack-core(Maven)< 0.9.110.9.11SummaryAffected Components:org.msgpack.core.MessageUnpacker.readPayload()org.msgpack.core.MessageUnpacker.unpackValue()org.msgpack.value.ExtensionValue.getData()A denial-of-service vulnerab

Hi Intercom team, we receive several errors after trying to login a user with attributes using react-native sdk.We check if the user is logged in before making a Intercom.loginUserWithUserAttributes call.A short stack-trace for the error we receive: code: 102,domain: io.intercom.ios.error.network,message: Error in loginUserWithUserAttributes,name: Error,NSLocalizedDescription: HTTP Error: 400 bad requestWe send email and userId to the method call, like this: Intercom.loginUserWithUserAttributes({ email, userId }) Could you help us understand why we still get an error, I’ve run a console.log for both email and userId and both seem legit.

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?