Merge Conversations & Tickets Beta is Back!
Engage users of your mobile app with an onboarding and support experience powered by Intercom
Recently active
Release Date: 11-12-2024 🐛 Bug Fixes Solves a crash in carousels. Addressed issue where video input wasn’t available in a conversation. Fixes issue where first part in a conversation would fail to show as failed in the scenario where it didn’t send. Resolved some layout issues in the conversation screen for users with large font sizes enabled. Note This release contains some beta features.
Execution failed for task ':app:mergeExtDexDevelopmentDebug'.> Could not resolve all files for configuration ':app:developmentDebugRuntimeClasspath'. > Failed to transform intercom-sdk-base-15.11.3.aar (io.intercom.android:intercom-sdk-base:15.11.3) to match attributes {artifactType=android-dex, asm-transformed-variant=developmentDebug, dexing-enable-desugaring=true, dexing-enable-jacoco-instrumentation=false, dexing-is-debuggable=true, dexing-min-sdk=24, org.gradle.category=library, org.gradle.dependency.bundling=external, org.gradle.libraryelements=aar, org.gradle.status=release, org.gradle.usage=java-runtime}.
I have determined that Our iPad app is experiencing Airplay issues that are being caused by the Intercom API. Setup:Intercom.setApiKey(apiKey, forAppId: appId)let userAttributes = ICMUserAttributes()userAttributes.userId = user.userIDIntercom.setUserHash(userHash)Intercom.loginUser(with: userAttributes) Steps to reproduce:cold launch the app Have above code run for Authenticated users Turn on Airplay to TV or Apple TV Issue: External screen is blackNote: Turning airplay off and back on solves the issue. Troubleshooting:Commenting the following lines of code solves the issue:Intercom.setUserHash(userHash)Intercom.loginUser(with: userAttributes)I have tried disabling Intercom swizzling as per your documentation but it has no affect. Currently using Intercom 17.4.0
I recently updated my intercom version from v15.10.0 to v15.11.2 because my app started to crash whenever a user tries to type a message. After upgrading, my app crashes whenever a user opens a chat or tries to start a new chatError log for v15.10.0java.lang.IllegalArgumentException: offset(1) is out of bounds [0, 0] at androidx.compose.ui.text.MultiParagraph.requireIndexInRangeInclusiveEnd(MultiParagraph.kt:913) at androidx.compose.ui.text.MultiParagraph.getCursorRect(MultiParagraph.kt:748) at androidx.compose.ui.text.TextLayoutResult.getCursorRect(TextLayoutResult.kt:553)Error log for v15.11.2java.lang.IllegalArgumentException: no paragraph (layoutCache=ParagraphLayoutCache(paragraph=null,
We’re experiencing a slow launch time in our SwiftUI app, about 35% of the slow launch time is caused by Intercom initialization. The stack trace indicates that multiple functions within the Intercom SDK, especially the initialization processes involving IMCCrashHandler, IMCConfig, HomeConfig, and HomeHeader, are contributing significantly to app launch latency. The UIKitCore and CoreImage components (like UIGraphicsImageRenderer and CIImage) invoked through ICAssets.backgroundImageViewWith also add processing overhead, which may impact the performance during launch.Here is the full stack trace given by XCodes tools:dyld start1. App.main() - SwiftUI2. AppDelegate.application(_:didFinishLaunchingWithOptions:) - SwiftUI3. IMCCrashHandler swizzleDidFinishLaunchingWithOptions - Intercom └ IMCCrashHandler sharedConfig - Intercom4. IntercomSDK_SentrySDK startWithConfigureOptions - Intercom5. IMCCrashHandler configureTags - Intercom6. IMCConfig sharedConfig - Intercom7. IMCConfig configFr
Hi!We’re experiencing a non negligible amount of crashes with our iOS app. We’re using the Intercom iOS SDK v18.2.0 (AKA the latest). As far as we can see, the user goes into the intercom integration, and at some point it crashes.Here is the crash-logs from Sentry: OS Version: iOS 18.0.1 (22A3370)Report Version: 104Exception Type: EXC_CRASH (SIGABRT)Crashed Thread: 0Application Specific Information:Expected dequeued view to be returned to the collection view in preparation for display. When the collection view's data source is asked to provide a view for a given index path, ensure that a single view is dequeued and returned to the collection view. Avoid dequeuing views without a request from the collection view. For retrieving an existing view in the collection view, use -[UICollectionView cellForItemAtIndexPath:] or -[UICollectionView supplementaryViewForElementKind:atIndexPath:]. Dequeued view: <IntercomSDK_ITBBlockCollectionViewCell: 0x1224ccc00; baseClass = UICollectionViewCell;
Intercom crashes every time you try to attach any type of content (even embedded gifs) on Android 9java.lang.NullPointerException at androidx.compose.ui.node.LayoutNodeDrawScope.drawContent(LayoutNodeDrawScope.kt:49) at io.intercom.android.sdk.m5.conversation.ui.ConversationScreenKt$ConversationScreenContent$32$1$1.invoke(ConversationScreen.kt:581) at io.intercom.android.sdk.m5.conversation.ui.ConversationScreenKt$ConversationScreenContent$32$1$1.invoke(ConversationScreen.kt:580) at androidx.compose.ui.graphics.drawscope.DrawScope$record$1.invoke(DrawScope.kt:1077) at androidx.compose.ui.graphics.drawscope.DrawScope$record$1.invoke(DrawScope.kt:941) at androidx.compose.ui.graphics.layer.GraphicsLayer$clipDrawBlock$1.invoke(AndroidGraphicsLayer.android.kt:71) at androidx.compose.ui.graphics.layer.GraphicsLayer$clipDrawBlock$1.invoke(AndroidGraphicsLayer.android.kt:66
Hello, I’m experiencing a problem where the Intercom chat does not open when a user taps on a push notification on iOS. I have implemented the Intercom React Native plugin as per the documentation, and the messaging functionality works perfectly. Notifications are received correctly, but tapping on them does not open the chat as expected. Environment Details: • Platform: iOS• React Native Version: 0.74• Intercom React Native Plugin Version: 8.1.0 Problem Description: • The Intercom messenger is fully integrated into my app, and users can send and receive messages without any issues.• Push notifications from Intercom are successfully delivered to the device.• According to the documentation, tapping on a push notification should automatically open the relevant chat within the app. However, this is not happening on iOS.• When I tap on a push notification while the app is closed, the app opens but does not display the chat. Instead, it remains on the previous screen or the home screen.• I
Hello, I was wondering if there is a way to listen to the “Send Us Messages” event to track the click?SDK is used on Android - its version is 12.5.3
Hello,I faced with unexpected experience when I cannot to capture video in Intercom messenger using iOS SDK since 17.2.0. Could you please help me to resolve this issue?My steps:Update iOS SDK to 18.2.0. Run the app, check that there is Intercom’s warning “Add NSMicrophoneUsageDescription...” in Xcode console. Add NSMicrophoneUsageDescription to Info.plist according to Installation guide, step 2. Run the app again, check the message is not printed. Open Intercom messenger, start a new conversation. Press a green plus icon. It opens an action sheet, choose Camera. The app asks only for camera permission, not microphone. Allow camera usage. Camera opens → only photo capturing is available, not video. Change SDK version to 17.1.2. Run the app, repeat step 5, press a grey camera icon. The app asks for microphone permission. Allow it. Camera opens. → Both options, Photo and Video, are available for choosing. Update SDK to 17.2.0, repeat steps 5-7. → Again, only photo capturing is availa
Release Date: 01-11-2024 📱 New Feature Added the ability to upload files to a conversation. 🚀 Enhancements Added new API isUserLoggedIn. This enables developers to determine if a user is currently logged in to Intercom. Added new API fetchLoggedInUserAttributes. This enables developers to retrieve the attributes of the currently logged in user. 🐛 Bug Fixes Fixed some layout issues in the conversation view. Improvements to the photo previewer. Fixes some colour accessibility issues throughout the SDK. Fixes issue where clicking on the CTA in a post would not dismiss it.
A Mobile Software Development Kit (SDK) is a collection of tools, libraries, and APIs that help developers create apps for platforms like Android or iOS. It simplifies app development by providing pre-built components for features such as user authentication, payment systems, and analytics.Benefits of Mobile SDKs:Faster Development: Reduces coding effort with ready-to-use tools. Consistency: Ensures reliable implementation across apps. Scalability: Supports growing user bases and feature additions. Enhanced Experience: Enables features like push notifications and smooth integrations.Popular SDKs:Firebase: For analytics and crash reporting. Facebook SDK: For social login and ad integration. Apple iOS SDK & Android SDK: Native app development essentials.Mobile SDKs save time, streamline workflows, and allow developers to focus on creating innovative, user-friendly apps.
Starting Android intercom SDK 15.10.2 and even in Latest 15.10.3 and 15.11.0, In Andorid messenger if a Workflow has been already triggered, it always remain there, No other Workflows get triggered afterwards.Eg. If Workflow-1 is trigger, then Workflow-2 is never triggered, even for the Rules of Workflow-2, We always see Workflow-1.This was fine until 15.10.1. Kindly resolve this ASAP.
We are currently working on our upcoming release to the Google Play Store, ensuring compatibility with Android 15. As part of this effort, we have recently updated our app to use the latest version of the Intercom SDK (15.9.1).During our testing phase, we encountered an issue specific to devices running Android 15. The problem pertains to the UI when attaching a video or image in the Intercom messenger.The "X" close button overlaps with the status bar, making it difficult to close the attachment preview.This behavior is observed only on Android 15 and seems related to the new edge-to-edge enforcement introduced in this version of Android.Here are the steps to reproduce the issue:1. Open the Intercom messenger in our app.2. Click on the attachment icon and choose Gallery.3. Select an image or video.4. Observe that the close ("X") button overlaps with the status bar, making it difficult to close the preview. You can view a screen shot of the issue here: Intercom UI Issue android 15 on at
The app sometimes crashes when adding video content, even after adding Media3 alongside the existing com.google.android.exoplayer:exoplayer. Crashes have reduced but still occur on various devices. Intercom SDK version is 15.11.0
Hey, After migrating from "@intercom/intercom-react-native": "^3.0.5",to latest version "@intercom/intercom-react-native": "^4.0.1",the displaying of specific helpcenter collections does not work anymore.Old code: Does not work after updating the SDKconst res = await Intercom.displayHelpCenterCollections([‘1234567’])// trueNew code: Also does not work with the latest SDKconst collections = await Intercom.fetchHelpCenterCollections();/**[ { "id": "1234567", "title": "FAQ" }]*/const collectionIds = collections.map(_ => _.id);// [ "1234567" ]const collectionContent = IntercomContent.helpCenterCollectionsWithIds(collectionIds);/**{ "type": "HELP_CENTER_COLLECTIONS", "ids": [ "1234567" ]}*/const res = await Intercom.presentContent(collectionContent);// trueThe problem is the same for both methods:displayHelpCenterCollections and presentContent return true, but no Intercom popup is opened.
When running unit tests in Xcode Cloud we often get a test failure because the tests failed to start. In those cases we get a spindump indicating that there is a deadlock caused by something Intercom does as a result of [UIBarAppearance init] being called. Anyone seen something similar? It seems to be related to a global initializer so just linking against Intercom will cause the problem. Just to be sure I’ve changed our code to not call any Intercom methods when running as part of XCTests but it appears to still be happening.
Android app crashes on launching the messenger with following logLibrary versions used:implementation 'io.intercom.android:intercom-sdk:15.9.1'implementation 'com.google.firebase:firebase-messaging:24.0.0'coreLibraryDesugaring 'com.android.tools:desugar_jdk_libs:2.0.4' Process: org.secondfloor, PID: 2558 java.lang.IncompatibleClassChangeError: Class 'android.content.res.XmlBlock$Parser' does not implement interface 'o8.a' in call to 'int o8.a.next()' (declaration of 's0.a' appears in base.apk) at s0.a.a(SourceFile:1) at H0.e.c(SourceFile:41) at H0.e.d(SourceFile:104)
I am using the React Native SDK and I would like to know the userId of the currently logged in user. Use-case: after updating to the latest SDK, loginUserWithUserAttributes throws an exception when the user is already logged in.But I have no way to know if the user is already logged into Intercom (after an app restart for example), and if logged it, if it is logged in using the correct user. I could store this in my app, but this makes the code much more complex. The best solution would be to have an Intercom method to return the currently logged user, if any.
I want to use latest version of Intercom Android, it's 15.11.0 but I'm facing this issue when I try to build an Android application through Unity 2022> A failure occurred while executing com.android.build.gradle.internal.tasks.R8Task$R8Runnable> Compilation failed to complete, origin: /Users/Jesus.Garcia@productmadness.com/.gradle/caches/transforms-3/4a75e8b5239795acd12bc894c94ac93e/transformed/jetified-intercom-sdk-base-15.11.0-runtime.jar:io/intercom/android/sdk/Injector$1.classI'm using gradle version 7.6 and AGP 7.4.2 but I see how you are using a most recent versionhttps://github.com/intercom/intercom-android/blob/master/sample/build.gradlehttps://github.com/intercom/intercom-android/blob/master/sample/gradle/wrapper/gradle-wrapper.propertiesSo I was wondering if I would have to upgrade also to the same versions.Regards,Jesús.
