Mobile SDKs

Hey! Our clients can't copy text or links from the messenger. We use iOS SDK. Android users are fine. Reported to support about a year ago. Any ideas, may be we missing someth? 😐

I'm wondering if this may be a bug, but I can't seem to find anywhere else to report bugs. When I use intercom-react-native 4.0.1 and running it on iOS Intercom.present() works and displays help and displaying articles like this also works: await Intercom.presentContent( IntercomContent.articleWithArticleId('5747692') );However, when I try to display a collection using the following code:await Intercom.presentContent( IntercomContent.helpCenterCollectionsWithIds(['3860234']) );The collection fails to display and we get the following error in the XCode output [Intercom] INTERCOM ERROR - 'Each object in the array' must be an NSString and can't be nil or empty We've rolled back to using v3.0.5 of intercom-react-native and the collections display is working as expected with that version.

Android Intercom SDK causes a crash in our app due to differences of the Jetpack Compose version. This issue has already been posted here, but has been marked as solved without actually being such. Since the issue is still present in version 14.2.0, I’m creating a new post, which hopefully will get more attention. Intercom Android SDK v14.2.0 still depends on Jetpack Compose 1.3.3. Our project is using Compose 1.4.4, which is the cause of the problem. Are there any plans to upgrade this anytime soon?Stacktrace:java.lang.NoSuchMethodError: No virtual method getOffset()Landroidx/compose/runtime/State; in class Landroidx/compose/material/ModalBottomSheetState; or its super classes (declaration of 'androidx.compose.material.ModalBottomSheetState' appears in /data/app/~~j2gBFh7VrrFZJGyrBBoH8A==/com.phyreapp-HUPotQQpnk4p2DFTgV863w==/base.apk) at io.intercom.android.sdk.m5.IntercomStickyBottomS

I searched the whole documentation and android repository with the sample app, but can not find any information on that. On the screenshot You can see the intercom in-app message notification:When I click on it I receive the NPE Error with following stacktrace:FATAL EXCEPTION: main Process: de.lexoffice.android.debug, PID: 19577 java.lang.NullPointerException: Attempt to read from field 'java.lang.String android.content.Intent.mAction' on a null object reference in method 'void android.content.Intent.<init>(android.content.Intent, int)' at android.content.Intent.<init>(Intent.java:7915) at android.content.Intent.<init>(Intent.java:7911) at android.app.TaskStackBuilder.getIntents(TaskStackBuilder.java:306) at android.app.TaskStackBuilder.startActivities(TaskStackBuilder.java:222) at android.app.TaskStackBuilder.startActivities(TaskStackBuilder.java:233) at android.app.TaskStackBuilder.startActivities(TaskStackBuilder.java:209) at io.intercom.android.sdk

I've encountered an issue related to the Intercom SDK  that appears to be caused by the androidx.profileinstaller.ProfileInstallerInitializer class (only intercom sdk uses this dependency in our project). I get this error using latest io.intercom.android:intercom-sdk:14.2.0. Probably, it may be due to an outdated version of the androidx.profileinstaller:profileinstaller:1.2.0 library included in the Intercom SDK.The issue has caused 82 crash events, raising serious concerns about my project’s stability and the quality of the user experience.Here's the error I encountered:Fatal Exception: java.lang.NoSuchMethodError: No direct method <init>(Landroid/content/Context;)V in class Landroidx/profileinstaller/ProfileInstallerInitializer$$ExternalSyntheticLambda2; or its super classes (declaration of 'androidx.profileinstaller.ProfileInstallerInitializer$$ExternalSyntheticLambda2' appears in base.apk:classes3.dex)       at androidx.profileinstaller.ProfileInstallerInitializer.writeInBack

Hello, We noticed that for some customers registered the app was crashing due to intercom sdk and we had to remove it completely and redirect our tickets to be handled in Whatsapp. Are you guys aware of this problem? It is curious that has happened only with certain registered customers. We suspect that the sdk is retrieving some invalid information for these customers Thanks

Using React Native SDK, we’re experiencing a bit weird issue. When opening messenger, conversation topics are not shown. The strange thing is that this does not happen for all users. Some users can see conversation topics while others cannot. Could you help us guessing what might be the problem?

[Intercom] Error unarchiving Object: Error Domain=NSCocoaErrorDomain Code=4864 "*** -[NSKeyedUnarchiver _initForReadingFromData:error:throwLegacyExceptions:]: data is NULL" UserInfo={NSDebugDescription=*** -[NSKeyedUnarchiver _initForReadingFromData:error:throwLegacyExceptions:]: data is NULL}

Chat opens in another separate activity/task/app, i.e. creates new application instance. That is, if you open recent applications on an android device, there are two apps (our and intercom chat). We’d like intercom chat to open inside the app without creating a second instance. Could you fix this please?

Can we use two different android/iOS apps with different bundle ids/application id in a single workspace? will this support the feature of push notification?

We have issue on Android. Intercom version = "14.0.5".Do you know about this bug? Is it fixed on new versions? Fatal Exception: java.lang.IllegalArgumentException: width and height must be > 0 at android.graphics.Bitmap.createBitmap(Bitmap.java:1257) at androidx.compose.ui.graphics.Api26Bitmap$$InternalSyntheticApiModelOutline$1$0d1481f8454719621a2b84122f73df767334f4ade3647b3247b2f70e57c1b7e1$0.m(Api26Bitmap.java) at androidx.compose.ui.graphics.Api26Bitmap.createBitmap-x__-hDU$ui_graphics_release(AndroidImageBitmap.android.kt:198) at androidx.compose.ui.graphics.AndroidImageBitmap_androidKt.ActualImageBitmap-x__-hDU(AndroidImageBitmap.android.kt:44) at androidx.compose.ui.graphics.ImageBitmapKt.ImageBitmap-x__-hDU(ImageBitmap.kt:255) at androidx.compose.ui.graphics.ImageBitmapKt.ImageBitmap-x__-hDU$default(ImageBitmap.kt:249) at androidx.compose.foundation.BorderKt.drawGenericBorder(Border.kt:474) at androidx.compose.foundation.Border

We are getting this crash on Android devices constantly. Attempt to invoke virtual method 'java.lang.String io.intercom.android.sdk.models.CustomizationColorsModel.getBackgroundColor()' on a null object reference This is the only piece of the stack trace that we get.

Android SDK version: 10.4.2iOS SDK version: 10.3.4Few days ago since I posted this, the SDK worked fine, and then about two days ago, it suddenly stopped working for unknown reason. We didn't even change the implementation code. The Messenger screen always stuck with "Something wrong happened. Please try it again.". Pressing "Reload" didn't help as well. When initializing the app, there was no error. After registering the user through an User ID and setting the FCM Token, also showed no errors. Once we got to the part to update the User or turning on the Messenger screen, then we received this error. This error is the example during turning on the Messenger. Updating the user also showed similar error message.ERROR - Tried to get conversations for display in the conversations list but there was a network error (401) - Request failed: unauthorized (401) There's no way the API key used was wrong. If it worked previously without changes, why did it stop wor

Ideally looking for a couple online public apps that do this well and any good tips to ensure we're collecting good data at launch but can also handle unknown volume.

Hi team,Can I know do we support multi instances?Or How can we re-initial Intercom when the app opens?My case is the app has 2 languages and would like to connect to the specific workspace once logged in, I have used unregisterForLateInitialisation to re-initial for another country when log-out but it doesn't work.Note: iOS is working when re-call initialize for each workspace. Only Android doesn't work.

Hello!  We have an app written in Flutter, where we use the `intercom_flutter` package version 7.6.1. This package uses your Android SDK version 14.0.3.  With our latest release we received an app crash on our Play Console. The error message was: io.intercom.android.sdk.m5.notification.InAppNotificationCardKt.addTicketHeaderToComposeWith the following stack trace:Exception java.lang.IllegalStateException: at androidx.compose.ui.platform.WindowRecomposer_androidKt.createLifecycleAwareWindowRecomposer (WindowRecomposer_androidKt.java:349) at androidx.compose.ui.platform.WindowRecomposer_androidKt.createLifecycleAwareWindowRecomposer$default (WindowRecomposer_androidKt.java:324) at androidx.compose.ui.platform.WindowRecomposerFactory$Companion$LifecycleAware$1.createRecomposer (WindowRecomposerFactory.java:168) at androidx.compose.ui.platform.WindowRecomposerPolicy.createAndInstallWindowRecomposer$ui_release (WindowRecomposerPolicy.java:224) at androidx.compose.ui.platform.Windo

Fatal Exception: java.lang.IllegalStateException: ViewTreeLifecycleOwner not found from android.widget.FrameLayout{9f9fb51 V.E...... ......ID 0,0-1080,2131 #7f0a04a1 app:id/intercom_overlay_root} at androidx.compose.ui.platform.WindowRecomposer_androidKt.createLifecycleAwareWindowRecomposer(WindowRecomposer.android.kt:349) at androidx.compose.ui.platform.WindowRecomposer_androidKt.createLifecycleAwareWindowRecomposer$default(WindowRecomposer.android.kt:324) at androidx.compose.ui.platform.WindowRecomposerFactory$Companion$LifecycleAware$1.createRecomposer(WindowRecomposer.android.kt:168) at androidx.compose.ui.platform.WindowRecomposerPolicy.createAndInstallWindowRecomposer$ui_release(WindowRecomposer.android.kt:224) at androidx.compose.ui.platform.WindowRecomposer_androidKt.getWindowRecomposer(WindowRecomposer.android.kt:299) at androidx.compose.ui.platform.AbstractComposeView.resolveParentCompositionContext(ComposeView.android.kt:242) at andr

I am experiencing an error when I generate my ipa and open my app on my physical device.In ios case the app closes automatically on android it works fine. I have generated my ipa before intercom and it works perfectly until I integrate the sdk, then ios crashes I have followed the documentation to the letter and also tried making the manual link.Also I disabled  Bitcode because when I was getting the archive the error message recommended to put in NO  Maybe I need an extra step in the ios configuration? Packages:I included some libraries that I am using in my project and they are using native code"@intercom/intercom-react-native" : 4.0.1"react": "18.1.0""react-native": "0.70.5""@react-native-community/geolocation": "^3.0.4""react-native-permissions": "^3.6.1""react-native-reanimated": "^2.12.0""@react-navigation/native": "^6.0.13""react-native-in-app-re

We are unable to view unread messages on the intercom mobile SDK, and the loading spinner just keeps spinning. We have implemented the Intercom mobile SDK, version 7.6.1, but we are still unable to view the unread messages. This works perfectly fine in our Test workspace, and the issue is limited to the main/production workspace. Once I go in and manually read messages on the web interface, they then appear on the mobile SDK.

After installing the mobile SDK to the IOS app, whenever we post a mobile carousel to the app, the external link on the C2A button doesn't work, it only closes the pop-up. Any ideas what can cause this?

We just upgraded from v1.0.1 to v4.0.1 and are getting some errors thrown in production.So far we've only rolled out our iOS release, so that's all the errors we're getting atm.await Intercom.loginUserWithUserAttributes(userProfile)Is throwingError: ERROR - [HTTP 429] - Request failed: client error (429)This is happening for a small, but non trivial, amount of our users.I can't find anything useful in the docs about this error or what might be contributing to it. So far it's limited to iOS v16+, but that might just be coincidence due to the larger % of users on the latest iOS version.

We've added userId to login attributes and also tested this in the examples app always error 409.

When building the last 4.0.0 release with "react-native": 0.70.5 we're getting this conflict about androidx.appcompat:appcompat:1.1.0. ` Could not determine the dependencies of task ':app:mergeReleaseNativeLibs'. Could not resolve all task dependencies for configuration ':app:releaseRuntimeClasspath'. Could not resolve androidx.appcompat:appcompat:1.1.0. Required by: project :app project :app > project :react-native-screens project :app > project :react-native-screens > com.google.android.material:material:1.6.1 > Cannot find a version of 'androidx.appcompat:appcompat' that satisfies the version constraints: Dependency path 'app:app:unspecified' --> 'androidx.appcompat:appcompat:1.1.0' Dependency path 'app:app:unspecified' --> 'com.facebook.react:react-native:0.70.5' (releaseVariantDefaultRuntimePublication) --> 'androidx.appcompat:appcompat:1.4.1' Dependency path 'app:app:unspecified

We are trying to upgrade from Intercom 8.x to Intercom 14.0.3 and getting the following error on calling Intercom.client().present(IntercomSpace.Home);2022-12-11 17:54:11.415 13331-13331/com.x.y E/AndroidRuntime: FATAL EXCEPTION: main Process: com.x.y, PID: 13331 java.lang.IncompatibleClassChangeError: Found interface androidx.compose.ui.graphics.drawscope.DrawScope, but class was expected (declaration of 'androidx.compose.ui.graphics.drawscope.DrawScope' appears in /data/app/~~055VLuai5T4CYOE8PxFBWA==/com.x.y-HBBsMBMGuNiKkrQsODOALw==/base.apk) at androidx.compose.ui.graphics.drawscope.DrawScope.drawRect-n-J9OG0$default(DrawScope.kt:410) at io.intercom.android.sdk.m5.IntercomStickyBottomSheetKt$Scrim$1$1.invoke(IntercomStickyBottomSheet.kt:132) at io.intercom.android.sdk.m5.IntercomStickyBottomSheetKt$Scrim$1$1.invoke(IntercomStickyBottomSheet.kt:131) at androidx.compose.ui.draw.DrawBackgroundModifier.draw(DrawModifier.kt:104) at

Hello Team,We have used the post feature to send feature updates to iOS customers. (Enabled push notification) Only a few of them have received notifications and most of them don't. (especially in terminated state/killed state) But after opening the app, They could see the post. Post referred - https://app.intercom.com/a/apps/fjguqlbd/outbound/post iOS intercom SDK used 12.1.1. Tested in iPhone with OS Version 16.0.3