Mobile SDKs

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   

We got a crash at the method `cellForRowAt` of the class `HelpCenterSearchViewController`with Intercom 10.4.0.I did not find any explicit fix relative to this crash in the latest versions released.Can you help me on that ?Thanks!

Hello! We are trying to set up push notifications for the iOS mobile app that we are building. We have performed all the steps described here:https://developers.intercom.com/installing-intercom/docs/ios-push-notifications/p> Our app requests user's permission to send push notifications, and we are able to see the correct "push notifications enabled" setting in Apple Settings, so we know that requesting permissions works.At the same time when I look at user profiles in Intercom, all users have "Enabled push messaging" property set to "Unknown", and so we are not able to send push notifications from Intercom. Has anyone experienced this issue before? Anything we are missing in the configuration? Thanks in advance!

I managed to have push notifications working in our Expo EAS app with `@intercom/intercom-react-native` library and `config-plugin-react-native-intercom`. They are working fine, but:when I answer a customer form Intercom chat dashboard the push notification subject is my Intercom user name and the body is only a couple of words that I wrote the message to customer. Can I customise the push notification to something like: subject - "Company Name:, body - "Hey, Company Name just sent you a message, please check it out" ?

This makes no sense, a week ago I set one of our mobile carousels to trigger every minute to help debug and test in our development environment, today when I try to do it an error says "a message can only be sent every hour".  Something is broken there.

I am getting above error while 'Rebuild' a project. AGPBI: {"kind":"error","text":"Can't determine type for tag '<macro name=\"m3_comp_bottom_app_bar_container_color\">?attr/colorSurface</macro>'","sources":[{"file":"/Users/brittognanaraj/.gradle/caches/transforms-3/bc32538fb0414547d4337593d1e2c55f/transfo

I'm using the React Native Intercom SDK (versions below) and am getting the following build error: /DEV AppCenter-iphoneos/XCFrameworkIntermediates/Intercom/Intercom.framework/Intercom' does not contain bitcode. You must rebuild it with bitcode enabled (Xcode setting ENABLE_BITCODE), obtain an updated library from the vendor, or disable bitcode for this target. @intercom/intercom-react-native: 4.0.0react-native: 0.70.6Node: 14Xcode: 13 What can I do to solve this?

In our first app launch, we need to ask for permission to send notifications. Even when granted, Intercom push notifications do not work for the app until the user relaunches the app. Using Intercom swift package 12.1.0Using automatic swizzle for enabling intercom push notification handlingHave enabled didRegisterForRemoteNotificationsWithDeviceToken in Application Delegate. Thanks for your help.

Hello.We want to report an issue with the ‘@Intercom/intercom-react-native’ for old ios devices (iPhone 5s, iPhone 6). The transition effect is incomplete and it does influence the appearance of the header component in a chat.As a pod dependence, we do use the ‘“Intercom”, ‘~> 10.3.5’' version.

I just upgrade to SDK v14. Now, every time a user logs in, I see some debug logging from the Intercom SDK. Looks like some leftover print() calls that were used to test the new color customization features. I verified with the example app that it is indeed the Intercom SDK and not any of my code.#1D7D1D #C1F1C1 #FFFFFF #FFFFFF #000000 #1D7D1D #FFFFFF #1D7D1D #FFFFFF #FFFFFF(Also, thread checker is still complaining about priority inversion in PINRemoteImageManager)

i have been trying to solve this problem for a while but can't seem to find the cause. though here and some things i found out the might helpif someone was testing the current versions of the app without deleting the older version before recompiling it keept working.despite working on past versions of the app going back now will lead the the same results. 2b. it's possible the issue was also pressent of older versions of the app without anyone noticing but i have gone back to all versions i have access tothis is only about push notifcations them selfs the rest of the funtions remain funtionalpush notifications send directly from fire base still work like expected.

Hello, Many SDKs allow a URLSession to be injected (and thus configured) into an SDK. Auth0 is such an example. A recent security audit has indicated Intercom is persisting chat information to disk. We'd like to be able to use an ephemeral URLSessionConfiguration on iOS to prevent Intercom from persisting anything to disk. As it stands we have to assume Intercom uses URLCache.shared and clear that manually, which is a non-ideal workaround. Can you please allow for URLSession to be specified by the app implementing the SDK?

I am getting this message in settings: "Intercom isn’t installed for your Android app yet" . In the iOS portion, I have the correct message: "Intercom has been installed in your iOS app". I have followed the instructions on adding the latest React Native wrapper and the `displayArticle` method works as expected. On Android, this method will display a white screen with a message similar to "Something went wrong, try again". Is there a solution to this issue?

Our app uses a webview on iOS.We enabled app-bound domains (https://webkit.org/blog/10882/app-bound-domains/). Since then, we can no longer open any article on Intercom, as it uses WKWebView. Even when we include the domain intercom.help in our allow-list, it still does not work. Our belief is that you do not correctly set "limitsNavigationsToAppBoundDomains" on your WKWebviewConfiguration. We tried to investigate your source code, but we noticed you only provide a binary (not the actual source code).  This is how it looks like. Upon inspection with Safari DevTools, you can verify that intercom.help has loaded (you can read the HTML), but it is not presented. We suppose there is a communication between the native code and the webview that got broken. This is critical for our application. When should I be expecting a reply from your technical team?