Mobile SDKs

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?

Trying to setup Intercom with react-native, got it working well on Android, but stuck on iOS attempting to register users (breaks for both unidentified & identified register methods) Tested a few different versions, all working as expected on Android, but still failing with same exception for iOSNPM Package: @intercom/intercom-react-nativeTested v3.0.3 - v3.0.5iOS Package: Intercom (intercom/intercom-ios)Tested v12.0.0 - v12.4.3React Native (npm): react-nativeTested: v0.66.x + v0.68.x + v0.70.x (latest) Strange part is that it actually worked the very first time tested on iOS simulator using registerUnidentifiedUser() method, then started seeing this exception and now cannot get any version of Intercom.register** to work without throwing this same error (for any/all iOS developers & devices). We have implemented the Intercom.logout() method, and have used it trying to force reset/register again, but no luck. Please help! Here is the full exception & trace for context:Except

Hi, Intercom iOS SDK has a layout issue with the navigation bar on iPad on several screens in Intercom Messenger. Steps to reproduce:Present Intercom Messenger on the iPad.Ensure that you have several conversations. Tap “See all your conversations" and open the list of conversations.Observe the corrupted navigation bar in the Conversation list screen. See the attached screenshot 2.Open any conversation and make the keyboard visible.Observe the corrupted navigation bar. See the attached screenshot 3. Additional info: reproduces only on the iPad platformreproduces on the previous and the latest Intercom SDK versionsreproduces on the previous and the latest iOS versions

Is it possible to have the SDK respect dark mode for the messenger chats?

Hi, i am sending a test push notification to my mobile phone. I did all the steps and the notification appears as sent at intercom ui but i never arrived to my mobile phone (android).My app is build with react native and the device token is well capture

the style of launcher works fine in website but it looks different in the mobile app. Is their some specific reason behind this? Can we make both look same?

I recently changed my react native library to the official one. I have no problem en iOS but cant make it work for Android. The error comes from from node_module intercom package, I think it might have something to do with hermes-engine (used for live reloading)This is the error on the console:Anyone have encountered this issue?

I'm developing iOS app using intercom iOS SDK. Currently I'm facing problem that's intercom doesn't update for new message coming. Only update when I open conversation from launcher or goes into background mode, then comes again in foreground mode your help is required?

It has been reported that on devices with smaller screens the configured layout does not work in the same way. Could anybody help me? 

Hi, We randomly get the following error when trying to build an android release build. After building a few times it seems to fix itself but suddenly appears again after some time. This is pretty annoying since it costs unnecessary credits on CI servers. It already happened in react-native-intercom 2.1.0 but also happens now on latest 3.0.5. FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':@intercom_intercom-react-native:generateReleaseRFile'. > A failure occurred while executing com.android.build.gradle.internal.res.GenerateLibraryRFileTask$GenerateLibRFileRunnable > /Users/vagrant/git/node_modules/@intercom/intercom-react-native/android/build/intermediates/local_only_symbol_list/release/R-def.txt 

When we sent a carousel from the website, we noticed that, if the iOS app is in foreground, the carousel is received (it is ticked as "sent" on Intercom's website), but it's never displayed to the user. But, if the app is killed, or in background, while the carousel is being set live, then, upon opening the app and logging the user to Intercom, the carousel is displayed correctly. We tried both with "IntercomAutoIntegratePushNotifications" set to YES, and setting it to NO, adding the following code to the AppDelegate, both to the function "didReceive", and the function "willPresent": let userInfo = response.notification.request.content.userInfo if (Intercom.isIntercomPushNotification(userInfo)) { Intercom.handlePushNotification(userInfo) } 

Hi , We have integrated android sdk for intercom in our Flutter app having version 12.3.0. There are few exceptions/ANR that is reported on firebase which I would like to highlight. Can you guy please look into it and let us know the resolution for the same. The screenshots for this are also attached with this. Do let me know if there is anything else required to fix this.   Here are the exceptions and its stack trace:- 1. IntercomPushManager.java line 51 main (runnable): tid=1 systid=24170 #00 pc 0x458f1c libart.so #01 pc 0x6f98a8 libart.so #02 pc 0x701380 libart.so #03 pc 0x3b38c0 libart.so #04 pc 0x34a314 libart.so #05 pc 0x28b45c libart.so #06 pc 0x28a630 libart.so #07 pc 0x28a630 libart.so #08 pc 0x364b88 libart.so #09 pc 0x677bb0 libart.so     at java.lang.Class.classForName(Class.java)    at java.lang.Class.forName(Class.java:454)    at java.lang.Class.forName(Class.java:379)    at io.intercom.android.sdk.IntercomPushManager.getFcmServiceClass(IntercomPushManager.java:51)    at

Why not just throw an error and let the developer handle it?