Mobile SDKs

Our Android app is suddenly crashing for any user that tries to open a collection of articles inside Intercom. SDK version 14.0.0. Opening individual articles seems to work fine, just not collections.We have a pre-release version with Intercom version 15.10.3 and this does not crash, but this is not helpful for the thousands of users on the old version. I don’t see anywhere saying SDK 14.0.0 is deprecated. Also, iOS is working fine. No changes have been made our side. Is there an issue Intercom’s side here?Crash details:Fatal Exception: java.util.NoSuchElementException: List is empty. at kotlin.collections.CollectionsKt___CollectionsKt.first(_Collections.kt:214) at io.intercom.android.sdk.m5.helpcenter.components.CollectionSummaryComponentKt.constructByAuthorsText(CollectionSummaryComponent.kt:108) at io.intercom.android.sdk.m5.helpcenter.components.CollectionSummaryComponentKt.CollectionSummaryComponent(CollectionSummaryComponent.kt:72) at io.intercom.android.s

Fatal Exception: java.io.FileNotFoundException: https://downloads.intercomcdn.com/i/o/139802627/c29e7134f9cd57088cf1d07b/blue+tear.png?expires=1729994400&signature=525d4a03fac180d11f7678691fbfa5f8ed5622dbd059a77c01227ffcc6b2a3a2&req=dSMuHsl8m4NYFb4f3HP0gIDAMfuWTACfTE0A7ru2V8zDHLslNtDMsv%2Fu0c%2Bq%0AXJ8eWqt3jD%2Bxi9f0GA%3D%3D%0A       The Above crash is reported in crashlytics, i am unable to reproduce the exception also i am using the latest release of intercom, the above crash is occurring for android 10Please help!

Hello, I am an Xamarin/Maui developer, and I am using intercom SDK for Android.I have created Xamarin Android binding for all required projects. Everything is working fine when I run the things without r8 shrinker. However, when I generate a release version where we have R8 shrinker enabled, I am getting compile time issues.Issues: 1>R8: Error  : A type variable is not in scope.1>R8: Error  : A type variable is not in scope.1>R8: Error  : A type variable is not in scope.1>R8: Error  : A type variable is not in scope.1>R8: Error  : A type variable is not in scope.1>R8: Error  : A type variable is not in scope.1>R8: Error  : A type variable is not in scope.1>R8: Error  : A type variable is not in scope.1>R8: Error  : A type variable is not in scope.1>R8: Error  : A type variable is not in scope.1>R8: Error  : A type variable is not in scope.1>R8: Error  : A type variable is not in scope.1>R8: Error  : A type variable is not in scope.1>R8: Error  

When will be the latest SDK 15.11.0 be available on https://mvnrepository.com/ ? Please update

Hi!I’ve encountered an issue with configuring push notifications in Intercom on iOS.I’m using the latest Intercom SDK (18.1.0). According to the documentation, I’ve added IntercomAutoIntegratePushNotifications with the value NO in Info.plist and am manually handling push notifications in the userNotificationCenter(_:didReceive:withCompletionHandler:) method as instructed: func userNotificationCenter(_ center: UNUserNotificationCenter, didReceive response: UNNotificationResponse, withCompletionHandler completionHandler: @escaping () -> Void) { let userInfo = response.notification.request.content.userInfo if Intercom.isIntercomPushNotification(userInfo) { Intercom.handlePushNotification(userInfo) } completionHandler(.noData)}However, Intercom notifications are not being handled correctly - it seems like the Intercom.handlePushNotification(_:) function is not being triggered at all. Has anyone faced a similar issue with manually handling push notifications on iOS? I’

We are experiencing a few crashes with the following exception on Intercom Android SDK 15.10.13. Fatal Exception: java.net.MalformedURLException: no protocol:        at java.net.URL.<init>(URL.java:601)       at java.net.URL.<init>(URL.java:498)       at java.net.URL.<init>(URL.java:447)       at io.intercom.android.sdk.ui.preview.viewmodel.PreviewViewModel.prepareBitmap(PreviewViewModel.kt:275)       at io.intercom.android.sdk.ui.preview.viewmodel.PreviewViewModel.access$get_state$p(PreviewViewModel.kt:35)       at io.intercom.android.sdk.ui.preview.viewmodel.PreviewViewModel.access$prepareBitmap(PreviewViewModel.kt:35)       at io.intercom.android.sdk.ui.preview.viewmodel.PreviewViewModel$saveImage$1.invokeSuspend(PreviewViewModel.kt:89)       at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)       at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:104)       at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(

React Native SDK, after first notification, subsequent messages do not trigger the `IntercomUnreadConversationCountDidChangeNotification` or update the unread conversations count. On Android, this works fine.I am getting this when I inspect further: Connection not set before response is received, failing taskTask <2DDF32F5-C689-494A-86DA-D797913F6B13>.<1> finished with error [-1005] Error Domain=NSURLErrorDomain Code=-1005 "The network connection was lost." UserInfo={NSErrorFailingURLStringKey=https://nexus-websocket-a.intercom.io/pubsub/5-u6Cx9ENZy3p6sdjM9V1iCe5wz7buKXpHc6VNBLk1HCGo5QC7Dgg_aFvSJMBYdr9mwDbTckhsvRxWmrp8fH1JAVh5VXifBJZq9Pt9?X-Nexus-Version=ios.0.17.0, NSErrorFailingURLKey=https://nexus-websocket-a.intercom.io/pubsub/5-u6Cx9ENZy3p6sdjM9V1iCe5wz7buKXpHc6VNBLk1HCGo5QC7Dgg_aFvSJMBYdr9mwDbTckhsvRxWmrp8fH1JAVh5VXifBJZq9Pt9?X-Nexus-Version=ios.0.17.0, _NSURLErrorRelatedURLSessionTaskErrorKey=(    "LocalWebSocketTask <2DDF32F5-C689-494A-86DA-D797913F6B13>.<1

We are experiencing a few crashes with the following exception on Intercom Android SDK 15.6.1. Can you help handle the exception gracefully? Fatal Exception: java.net.MalformedURLException: no protocol: at java.net.URL.<init>(URL.java:601) at java.net.URL.<init>(URL.java:498) at java.net.URL.<init>(URL.java:447) at io.intercom.android.sdk.ui.preview.viewmodel.PreviewViewModel.prepareBitmap(PreviewViewModel.kt:114) at io.intercom.android.sdk.ui.preview.viewmodel.PreviewViewModel.access$get_state$p(PreviewViewModel.kt:33) at io.intercom.android.sdk.ui.preview.viewmodel.PreviewViewModel.access$prepareBitmap(PreviewViewModel.kt:33) at io.intercom.android.sdk.ui.preview.viewmodel.PreviewViewModel$saveImage$1.invokeSuspend(PreviewViewModel.kt:68) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:108) at kotlinx.corou

Hello, intercom community. It seems the messenger in the mobile app doesn't allow to attach the files inside the dialogue. I would like to provide this option to our customers. Could let me know if that's possible?

After upgrading to React Native Intercom SDK from 6.8.1 to 7.1.2 we are getting the following error whenever we start the android app: 

the displayed message interrupts the use of the bottom navigation barHow can i change the display of position message?

Hello,We have an issue when using Expo + CustomerIO + Intercom for notifications, on Android. We don't receive notifications from Intercom after installing CustomerIO.On iOS, everything works fine, we receive notifications from CustomerIO as well as from Intercom without any issue.**SDK version:**{    "@intercom/intercom-react-native": "^7.1.3",    "customerio-expo-plugin": "^1.0.0-beta.15",    "customerio-reactnative": "3.7.0"}**Environment:** Android only**Are logs available?** No logs available**Describe the bug**Push notifications are not received from Intercom after installing CIO SDK.**To Reproduce**- Create a fresh expo app- Install intercom (and add the plugin in `app.config.ts`)- Push notifications are received from Intercom- Install CIO sdk (and add the plugin in `app.config.ts`)- Push notifications are not received from Intercom anymore**Expected behavior**We would expect to be able to receive both CIO and Intercom notifications.**Additional context**For context, we already

​ 2024-09-05 11:40:09.795 4736-4736 AndroidRuntime ipnossoft.rma.free E FATAL EXCEPTION: main Process: ipnossoft.rma.free, PID: 4736 java.lang.NoSuchMethodError: No static method rememberModalBottomSheetState(ZLkotlin/jvm/functions/Function1;Landroidx/compose/runtime/Composer;II)Landroidx/compose/material3/SheetState; in class Landroidx/compose/material3/ModalBottomSheet_androidKt; or its super classes (declaration of 'androidx.compose.material3.ModalBottomSheet_androidKt' appears in /data/app/~~g_FRDbFowwX3NIDZuLr61w==/ipnossoft.rma.free-uVLziORaSPfDo1O1hhh66A==/base.apk) at io.intercom.android.sdk.m5.conversation.ui.ConversationScreenKt.ConversationScreenContent

2024-09-05 11:40:09.795 4736-4736 AndroidRuntime ipnossoft.rma.free E FATAL EXCEPTION: main Process: ipnossoft.rma.free, PID: 4736 java.lang.NoSuchMethodError: No static method rememberModalBottomSheetState(ZLkotlin/jvm/functions/Function1;Landroidx/compose/runtime/Composer;II)Landroidx/compose/material3/SheetState; in class Landroidx/compose/material3/ModalBottomSheet_androidKt; or its super classes (declaration of 'androidx.compose.material3.ModalBottomSheet_androidKt' appears in /data/app/~~g_FRDbFowwX3NIDZuLr61w==/ipnossoft.rma.free-uVLziORaSPfDo1O1hhh66A==/base.apk) at io.intercom.android.sdk.m5.conversation.ui.ConversationScreenKt.ConversationScreenContent(C

We migrated the SDK version from 15.0.0 to 15.5.0 and then saw the error described in the header. In 15.0.0, our MAIN/LAUNCHER activity, which processes information about clicks, was initially opened, than it opens Intercom Chat. After migrating to 15.5.0, this behavior broke. The problem is that our activity opens immediately after the intercom chat activity opens. This leads to confusion for the user. For example, if the user clicks on the "Back" button from our application, they are taken to the intercom chat, which is not expected.The service for processing looks like this:@AndroidEntryPointclass CloudService : FirebaseMessagingService() { private val intercomPushClient = IntercomPushClient() override fun onNewToken(token: String) { super.onNewToken(token) intercomPushClient.sendTokenToIntercom(application, token) } override fun onMessageReceived(message: RemoteMessage) { super.onMessageReceived(message) val remoteMsg = message.data if

We need to show users that there are additional unread responses - how is this done?Seems the Android SDK behaviour differs and every new message is displayed as it comes in.

Hi there! I’ve been debugging an issue with our React Native app’s implementation of the `loginUnidentifiedUser` + `loginUserWithUserAttributes` combo, and noticed that while the Android module has a few descriptive cases before being handled by `IntercomError.getErrorMessage()`, the iOS module simply throws a generic error for all failures.Is there a reason why actual request errors aren’t being bubbled up through these methods? For example, if the login failed due to the Identity Verification check, I feel like it would be reasonable to include that and the related code in the failure callback.Thanks!

Hi there, we’ve got a barebones React Native app running the Intercom SDK version 7.1.3 - we’ve been trying to follow the documentation to setup Universal linking (including the appropriate Info.plist attribution), so our CX team can link specific places inside the app from their conversations https://developers.intercom.com/installing-intercom/react-native/deep-linking - but we’ve found that it correctly routes behind the modal for Intercom, but Intercom still opens up Safari (this is on an iOS test device) even though the specified domain is included in the ` IntercomUniversalLinkDomains` property in `Info.plist` - we are using AppsFlyer if that helps / aids anything, and React Navigation under the hood. (So if we head back to the app and dismiss Intercom, we are in the correct place)Thanks!

Release Date: 01-10-2024 🐛 Bug Fixes Fixed a crash that could occur when calling setDeviceToken. This can now be worked around by disabling swizzling. Resolved an issue where the conversation would jump after loading completed. Corrected the accessibility of the “Powered by Intercom” link text. 🚀 Enhancements Improved memory management & performance in the Conversation screen. Note This release contains some beta features.

After upgrading the intercom to version 7.1.3, Android fails to build. Execution failed for task ':app:mergeExtDexDebug'.> Could not resolve all files for configuration ':app:debugRuntimeClasspath'. > Failed to transform lifecycle-livedata-core-2.8.1.aar (androidx.lifecycle:lifecycle-livedata-core:2.8.1) to match attributes {artifactType=android-dex, asm-transformed-variant=debug, dexing-enable-desugaring=true, dexing-enable-jacoco-instrumentation=false, dexing-is-debuggable=true, dexing-min-sdk=25, 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 DexingNoClasspathTransform: /Users/gustavojorge/.gradle/caches/transforms-3/9fc0c96944c3586bc20019947323a0d6/transformed/lifecycle-livedata-core-2.8.1-runtime.jar. > Error while dexing.* Try:> Run with --info or --debug option to get more log output.> Run with --scan to get ful

Is it possible to change the Data Hosting Region Configuration at runtime? We’re using native Android and iOS apps. The documentation says we need to set the region in the AndroidManifest or the plist (iOS). But we have US and AU customers. Attempting to just change the app ID and API key grabs most of the helpful stuff (I can see the icon color changing for example...) but when opened, the Intercom app just says “Something’s gone wrong.”Are mobile apps able to support multiple regions with Intercom?

After upgrading to Compose 1.7.0, I get the following crash.Process: com.toasttab.toastoperator.preprod, PID: 23851java.lang.NoSuchMethodError: No static method rememberModalBottomSheetState(ZLkotlin/jvm/functions/Function1;Landroidx/compose/runtime/Composer;II)Landroidx/compose/material3/SheetState; in class Landroidx/compose/material3/ModalBottomSheet_androidKt; or its super classes (declaration of 'androidx.compose.material3.ModalBottomSheet_androidKt' appears in /data/app/~~b5UPeePLMTwW-g8HyLVhuA==/com.toasttab.toastoperator.preprod-94iR5SgFn2i9HyAs8uyDnA==/base.apk)at io.intercom.android.sdk.m5.conversation.ui.ConversationScreenKt.ConversationScreenContent(ConversationScreen.kt:371)at io.intercom.android.sdk.m5.conversation.ui.ConversationScreenKt.ConversationScreen(ConversationScreen.kt:189)at io.intercom.android.sdk.m5.navigation.ConversationDestinationKt$conversationDestination$13.invoke(ConversationDestination.kt:178)at io.intercom.android.sdk.m5.navigation.ConversationDestina

Release Date: 18-08-2024 🚀 Enhancements Updated to support iOS 18 and Swift 6 concurrency for all public interface types. The sections model has been previously deprecated in the Help Center API. It has now been removed. Any uses of sections should now be replaced with collections.

Hi! We’re are currently setting up Intercom in our React native + Expo application. Everything regarding push notifications is working. We can receive push notifications on both android and iOS platforms. However, deep link are only working on iOS.  Our intent filter is as follows:const BASE_MW_INTENT = { autoVerify: true, action: "VIEW", category: ["BROWSABLE", "DEFAULT"],};const MW_ANDROID_INTENT_FILTERS = [ // Deep links config. { ...BASE_MW_INTENT, data: [ { scheme: "ourcompany", host: "ourcompany.site.nl", }, ], }, // Universal links config. { ...BASE_MW_INTENT, data: UNIVERSAL_LINKS_DATA, },]; And our deep link is as follows:ourcompany://ourcompany.site.nl/mijn/account/abonnementThis again works on iOS, but not on android. The following also do not work:ourcompany://ourcompany.nl/mijn/account/abonnementhttps://ourcompany.nl/mijn/account/abonnementWhich are all valid urls for our app. Launching any of these via the abd CLI does work,

Hello!We are using push notifications with Intercom to notify users of important events in our app.We’d like to know if Intercom supports silent push notifications for iOS & Android i.e. push notifications that we send to our apps that do not display any alerts/sounds, but are just used from our apps, to do actions such as reloading UI elements.Thank you.