Mobile SDKs

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.

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)