Mobile SDKs

Hi,We upgraded the Intercom SDK on react-native to 5.1.1, however we found a very strange crash. On a screen we use https://github.com/react-native-picker/picker and when the picker is opened on Android the app will crash. We found that the Intercom upgrade from 4.0.1 to 5.1.1 was the culprit. I presume it’s something to do with the underlying Android SDK which was updated. Below is the stack trace from Sentry java.lang.ClassNotFoundException: androidx.appcompat.widget.e0$a at androidx.appcompat.widget.e0.setSelector(DropDownListView.java:1) at android.widget.AbsListView.<init>(AbsListView.java:899) at android.widget.ListView.<init>(ListView.java:231) at android.widget.ListView.<init>(ListView.java:227) at androidx.appcompat.widget.e0.<init>(DropDownListView.java:1) at androidx.appcompat.widget.i0.s at androidx.appcompat.widget.i0.q(ListPopupWindow.java:4) at androidx.appcompat.widget.i0.a(ListPopupWindow.java:1) at androidx.appcompat.

In the Android project I'm working on, we're noticing that user data is getting mixed up. Why could this be happening? Every time a user logs into the application, we perform a login to Intercom using the following code: operator fun invoke(user: UserModel, intercomHash: String) {    val userAttributes = createUserAttributes(user)    val registration = Registration.create().withUserId(user.id)    Intercom.client().setUserHash(intercomHash)    Intercom.client().loginIdentifiedUser(registration, object : IntercomStatusCallback {        override fun onFailure(intercomError: IntercomError) {            /*                The Intercom login will fail with error code 3002 if the user is already logged in.             */        }        override fun onSuccess() {            Intercom.client().updateUser(userAttributes)        }    })}private fun createUserAttributes(user: UserModel) = UserAttributes.Builder()    .withEmail(user.person.emailAddress)    .withPhone(user.person.phoneNumber)    .wit

Mobile SDKs: 1. We have embedded Intercom into our developed app (let’s called it Venus in this case), and when we reply our users through Intercom, how do users see mobile push/notifications on their phone? Can they see on lock screen? And what will be the text like, is it “New message from Venus” or “New message from Intercom?”Like:  2. Our users would like to send files via Intercom within Venus, can we create maybe like a short link in Workflow’s message, and when someone clicks it, it will direct the user from Venus to his/her email app and fill in email template automatically? Workflow:1.  We have created a workflow which is when customer clicks on messenger, workflow will be triggered. However, we want this workflow to be launched from beginning again every time when the same user clicks on messenger. How can I set it up?  

I have a problem with `io.intercom.android:intercom-sdk:15.1.0`. When a new in-app message appears, it's hidden "under" the navigation bar. Switching to another tab fixes the position on the screen (I think it calculates window insets). I've tried setting bottom padding, but the behavior is still similar (2nd gif). The content displays with the given padding, and after changing the tab, it moves up by the height of the system navigation bar.No bottom padding set:  After setting bottom padding:  

If we connect Intercom in our developed app, when we send messages to our customers, how will they receive notifications? Like will they see “you’ve got a new message from [app name]? 

When calling the IntercomModule.loginUserWithUserAttributes without an email it crashes because the IntercomHelpers.getValueAsStringForKey(params, “email”); line here is being called even if there is no email and there is no null check in that method: https://github.com/intercom/intercom-react-native/blob/9623a0c4822e91949d27357ef21df845cc91f38f/android/src/main/java/com/intercom/reactnative/IntercomModule.java#L139 . Same this would happen if no userId was passed in. Both values are checked to see if they are there, but even if they are not it still attempts to get them rom the params. It can be bypassed by passing in an empty string, but that is not ideal.

When launch button is visible screen rotation doesn’t work correct, content is rotating with wrong layout and status bar doesn’t rotate at all.

I’m having a crash after adding intercom SDK to my jetpack compose project.I using intercom-sdk-base:15.0.0At launch I’m having this crash (before I init intercom):E/AndroidRuntime: FATAL EXCEPTION: main    Process: com.solidict.gezerkasa.dev, PID: 31609    java.lang.NullPointerException: Parameter specified as non-null is null: method androidx.compose.material.ModalBottomSheetKt.rememberModalBottomSheetState, parameter confirmStateChange        at androidx.compose.material.ModalBottomSheetKt.rememberModalBottomSheetState(Unknown Source:7)        at com.google.accompanist.navigation.material.BottomSheetNavigatorKt.rememberBottomSheetNavigator(BottomSheetNavigator.kt:107) I tried to change material versions as I saw in the other tickets but again I had the same crash.I tried to use different intercom versions all the same.any help would be greatly appreciated.

I’m using the latest cordova-plugin-intercom version.Steps to reproduce.Open an article directly from my code using the displayArticle function.Tap the frown face under “Did this answer your question?”Tap the Send us a Message buttonApp crashes and closes.Let me know if you need the exact Xcode crash info.

Hi!I was using gradle :dependencies to find out the Compose version Intercom 1.5.0 is using and noticed that it depends on several Accompanist libraries v0.28.0, for example:com.google.accompanist:accompanist-flowlayout:0.28.0com.google.accompanist:accompanist-systemuicontroller:0.28.0com.google.accompanist:accompanist-pager:0.28.0According to the Accompanist docs, for Compose 1.4.x Accompanist v0.30.1 should be used as different versions might cause unexpected behaviour or crashes. An example of this was raised in this issue where the crash was caused by differences between Compose 1.3.x and 1.4.xAs a sidenote, could you please include the compose version Intercom is using in the release notes or docs?

Intercom SDK: 15.0.0Android OS: 13User: https://app.intercom.com/a/apps/hqausqan/users/5a294df84dbb32cda1153452/all-conversationsThe list of messages from Intercom.client().present(IntercomSpace.Messages)  disappears and it’s replaced by the “No messages” screen.Video:https://drive.google.com/file/d/1GgwvKj6xMxjdyr49A-XqgsX3zAcpvcw3/view?usp=sharing

Our Android app is integrated with Intercom and everythign works well on Compose Version 1.3.3, but when updated to 1.4.0 intercom keeps crashing when we try to show the messenger.This is the stacktracejava.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/~~z4UTrvmcfPy_7KD14FmyyA==/com.pleny.tst-yaxEdFlvh_1wkGx-0_Cr-A==/base.apk) at io.intercom.android.sdk.m5.IntercomStickyBottomSheetKt.getEquivalentCorner(IntercomStickyBottomSheet.kt:175) at io.intercom.android.sdk.m5.IntercomRootActivity$onCreate$1$1.invoke(IntercomRootActivity.kt:102)

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