Mobile SDKs

Any word on when you'll support Catalyst apps on macOS? We've been using Intercom on our mobile app, and would love to use Carousels in the Mac App as well.

Hello, I am an Android Kotlin developer, and I am using your SDK's automatic survey feature, which is triggered by an event. Everything is working fine when I test it in my environment because minify and shrink are disabled. However, when I generate a release version where this scenario changes (minify and shrink are enabled), the survey stops working.I am using the ProGuard configuration provided in your GitHub documentation, as well as the ProGuards for OkHttp, Okio, and Retrofit (these last ones have been working in production for a long time in the code, it's not something recent, only Intercom is). Could you please assist me with this issue?Intercom SDK: 15.1.0 (Without push messaging)Compile SDK: 33Min SDK: 21Target SDK: 33Our logging is not throwing any type of errors.

Hello, the Compose version of my Android project is “1.4.1” and the intercom sdk version is “15.10.2”.The issue I am having is that the app crashes when I select an image from the user’s gallery. 

Release Date: 29-08-2024 🚀 Enhancements Added support for merged conversations

Release Date: 08-08-2024 🐛 Bug Fixes Support added for multiline attribute collector. Fixes an issue with canvas kit where some users were experiencing crashes. Fixes some minor UI issues. Note This release contains some beta features.

Hi,We are getting the following bug on React-Native Android, which is causing Play Store to reject our appBug: - React Native SDK 7.1.3- We open an article by using the method "Intercom.presentContent(IntercomContent.articleWithArticleId(9305883)) "- When the article we just get a screen that says "Something went wrong" (screenshot below)- FYI this works on iOS  

Execution failed for task ':app:mergeExtDexDebug'.> Could not resolve all files for configuration ':app:debugRuntimeClasspath'.> Failed to transform lifecycle-livedata-core-2.8.3.aar (androidx.lifecycle:lifecycle-livedata-core:2.8.3) to match attributes {artifactType=android-dex, asm-transformed-variant=NONE, dexing-enable-desugaring=true, dexing-enable-jacoco-instrumentation=false, dexing-is-debuggable=true, dexing-min-sdk=21, org.gradle.category=library, org.gradle.dependency.bundling=external, org.gradle.libraryelements=aar, org.gradle.status=release, org.gradle.usage=java-runtime}.> Execution failed for DexingWithClasspathTransform: /Users/name/.gradle/caches/transforms-3/3bfdb8d4164eceb9beb59b9f7ee5ce18/transformed/lifecycle-livedata-core-2.8.3-runtime.jar.> Error while dexing.

Open the modal of the intercom → swipe left and right → the app freezes as a result. Issue is only in IOS mobiles.

I'm seeing this weird error.TypeError: null is not an object (evaluating 'IntercomEventEmitter.UNREAD_COUNT_CHANGE_NOTIFICATION') I followed the guide on the official Github repo https://github.com/intercom/intercom-react-native#android. After trying the manual linking, I get a different error when building the app.> Task :intercom-react-native:generateDebugRFile FAILED Execution optimizations have been disabled for task ':intercom-react-native:generateDebugRFile' to ensure correctness due to the following reasons: - Gradle detected a problem with the following location: '/Users/bryamrodriguez/src/sammy-native/node_modules/@intercom/intercom-react-native/android/build/intermediates/packaged_manifests/debug'. Reason: Task ':intercom-react-native:generateDebugRFile' uses this output of task ':intercom_intercom-react-native:processDebugManifest' without declaring an explicit or implicit dependency. This can lead to incorrect results being p

Release Date: 23-08-2024 🚀 Enhancements Added the ability to disable swizzling. This can be done by adding the following value to your Info.plist: xml <key>IntercomDisableSwizzling</key> <true/> 🐛 Bug Fixes Fixed various memory leaks. Addressed some constraint-related issues in the SDK that were outputting warnings in the console.. Fixed a bug related to the Scroll to Bottom button in the conversation screen. Note This release contains some beta features.

Hi.I’m trying to write Android UI tests on the app with Intercom integrated.I’d like to check that Intercom main screen is opened after some actions made in our UI.However I’ve discovered, that Intercom uses Compose, that’s why usual techniques to find views ids are not working.Could you suggest if any semantics were used in your Compose code or how can I find any stable identifiers to check them in my tests?

BottomSheet for attaching images/videos to a message is overlapped by Navigation Bar if Navigation type is Buttons. 

ERROR - [HTTP 403] - Request failed: forbidden (403)

Hi,In our product we want to start using the Android Mobile SDK, but for only a set of users. When the app opens we don’t know if the user needs Intercom, we only have that information later in the process.In the iOS Mobile SDK we used the SDK without any issue but in Android we found a warning: Intercom must be initialized inside the application onCreate() method. Initializing anywhere else will result in Intercom not behaving as expected and could even result in the host app crashing. Calling the initialize in the onCreate will add this user to the pricing plan? It’s safe to call this method and later when we are sure that this user has intercom enabled call loginIdentifiedUser?Intercom.initialize(this, "your api key", "your app id")Thanks

Hi,We are currently experiencing an issue with the Intercom Android SDK (version 15.9.1) in our application while developing a new feature with event.When a user clicks on the refill button, we send an event to Intercom as per your documentation: https://developers.intercom.com/installing-intercom/android/using-intercom#submit-an-event.As a result, a small popup window appears at the bottom of the screen. However, this popup window does not disappear automatically after the user reads the message and returns to the previous screen. Instead, it remains persistent until the app is killed and reopened.This behavior differs from the iOS SDK, where the popup window disappears automatically once the message is read, and the user returns to the previous screen.The user can manually remove the popup by sliding it. Is the persistent popup designed to be removed only manually by the user, or is there a way to make it disappear automatically after the message is read? We have implemented the feat

I currently use Intercom's Android SDK in my App for customer support. Previously I was using the 'io.intercom.android:intercom-sdk:15.1.4' then I updated the SDK version to 'io.intercom.android:intercom-sdk:15.8.3' (currently the latest) version. After this Android permission issues start to come i.e. Devices running Android Version 12 and below cannot grant permissions. This started happening only when I upgraded the intercom's SDK version, reverting the version to the previous one solves the issue. I am asking the user to permit access to READ_EXTERNAL_STORAGE, which is getting denied.

Hello dear Support Team,after updating the Intercom SDK to version 15.2.0 our app crashing with the next Stacktrace: This happens when our own push notification will be consumed and the application will be send in background. After resuming the app from “recent apps” the crash happens. This behavior is noticed on different android versions from 11 to 14, and with Intercom SDK Versions 15.+, the same happens with 15.5.0.Thanks in advance for support!

Release Date: 18-07-2024 🐛 Bug Fixes Fixed an issue where the Powered By Intercom link could appear even when disabled. Note This release contains some beta features.

Release Date: 18-07-2024 🚀 Enhancements A newly designed composer for the messenger. 🐛 Bug Fixes Fixes an issue with text fields in surveys. Fixed issue allowing customers to start a conversation after reacting to an article. Fixes an issue to handle empty message parts for bot introductions. Note This release contains some beta features.

Our mobile development team has identified a significant memory leak in the latest iOS Intercom SDK 17.1.2. This is causing app crashes for many users.Observations: Memory Usage: Before integrating Intercom, our app uses ~50MB of RAM. After integration, RAM usage exceeds 200MB, primarily allocated by the SDK.  Maybe this post can be relevant:    Performance Issues: The app experiences periodic CPU and IO spikes, leading to further slowdowns. iOS may terminate the app if CPU usage exceeds 50% for over 180 seconds. A way to cause a Crash: Interrupting an image upload, retrying, and repeating reliably crashes the SDK. Memory Profiling Suggestion: The SDK significantly increases RAM usage with chat usage, especially with image handling. Profiling suggests the decodedImageUsingGraphicsImageRendererRefWithCGImageRef function consumes substantial memory. Photo handling: The SDK renders images poorly, seemingly sending them at their full file size without any optimization. This is a ma

Hi,Our app uses a static analysis tool called Veracode to analyze the source code and all third-party libraries for both Android and iOS apps.Veracode has detected 9 high-level security issues in the Android version of the Intercom SDK.The following issue was identified by Veracode in 9 places: Issue Description:This call contains a path manipulation flaw. The argument to the function is a filename constructed using untrusted input. If an attacker is allowed to specify all or part of the filename, it may be possible to gain unauthorized access to files on the server, including those outside the webroot, that would be normally be inaccessible to end users. The level of exposure depends on the effectiveness of input validation routines, if any.Recommendations:Validate all untrusted input to ensure that it conforms to the expected format, using centralized data validation routines when possible. When using black lists, be sure that the sanitizing routine performs a sufficient number of it

When opening the Intercom messenger to send messages, after tapping the initial prompt and being asked to type a question, sometimes the text input field for the message does not appear, and there is no way for the user to type. We’ve had reports of this happening from users and have videos of it happening, but have not been able to replicate this behaviour on the simulator. We’re encountering this issue on version 17.0.0

Environment:Intercom iOS SDK v17.1.2iOS v16, v17 STR: for us it reproduces if a conversation has a lot of messages (100 one word messages would be enough to reproduce the issue) open Message Composer using any available method select conversation that contains many messages (100 one word messages is enough for us to reproduce), you may notice the hang after this step type some message and send it  

Hey everyone, we have a lot of crashes from crashlytics related to NavGraph, production buildSDK version: 15.9.1We are unable to reproduce it, but it’s top crash for nowCould you please take a look?Fatal Exception: java.lang.IllegalArgumentException: Cannot have an empty start destination route       at androidx.navigation.NavGraph.setStartDestinationRoute(NavGraph.kt:346)       at androidx.navigation.NavGraph.setStartDestination(NavGraph.kt:331)       at androidx.navigation.NavGraphBuilder.build(NavGraphBuilder.java:187)       at androidx.navigation.compose.NavHostKt.NavHost(NavHost.kt:391)       at io.intercom.android.sdk.m5.navigation.IntercomRootNavHostKt$IntercomRootNavHost$1.invoke(IntercomRootNavHost.kt:39)       at io.intercom.android.sdk.m5.navigation.IntercomRootNavHostKt$IntercomRootNavHost$1.invoke(IntercomRootNavHost.kt:34)       at androidx.compose.runtime.internal.ComposableLambdaImpl.invoke(ComposableLambda.jvm.kt:109)       at androidx.compose.runtime.internal.Composab

ClassNotFoundExceptionDidn't find class "androidx.compose.ui.platform.ComposeView" on path: DexPathList[[zip file "/data/app/~~n484KKX1r-3zoEfjsBrAGQ==/com.android.truespaces-vuchoULl4z4i_2GC-keNLw==/base.apk"],nativeLibraryDirectories=[/data/app/~~n484KKX1r-3zoEfjsBrAGQ==/com.android.truespaces-vuchoULl4z4i_2GC-keNLw==/lib/arm64, /data/app/~~n484KKX1r-3zoEfjsBrAGQ==/com.android.truespaces-vuchoULl4z4i_2GC-keNLw==/base.apk!/lib/arm64-v8a, /system/lib64, /system_ext/lib64]]