Mobile SDKs

When we send out a post message via push notification, select reply via emojis, the emojis don't appear in the message, any thoughts as too why?

After updating to new RN, everything was fine, but when i updated Intercom, the app has been starting close after open, and rn console was clean... But i found problem in xCode: 2022-12-27 22:31:47.367063-0600 MyApp[83087:2986586] [Intercom] ERROR - Tried to update user, but no user has been registered yet.   2022-12-27 22:31:47.367854-0600 MyApp[83087:2986586] [Intercom] ERROR - Tried to send metrics, but no user has been registered yet.   2022-12-27 22:31:47.368022-0600 MyApp[83087:2986586] -[NSNull code]: unrecognized selector sent to instance 0x1b9554020   2022-12-27 22:31:47.372064-0600 MyApp[83087:2986586] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[NSNull code]: unrecognized selector sent to instance 0x1b9554020'   **** First throw call stack:**   (   0 CoreFoundation 0x000000018040e7ec __exceptionPreprocess + 172   1 libobjc.A.dylib 0x0000000180051144 objc_exception_throw + 56   2 CoreFoundation

Here is the crash log, also noticing the error about email not present. I am not sending user email to intercom. ```INTERCOM ERROR - 'email' must be an NSString and can't be nil or empty [Intercom] ERROR - Tried to update user, but there was a problem with the SDK's initialisation.[Intercom] ERROR - Tried to send metrics, but there was a problem with the SDK's initialisation. -[NSNull code]: unrecognized selector sent to instance 0x111a1d5902023-05-01 16:56:50.683285-0700 ZiggyReactNative[42315:4564543] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[NSNull code]: unrecognized selector sent to instance 0x111a1d590'*** First throw call stack:(    0   CoreFoundation                      0x00000001117b778b __exceptionPreprocess + 242    1   libobjc.A.dylib                     0x000000010dc37b73 objc_exception_throw + 48    2   CoreFoundation                      0x00000001117c68c4 +[NSObject(NSObject) instanceMethodSignatureForSelector:] + 0    3   C

I’m using same dependencies with your sample and have the crash: java.lang.IncompatibleClassChangeError: Found interface androidx.compose.ui.graphics.drawscope.DrawScope, but class was expected (declaration of 'androidx.compose.ui.graphics.drawscope.DrawScope'proj lever build.gradle:plugins {    id 'com.android.application' version '8.1.1' apply false    id 'com.android.library' version '8.1.1' apply false    id 'org.jetbrains.kotlin.android' version '1.8.22' apply false}app level:composeOptions {        kotlinCompilerExtensionVersion "1.4.8"    }   def composeBom = platform('androidx.compose:compose-bom:2023.08.00')    implementation composeBom    androidTestImplementation composeBom    implementation 'androidx.compose.material:material'    implementation 'androidx.compose.ui:ui-tooling-preview'    debugImplementation 'androidx.compose.ui:ui-tooling'     implementation("io.intercom.android:intercom-sdk:15.2.2") 

Intercom appear animation looks like it’s presenting its View Controller on top of the current View Controller. But in reality it adds a new UIWindow with a snapshot of the current window and presents its View Controller on top of it.The issue is it doesn’t look for the top window, but uses something like UIApplication.shared.windows.first for the snapshot — this breaks animation with multiple app windows.In our case we have another “User is blocked please contact support” window on top (with higher windowLevel), which is not used for this snapshot :(Expected:Intercom should use the top-level key window for the snapshot.Intercom UIWindow’s windowLevel should be the same or higher than the current top window.

Hey folks 👋🏾After several recent updates, Xcode debugger stopped working for us, (lldb) po selfwarning: Swift error in scratch context: error: failed to load module 'Pipedrive'.Shared Swift state for Pipedrive has developed fatal errors and is being discarded.REPL definitions and persistent names/types will be lost. error: expression failed to parse:unknown errorDo you have any ideas what can be an issue? We are using cocoapods, but adding framework manually or via SPM doesn’t solve the issue. If we roll back to 15.1.1 everything works fine for us 🤔

This is the same bug as reported here : @Engineering  LLDB still doesn’t work with latest version (15.2.1) from https://github.com/intercom/intercom-ios-spThis topic was created to attract the attention of the Intercom developers since the previous question is marked as ‘Solved’.This is a critical bug as we can not use the latest version since developing without the debugger is almost impossible.

Hi there,   I am using react-native intercom library and after release of io.intercom.android:intercom-sdk-base:15.1.6, getting below errorManifest merger failed with multiple errors 

I’m installing the SDK via Swift Package Manager on Xcode 15 beta 8. I haven’t tested on Xcode 14. [...]/SourcePackages/artifacts/intercom-ios/Intercom/Intercom.xcframework:1:1: The signature of “Intercom.xcframework” cannot be verified. 

We are experiencing quite a lots of crashes after updating to Intercom 15.1.1 iOS SDK. All of them in iOS 16.XDo you have any identified issue with this version?Thanks a lot,ChristianFirebase stack traces… Crashed: nexus.reachability0  libobjc.A.dylib                0x2820 objc_msgSend + 321  Intercom                       0x5da28 IntercomSDK_MethodSwizzle + 189042  Intercom                       0x5daa4 IntercomSDK_MethodSwizzle + 190283  Intercom                       0x5ab00 IntercomSDK_MethodSwizzle + 68324  Network                        0x7f2e5c __nw_path_necp_update_evaluator_block_invoke + 4565  libdispatch.dylib              0x2320 _dispatch_call_block_and_release + 326  libdispatch.dylib              0x3eac _dispatch_client_callout + 207  libdispatch.dylib              0xb534 _dispatch_lane_serial_drain + 6688  libdispatch.dylib              0xc0a4 _dispatch_lane_invoke + 3849  libdispatch.dylib              0x16cdc _dispatch_workloop_worker_thread + 64810 libsystem_pthread.d

Hi,I’m following this guide to setup push notification and would like to find out more details on what does the Intercom.handlePushMessage() do in the react-native. https://developers.intercom.com/installing-intercom/react-native/push-notifications/ useEffect(() => { /** * Handle PushNotification */ AppState.addEventListener( 'change', (nextAppState) => nextAppState === 'active' && Intercom.handlePushMessage() ); return () => AppState.removeEventListener('change', () => true); } , [])  When tapping the push notification on iOS it opens the message but not on Android. What did I miss? Thanks.

When I create a new iOS Storyboard project and add the iOS SDK https://github.com/intercom/intercom-ios-sp via Swift Package Manager it fails to build with the following error:The signature of “Intercom.xcframework” cannot be verified.I received the same error when upgrading from 15.1.5 to 15.2.0 in an existing project also.Edit: Fetching other versions work fine.Edit 2: This is an issue in Xcode 15 betas only (specifically Beta 6 for me). Building with Xcode 14.3 works fine.

Hi, everyone!I am facing some weird issues after updating to latest intercom version, but it also happened after last update.Last year, in november, I upgraded to 'io.intercom.android:intercom-sdk:12.5.0' and after that, we got some massive crashing in production which is still present since I was trying to fix navigation until today when something else happened and I got suspicion it is related to intercom upgrade. So, here is out massive crash (6k events in last 90 days) submitted to google: https://issuetracker.google.com/issues/295991505Today, I have tried upgrading to 'io.intercom.android:intercom-sdk:15.2.0' and another equally weird thing happened, but now it was underwritten by red, related to `BottomSheetDialog` (?!). We had this part of code for like 4 years and it was working just fine until I have changed intercom version:binding.bottomSheetFFFFFF.getViewTreeObserver().addOnGlobalLayoutListener(new ViewTreeObserver.OnGlobalLayoutListener() { @Override public void onGl

We’ve seen this now occasionally where Intercom gets into a reconnection state and keeps allocating more and more memory. On production iOS this results in a termination of the OS but in our simulator it will accumulate until it cannot get no more (we’ve seen this go up in the several hundreds of gigabytes). Since the source is closed I cannot determine where this goes wrong but the memory inspection seems to point to these two functions:  As long as we keep the debugger on we will continuously see this being triggered, literally thousands of times within a minute. Is there anything that can be done here?

There was a ticket which was closed without viable solution, so I’m creating new one. Issue seems to be related to compose and accompanist versions.Required accompanist version: 0.32.0Required compose version: 1.5.0Target and compile sdk: 34 Error looks like this:java.lang.ClassCastException: androidx.compose.animation.AnimatedContentTransitionScopeImpl cannot be cast to androidx.compose.animation.AnimatedContentScope at io.intercom.android.sdk.m5.navigation.IntercomTransitionsKt$defaultEnterTransition$1.invoke(IntercomTransitions.kt:12) at androidx.navigation.compose.NavHostKt.createEnterTransition(NavHost.kt:346) at androidx.navigation.compose.NavHostKt.access$createEnterTransition(NavHost

For an Android app that targets API 33 and that includes FCM for push notifications, what is the advice on requesting the NOTIFICATION permission?My usecase: We have a tab in our app that when pressed, calls Intercom.client().present(). While the user is viewing the HelpCenter, the user could start a customer support chat. This is an ideal moment to request the NOTIFICATION permission. The user just sent a chat message and likely expects a notification when there is a reply.Is there a way for our app to know when the user sent a message so we can request the permission? Or does the intercom SDK request the notification permission on behalf of the app if needed?Versions:Intercom Android SDK v15.1.3 App targetSDK 33 Firebase BOM 30.0.0 (Firebase Messaging 23.0.4)

I setup and added Acute Feedback on my Intercom project as above image. But in Mobile app that using Android SDK 15.1.6, the Acute Feedback button is invisible.Could you please help me check this problem? How can I fix it? Thank you

Do push notification work on a iOS simulator? I have not been able to receive one despite going through at the steps required to setup push notification for  a React Native iOS app. 

We’re seeing a LOT of crashes with iOS SDK as of late and even after upgrading to the latest iOS SDK of 15.1.4Main three for sure are the following areas:IntercomColors.accessibleActionColor.getter IntercomSDK_IntercomNexusSocket resetConnectionTimeout outlined init with copy of (String, Any)Seeing about 100+ of these a week from our users.I can’t attach the logs as the question won’t post if I do. But I have a lot that I can supply.

I’ve followed the react native android push notification setup (https://developers.intercom.com/installing-intercom/docs/react-native-push-notifications) however I am receiving the following build error when building my app.  android:exported needs to be explicitly specified for element <service#<<my package name>>.MainNotificationService>. Apps targeting Android 12 and higher are required to specify an explicit value for `android:exported` when the corresponding component has an intent filter defined.Has anyone experienced this and what is the fix?

After upgrading from an older Intercom React Native version to the latest version (see details below) we’re no longer able to use the Intercom.displayMessenger() API to open the message composer with the logic mentioned in the docs here, which says:Then we’ll ensure the Messenger opens in the best place for each user.For example:If a user has one unread conversation, we open that conversation. If a user has no conversations, we open the composer. If a user has more than one unread conversation, we open the conversations list. If a user has no unread conversations, we open the last screen they were on when they closed it.The docs still mention the Intercom.displayMessenger() API, but according to comments in the code it’s deprecated and will be removed in the future. Currently calling the function seems to simply do the same as the Intercom.present() API. Our customer support team really likes the old Intercom.displayMessenger() UX and messenger display logic and would prefer to keep it

We use @capacitor/intercom plugin to use Intercom in Ionic app. According to logs device token is passed inside the plugin. And user is registered in Intercom. But without device token. So it is unable to send push notification to it

Hi Intercom:When using Intercom, some users have provided feedback that they are unable to send pictures on the Android system. when trying to send pictures, it prompts an error: unable to send.However, we can still receive text messages.we use @intercom/intercom-react-native, here is the dependencies:{ "react-native": "0.64.4", "@intercom/intercom-react-native": "3.0.0", "expo": "^44.0.4"}android/build.gradle information:buildscript { ext { buildToolsVersion = "30.0.3" minSdkVersion = 24 compileSdkVersion = 32 targetSdkVersion = 31 multiDexEnabled = true readerSdkVersion = "1.5.6" }}here is the information collected from users.Android Device: SM-A426UAndroid OS version: 13Could you please take a look, Thanks in advance!

Getting reports of crashes. It’s pretty explicit, the SDK tries to launch an app to handle `mailto` but none are found on the device.Intercom Android SDK version: `15.0.0`android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.intent.action.VIEW dat=mailto:xxxxxxx@xxxx.xxx } at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:1945) at android.app.Instrumentation.execStartActivity(Instrumentation.java:1620) at android.app.Activity.startActivityForResult(Activity.java:4541) at androidx.activity.ComponentActivity.startActivityForResult(ComponentActivity.java:754) at android.app.Activity.startActivityForResult(Activity.java:4499) at androidx.activity.ComponentActivity.startActivityForResult(ComponentActivity.java:735) at android.app.Activity.startActivity(Activity.java:4860) at android.app.Activity.startActivity(Activity.java:4828) at io.intercom.android.sdk.articles.ArticleWebViewClient.shouldOverrideU

Using React Native SDK, I see this error each time I open the app. Here is my codeIntercom.loginUserWithUserAttributes({ userId: `${authData.id}` }).then(() => { this.updateUser(authData, onUpdate)}) Even when I wrap this inside logout then callback, I get the same error.Intercom.logout().then(() => {  Intercom.loginUserWithUserAttributes({ userId: `${authData.id}` }).then(() => {    this.updateUser(authData, onUpdate)  })})Note: This happens only on Android.