Mobile SDKs

Engage users of your mobile app with an onboarding and support experience powered by Intercom

  • 191 Topics
  • 628 Replies

191 Topics

T
TomMoranNew Participant
asked in Mobile SDKs

React Native [HTTP 401] - Failed Identity Verification check

We have recently updated to 4.0.1Based on the docs, it appears we are using the correct flow of calls when we wither get a new sign-up or a log-inawait Intercom.setUserHash(userHash)await Intercom.loginUserWithUserAttributes({ email, userId })await Intercom.updateUser({...}) With the above, we get [HTTP 401] - Failed Identity Verification check, after the sign-up call. Interestingly it only occurs for a new user sign up. Login works fine. I have tried adding in await Intercom.loginUnidentifiedUser() before I call loginUserWithUserAttributes but oddly I then get the verification error on the updateUser call. Is this a bug or am I missing something from the docs?  

1
T
13 hours ago
L
lucasNew Participant
asked in Mobile SDKs

How to detect when user close Intercom

I’m writing a SwiftUI app. I need to detect when user close an Intercom window.Is that even possible?

6
C
23 hours ago
M
manfredxu99New Participant
asked in Mobile SDKs

React-Native problem building android - intercom-react-native:generateDebugRFile failed

Been getting this error since upgrading react-native, an ideas? * What went wrong:Execution failed for task ':intercom-react-native:generateDebugRFile'.> A failure occurred while executing com.android.build.gradle.internal.res.GenerateLibraryRFileTask$GenerateLibRFileRunnable   > /Users/manfredxu/Documents/project/node_modules/@intercom/intercom-react-native/android/build/intermediates/local_only_symbol_list/debug/R-def.txt Above I also see this:> Task :intercom-react-native:generateDebugRFile FAILEDExecution optimizations have been disabled for task ':intercom-react-native:generateDebugRFile' to ensure correctness due to the following reasons:  - Gradle detected a problem with the following location: '/Users/manfredxu/Documents/project/node_modules/@intercom/intercom-react-native/android/build/intermediates/local_only_symbol_list/debug/R-def.txt'. Reason: Task ':intercom-react-native:generateDebugRFile' uses this output of task ':intercom_intercom-react-native:parseDebugLocal

2
P
1 day ago
A
AlexNew Participant
asked in Mobile SDKs

Bug with screen rotation on iOS

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.

0
A
1 day ago
C
cody.rouecheNew Participant
asked in Mobile SDKs

React native crash on Android for latest version 5.0.0

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.

3
A
1 day ago
V
Valentin PertuisotNew Participant
asked in Mobile SDKs

Intercom iOS SDK 15.0.0: New Lottie dependency integration is botched and cause conflicts with host app Lottie integration

Hello,The latest Intercom iOS SDK version (15.0.0) has an integration of the Lottie Animation framework.  This dependency seems integrated statically.  Unfortunately if the host app also integrates Lottie, we now are flooded with following warnings from the System when running the app:  ...objc[69173]: Class _TtC6Lottie14AnimatedButton is implemented in both /Users/username/Library/Developer/CoreSimulator/Devices/BFEE2DFC-C11E-470B-B711-48A3266380E2/data/Containers/Bundle/Application/B04B0D15-DDBA-4889-BE53-1EB98904A186/HOSTAPP.app/Frameworks/Lottie.framework/Lottie (0x1055dc0b0) and /Users/username/Library/Developer/CoreSimulator/Devices/BFEE2DFC-C11E-470B-B711-48A3266380E2/data/Containers/Bundle/Application/B04B0D15-DDBA-4889-BE53-1EB98904A186/HOSTAPP.app/Frameworks/Intercom.framework/Intercom (0x104d407e0). One of the two will be used. Which one is undefined. ...(One of each for each Lottie class)It is too risky for us to go to production with the version 15.0.0 of the Intercom SDK

1
P
2 days ago
R
RenaudNew Participant
asked in Mobile SDKs

How can I get the currently logged in user?

I am using the React Native SDK and I would like to know the userId of the currently logged in user. Use-case: after updating to the latest SDK, loginUserWithUserAttributes throws an exception when the user is already logged in.But I have no way to know if the user is already logged into Intercom (after an app restart for example), and if logged it, if it is logged in using the correct user. I could store this in my app, but this makes the code much more complex. The best solution would be to have an Intercom method to return the currently logged user, if any.

4
J
2 days ago
A
Ahmet NovaNew Participant
asked in Mobile SDKs

Jetpack compuse crashes when adding intercom library

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.

1
Jacob Cox
4 days ago
E
eTaskun
asked in Mobile SDKs

The error about incorrect threads using in Xcode 14

Hi! When building the application in Xcode 14.0 b6, it shows the following error:Thread Performance Checker: Thread running at QOS_CLASS_USER_INITIATED waiting on a lower QoS thread running at QOS_CLASS_DEFAULT. Investigate ways to avoid priority inversions PID: 743, TID: 31796 Backtrace ================================================================= 3 Intercom 0x000000010440805c IntercomSDK_PINRemoteImageManagerSubclassOverridesSelector + 80944 4 Intercom 0x0000000104407e48 IntercomSDK_PINRemoteImageManagerSubclassOverridesSelector + 80412 5 libdispatch.dylib 0x0000000103c2a04c _dispatch_client_callout + 20 6 libdispatch.dylib 0x0000000103c2bbbc _dispatch_once_callout + 136 7 Intercom 0x0000000104407de0 IntercomSDK_PINRemoteImageManagerSubclassOverridesSelector + 80308 8 Intercom 0x0000000104403d5c IntercomSDK_PINRemoteImageManag

19
V
6 days ago
A
Alex T
asked in Mobile SDKs

[react-native] removing event listener throws "Maximum call stack size exceeded" error

Howdy!We're experiencing this issue after updating from 3.x SDK to 4.0.1 (https://github.com/intercom/intercom-react-native react-native version: 0.70.5  Code sample (which is basically the same that you have in docs):  useEffect(() => { const subscription = Intercom.addEventListener( IntercomEvents.IntercomUnreadCountDidChange, (response) => { setCount(response.count); } );   return () => { try { subscription.remove(); } catch (e) { console.log(e); } }; }, []); Calling subscription.remove on line 11 during effect cleanup triggers an exception. Line 13 prints:[RangeError: Maximum call stack size exceeded]Without try/catch block the call just fails silently due to this - https://github.com/facebook/react-native/issues/32673(which doesn't contribute to the original problem, just makes it go unnoticed).  Let me know what other details you might need. What can be done about it? Thanks.

7
N
9 days ago
J
Jason AndressNew Participant
asked in Mobile SDKs

iOS app crash when open an article directly and then try to send a message

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.

1
Racheal
9 days ago
K
Kostas TsalikisNew Participant
asked in Mobile SDKs

IllegalStateException The specified child already has a parent. You must call removeView() on the child's parent first

We are getting a great number of crashes on the Android version 14.1.0.This seems to happen to the conversation_list RecyclerView.You can find the stack trace bellow:java.lang.IllegalStateException: The specified child already has a parent. You must call removeView() on the child's parent first. at android.view.ViewGroup.addViewInner(ViewGroup.java:4471) at android.view.ViewGroup.addView(ViewGroup.java:4312) at android.view.ViewGroup.addView(ViewGroup.java:4252) at android.view.ViewGroup.addView(ViewGroup.java:4225) at androidx.compose.ui.viewinterop.AndroidViewHolder.setView$ui_release(AndroidViewHolder.android.kt:97) at androidx.compose.ui.viewinterop.ViewFactoryHolder.<init>(AndroidView.android.kt:332) at androidx.compose.ui.viewinterop.ViewFactoryHolder.<init>(AndroidView.android.kt:312) at androidx.compose.ui.viewinterop.AndroidView_androidKt$createAndroidViewNodeFactory$1.invoke(AndroidView.android.kt:247) at androidx.compose.ui.viewinterop.

2
K
14 days ago
U
User831
asked in Mobile SDKs

Long time to fetch intercom-ios repository with SPM

I noticed that adding intercom-ios takes an awfully long time to fetch repository. Upon further inspection it looks like the repo is ~1.5GB in size. Swift package manager for some reason chooses to fetch the entire directory and therefore it takes an inordinate amount of time to download (over 8minutes).

6
A
15 days ago
R
Roman KamyshnikovNew Participant
asked in Mobile SDKs

Incorrect Accompanist version in Intercom 15.0.0 (Android)

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?

2
Jacob Cox
17 days ago
G
gleb.pregerNew Participant
asked in Mobile SDKs

[SDK] [iOS] [Swift] [Crash] Intercom 13 and 14 crashes

Hello, Intercom team.I've encountered a serious problem when using Intercom ios sdk on the latest versions of ios 16.4 and higher, the application began to crash with an error when trying to open a conversation from the list of conversations in Intercom. (1)After that, I tried to update Intercom version to 14.1.0 but faced an even more serious problem, the application began to crash when opening the Intercom screen (after calling Intercom.presentMessenger()), including on older iOS versions. (2)Are you aware of these problems and can you suggest a solution?1)Xcode Version 14.3 (Swift)iPhone iOS versions 16.4 and 16.4.1 Intercom iOS SDK version 13.0.0 (installed with cocoapods)Error description:Thread 1: "Invalid batch updates detected: the number of sections and/or items returned by the data source before and/or after performing the batch updates are inconsistent with the updates.\nData source before updates = { 1 section with item counts: [1] }\nData source after updates = { 1 section

3
G
17 days ago
M
Mobile TeamNew Participant
posted in Mobile SDKs

The messages list from 'Intercom.client().present(IntercomSpace.Messages)' disappear

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

1
M
17 days ago
A
amrhanyNew Participant
asked in Mobile SDKs

Intercom crashes using Android SDK 14.1.0 on Jetpack Compose Version 1.4.0 when attempting to show the messenger

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)

22
M
17 days ago
A
Adnan
asked in Mobile SDKs

Deep links on Intercom push notifications for iOS do not send the user to the correct page.

Package: @intercom/intercom-react-native: ^3.0.3 When a push notification is sent via Intercom, with a deep link, the deep link opens correct on android (it opens to the correct in-app page when the app is in the background and the notification is clicked, as well as when the app is closed and the notification is clicked). However, on iOS, if the notification is clicked while the app is closed, the notification does not send the user to the correct page, it simply sends them to the home page (the page they would have landed on if they had simply opened the app by itself). If the notification is clicked while the app is backgrounded however, it does send them to the correct page. Anyone have any idea why this behaviour might be happening? 

2
P
23 days ago
U
User2410
asked in Mobile SDKs

Can't copy messages content, iOS

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? 😐

5
S
23 days ago
S
Shiva SrivastavaNew Participant
asked in Mobile SDKs

Seeing crash on Intercom SDK initialization on react native iOS app: "Unrecognized selector sent to instance" on re

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

2
Racheal
28 days ago
U
User1413
asked in Mobile SDKs

Can't display collections using intercom-react-native 4.0.1 mobile SDK

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.

4
K
29 days ago
B
bkolarov-phyreNew Participant
asked in Mobile SDKs

Android SDK 14.2.0 Crashes due to Jetpack Compose version inconsistency

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

1
Racheal
30 days ago
A
Artiom C
asked in Mobile SDKs

Hello, since last migration to 14.0.3 we have a problem with in-app messages in our Android app: app crashes when I try to open a message by clicking a in-app message notification in the bottom of the screen.

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

6
K
1 month ago
I
Illia HermanNew Participant
asked in Mobile SDKs

[ANDROID INTERCOM SDK] NoSuchMethodError related to androidx.profileinstaller.ProfileInstallerInitializer

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

1
Racheal
1 month ago
L
Lucas BastosNew Participant
asked in Mobile SDKs

Intercom Flutter SDK crash - 3.7.8

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

1
Racheal
1 month ago
Ask a question
Terms & ConditionsCookie settings