Mobile SDKs

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]]

I’m using the latest version of the sdk. Here’s the crash output:java.lang.IncompatibleClassChangeError: Class 'android.content.res.XmlBlock$Parser' does not implement interface 'hk.a' in call to 'int hk.a.next()' (declaration of 'h1.a' appears in base.apk) at h1.a.a(SourceFile:6) at u1.e.c(SourceFile:66) at u1.e.d(SourceFile:113) at io.intercom.android.sdk.m5.components.HomeItemKt.HomeItem(SourceFile:112) at io.intercom.android.sdk.m5.home.ui.components.SpacesCardKt$SpacesCard$1.invoke(SourceFile:50) at io.intercom.android.sdk.m5.home.ui.components.SpacesCardKt$SpacesCard$1.invoke(SourceFile:1) at t0.b.e(SourceFile:50) at t0.b.invoke(SourceFile:1) at g0.b2$a.invoke(SourceFile:40) at g0.b2$a.invoke(SourceFile:1) at t0.b.e(SourceFile:50) at t0.b.invoke(SourceFile:1) at m0.v.a(SourceFile:41) at g0.b2.a(SourceFile:466) at g0.j.a(SourceFile:146) at io.intercom.android.sdk.m5.home.ui.components.S

Release Date: 14-06-2024 🚀 Enhancements It is now possible to send push notifications to the Simulator. 🐛 Bug Fixes Fixed an issue where it was not possible to close modal view that was opened from a Messenger App. The message composer is now always displayed on the conversation screen when appropriate. When a conversation is closed, form entry is disabled on the conversation screen. Made some minor UI bug fixes.

Hi! When building the application in Xcode 14.0 b6, it shows the following error:Thread Performance Checker: Thread running at QOS_CLASS_USER_INITIATED waiting on a lower QoS thread running at QOS_CLASS_DEFAULT. Investigate ways to avoid priority inversions PID: 743, TID: 31796 Backtrace ================================================================= 3 Intercom 0x000000010440805c IntercomSDK_PINRemoteImageManagerSubclassOverridesSelector + 80944 4 Intercom 0x0000000104407e48 IntercomSDK_PINRemoteImageManagerSubclassOverridesSelector + 80412 5 libdispatch.dylib 0x0000000103c2a04c _dispatch_client_callout + 20 6 libdispatch.dylib 0x0000000103c2bbbc _dispatch_once_callout + 136 7 Intercom 0x0000000104407de0 IntercomSDK_PINRemoteImageManagerSubclassOverridesSelector + 80308 8 Intercom 0x0000000104403d5c IntercomSDK_PINRemoteImageManag

Hello. I’ve found this report, but didn’t find the answer, so I’ll write my own example.We are faced with similar problem, after updating to version 17.0.1 from the version 14.0.7 (video in attachment). I can’t downgrade the library to the lowest version, due to we updated it to avoid another issues, which have been fixed in 17.x.  This issue is not reproducible on versions below 16.x.x. If you’ll have any additional question, please contact me. 

I’m using the Android SDK version and I got this crash in the intercom. Crash Stacktrace 

We are facing an issue in our app that shows the following error messages in our Firebase. They are for the same issue with other Exceptions too, but these are the first two.We have tried to retrace the stacktrace locally but nothing was different.### First error message      Fatal Exception: java.lang.ExceptionInInitializerError:       at kotlin.reflect.jvm.internal.impl.resolve.jvm.JvmPrimitiveType.values(JvmPrimitiveType.java:722)       at kotlin.reflect.jvm.internal.impl.builtins.jvm.JavaToKotlinClassMap.<clinit>(JavaToKotlinClassMap.kt:722)       at kotlin.reflect.jvm.internal.RuntimeTypeMapper.mapJvmClassToKotlinClassId(RuntimeTypeMapper.java:116)       at kotlin.reflect.jvm.internal.KClassImpl.getClassId(KClassImpl.kt:116)       at kotlin.reflect.jvm.internal.KClassImpl.access$getClassId(KClassImpl.kt:5)       at kotlin.reflect.jvm.internal.KClassImpl$Data$simpleName$2.invoke(KClassImpl.java:5)       at kotlin.reflect.jvm.internal.KClassImpl$Data$simpleName$2.invoke(KClass

I’m moving our app from the old AppDelegate to the new SceneDelegate. I’m now seeing this stack trace before my app even gets to run. It seems to be stuck on a lock that never resolves. This is on a test run, is there a way I can disable loading Intercom while running tests? Why on earth is Intercom attempting to load images on a +load, who thought this was a good idea. * thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGSTOP  * frame #0: 0x0000000115293fa8 libsystem_kernel.dylib`__psynch_mutexwait + 8    frame #1: 0x00000001155107b0 libsystem_pthread.dylib`_pthread_mutex_firstfit_lock_wait + 80    frame #2: 0x000000011550e2f8 libsystem_pthread.dylib`_pthread_mutex_firstfit_lock_slow + 244    frame #3: 0x0000000115a74aec Intercom`-[IntercomSDK_PINDiskCache isTTLCache] + 20    frame #4: 0x0000000115a7cdbc Intercom`-[IntercomSDK_PINCache(PINRemoteImageCaching) diskCacheIsTTLCache] + 32    frame #5: 0x0000000115a85934 Intercom`-[IntercomSDK_PINRemoteImageManager initWith

Running the SDK version "15.7.0" on my pixel 8 using android 14, when adding a video attachement the SDK is crashing. We find this error in the field on our crash monitor tool. Summary of crash iscom.google.android.exoplayer2.ui.AspectRatioFrameLayout cannot be cast to androidx.media3.ui.AspectRatioFrameLayoutI run the dependencies of our application and Intercom is not using the `com.google.android.exoplayer2`. I was able to reproduce and record the crash but it look like i can’t add video to this conversation.Let me know if you need more information  

SDK version: 16.6.1We’re unable to reproduce this issue, but it seem to occur in Intercom chat.Here’s the crashlog:IntercomSDK_saveViewHierarchycom.apple.main-thread0 libsystem_kernel.dylib 0x1808 mach_msg2_trap + 81 libsystem_kernel.dylib 0x5008 mach_msg2_internal + 802 libsystem_kernel.dylib 0x4f20 mach_msg_overwrite + 4363 libsystem_kernel.dylib 0x4d60 mach_msg + 244 CoreFoundation 0x53f5c __CFRunLoopServiceMachPort + 1605 CoreFoundation 0x53600 __CFRunLoopRun + 12086 CoreFoundation 0x52cd8 CFRunLoopRunSpecific + 6087 GraphicsServices 0x11a8 GSEventRunModal + 1648 UIKitCore 0x40a90c -[UIApplication _run] + 8889 UIKitCore 0x4be9d0 UIApplicationMain + 34010 Runner 0xbf74 main + 12 (AppDelegate.swift:12)11 ??? 0x1b2aa9e4c (Missing)com.apple.uikit.eventfetch-thread0 libsystem_kernel.dylib

Himy intercom is connected with IOS but In android, it is crashing with latest SDK 7.1.1details as below:  ClassNotFoundExceptionDidn't find class "androidx.compose.ui.platform.ComposeView" on path: DexPathList[[zip file "/data/app/~~_6n0USz8LnZCXj6M1KD4qg==/com.android.truespaces-wtWLOzkW30uslK-SfrqcEg==/base.apk"],nativeLibraryDirectories=[/data/app/~~_6n0USz8LnZCXj6M1KD4qg==/com.android.truespaces-wtWLOzkW30uslK-SfrqcEg==/lib/arm64, /data/app/~~_6n0USz8LnZCXj6M1KD4qg==/com.android.truespaces-wtWLOzkW30uslK-SfrqcEg==/base.apk!/lib/arm64-v8a, /system/lib64, /system_ext/lib64]]images as:  Can you please suggest how can we resolve this issue? Thanks 

Hey all, I love using the events via the Intercom iOS SDK. For some actions, users might trigger large amount of events(~30 in 1 min). Should I batch these events myself or the Intercom SDK is already handling it?  Specifically, do I need to batch events myself before calling this method?Intercom.logEvent(withName: event, metaData: metadata) Thanks!

Release Date: 28-05-2024 🐛 Bug Fixes Fixed some memory issues that impacted a small number of users. Fixed an issue that was preventing some modals from closing correctly. Removed Xcode console warning.

App crashes on user entering Intercom interface, here is crash logs from Crasklytics. Fatal Exception: NSInternalInconsistencyException0 CoreFoundation 0xc7bc __exceptionPreprocess1 libobjc.A.dylib 0x18ea0 objc_exception_throw2 Foundation 0x6aac24 _userInfoForFileAndLine3 UIKitCore 0x7aa458 -[UICollectionView _Bug_Detected_In_Client_Of_UICollectionView_Invalid_Batch_Updates:]4 UIKitCore 0x2fec4c -[UICollectionView _endItemAnimationsWithInvalidationContext:tentativelyForReordering:animator:collectionViewAnimator:]5 UIKitCore 0x25ef54 -[UICollectionView _updateRowsAtIndexPaths:updateAction:updates:]6 UIKitCore 0x25eda4 -[UICollectionView insertItemsAtIndexPaths:]7 Intercom 0x139d30 (Missing UUID 97c5fb2d3c3d3fe5b90a2180a2c2ccbc)8 CoreFoundation 0x414b8 __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__9