Mobile SDKs

We are currently experiencing crashes when opening old messages on Intercom - iOS SDK.  Here is the error message:  *** Assertion failure in -[IntercomSDKPrivate.TouchTransparentCollectionView _Bug_Detected_In_Client_Of_UICollectionView_Invalid_Batch_Updates:], UICollectionView.m:10,929*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Invalid batch updates detected: the number of sections and/or items returned by the data source before and after performing the batch updates are inconsistent with the updates.Data source before updates = { 1 section with item counts: [2] }Data source after updates = { 1 section with item counts: [2] }Updates = [Insert item (0 - 0)]Collection view: <IntercomSDKPrivate.TouchTransparentCollectionView: 0x7fe6630e8c00; baseClass = UICollectionView; frame = (-393 0; 393 783); transform = [1, 0, 0, 1, -393, 0]; clipsToBounds = YES; alpha = 0; gestureRecognizers = <NSArray: 0x600000590e70>; backgroundColor = UIEx

 Crashlitics has reported a `FileNotFoundException` on Android, the resource can not be downloaded within the browser either.Androdi SDK version: 15.7.0Fatal Exception: java.io.FileNotFoundException: https://downloads.intercomcdn.com/i/o/1052073407/eabcb799a0515a981f18b011/IMG-20240515-WA0067.jpg       at com.android.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:255)       at com.android.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:211)       at com.android.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:30)       at com.google.firebase.perf.network.InstrURLConnectionBase.e(InstrURLConnectionBase.java:24)       at com.google.firebase.perf.network.InstrHttpsURLConnection.getInputStream(InstrHttpsURLConnection.java:3)       at io.intercom.android.sdk.ui.preview.viewmodel.PreviewViewModel.prepareBitmap(PreviewViewModel.kt:17)       at io.intercom.android.sdk.ui.

[Error: ERROR - [HTTP 404] - Resource Not Found]. when I try to use one of the login function.we are using or trying to present the Intercom Messenger. const loginWithIntercom = async () => { const status1 = await Intercom.setUserHash(user.id.toString()); console.log('status hash : ', status1) // true const status = await Intercom.loginUserWithUserAttributes({ userId: user.id.toString() }); // throw 404 not found error console.log('login success : ', status); };I’ve checked in the native code that everything is configured as it should be after running npx expo prebuild.how to deal with this issue ?We are using :expo SDK: 51react-native: 0.74.1intercom/intercom-react-native: 7.1.1how to deal with this issue

Release Date: 16-05-2024 🐛 Bug Fixes * Fixes a layout issue with the Powered by Intercom link. Note This release contains some beta features.

Hello our monitoring is reporting some crash errors on lastest RN package version 6.0.1:NSInternalInconsistencyException: Attempted to reload item identifier that does not exist in the snapshot: IntercomSDKPrivate.ConversationCollectionViewCellType.message(<ICMConversationPart: 0x10a8747b0>)iOS 16.6.1Will this be fixed in upcoming versions?

Release Date: 10-05-2024 🐛 Bug Fixes Fixed a crash that was affecting a small subset of users. ([ICMDataManager resetPresenceTimer]) Fixed some memory issues. Fixed some minor UI glitches. Fixed a crash that users were experiencing. ([ICMUserIdentity isEqual:])

Hello,I started getting memory leaks printed from Instruments after installing Intercom(17.0.2). Double checked by uninstalling(got 0 after uninstalling).The package was installed using SPM.  

io.intercom.android.sdk.survey.block.AttachmentBlockKt.VideoAttachmentBlockThis strange error apeared to a single user 3 times on my app, i wonder what could it beMy app runs in Flutter, android version, The SDK version is intercom_flutter: ^8.0.3here the error stack:Fatal Exception: java.lang.NoSuchMethodError: No virtual method at(Ljava/lang/Object;I)Lt/q0$a; in class Lt/q0$b; or its super classes (declaration of 't.q0$b' appears in base.apk)       at androidx.compose.material3.ProgressIndicatorKt$CircularProgressIndicator$endAngle$1.invoke(ProgressIndicator.kt:16)       at androidx.compose.material3.ProgressIndicatorKt$CircularProgressIndicator$endAngle$1.invoke(ProgressIndicator.kt:2)       at androidx.compose.animation.core.AnimationSpecKt.keyframes(AnimationSpec.kt:7)       at androidx.compose.material3.ProgressIndicatorKt.CircularProgressIndicator-LxG7B9w(ProgressIndicator.kt:448)       at io.intercom.android.sdk.survey.block.AttachmentBlockKt.VideoAttachmentBlock(:513)       at

We tried updating io.intercom.android:intercom-sdk from 15.6.3 to 15.8.2 and noticed that attaching photos from camera directly is broken (permission was given). On version 15.6.3 it works as expected. 

The documentation and sample app show Intercom.setAPIKey being called from a Scene delegate.  I would prefer not to configure that for my SwiftUI App if I don’t have to.  In addition, we normally do not compile keys like this into our App, instead preferring to fetch them from the server.Are there any restrictions on when I call Intercom.setAPIKey? Does it have to be called on the main thread? Do I have to call setAPIKey from the Scene delegate?  Can I wait to call it until after the user has logged in and communicated with our server to fetch the API key as long as I don’t call any other Intercom calls before that? Thanks,Tom 

Hello,I am using react native 0.72.6 and I followed your documentation. When I start the application on Android, the app directly crashes.React Native: 0.72.6Intercom: 7.0.1Error log;04-17 20:41:03.757 16506 16565 E AndroidRuntime: FATAL EXCEPTION: WM.task-104-17 20:41:03.757 16506 16565 E AndroidRuntime: Process: com.xx.xx, PID: 1650604-17 20:41:03.757 16506 16565 E AndroidRuntime: java.lang.NoSuchFieldError: No instance field mDelegate of type Landroid/database/sqlite/SQLiteStatement; in class Landroidx/sqlite/db/framework/FrameworkSQLiteStatement; or its superclasses (declaration of 'androidx.sqlite.db.framework.FrameworkSQLiteStatement' appears in /data/app/~~-CoVl2828_OGDZn2i-axfA==/com.xx.xx-4SqgA3KMc2bMy==/base.apk!classes6.dex)04-17 20:41:03.757 16506 16565 E AndroidRuntime:     at androidx.sqlite.db.framework.FrameworkSQLiteStatement.executeUpdateDelete(Unknown Source:0)04-17 20:41:03.757 16506 16565 E AndroidRuntime:     at androidx.work.impl.model.WorkProgressDao_Impl.delete

I’ve recently become unable to successfully build for Android with Intercom SDK I’m using "@intercom/intercom-react-native": "^7.0.1",and have configured my app.json / expo properly with  ["@intercom/intercom-react-native",{"appId": "lxxxxxxxxp","androidApiKey": "anxxxxxxxxxxxxxxxx196","iosApiKey": "ioxxxxxxxxxxxxxxxxx29f","intercomRegion": "US","isPushNotificationsEnabledIOS": "true" // I know this is currently unsupported though I did set up my code to push native tokens to intercom as I assume itll get there soon.}],FAILURE: Build failed with an exception.* What went wrong:Could not determine the dependencies of task ':intercom_intercom-react-native:compileDebugJavaWithJavac'.> Could not resolve all dependencies for configuration ':intercom_intercom-react-native:debugCompileClasspath'.   > Problems reading data from Binary store in /Users/joshuamohrer/.gradle/.tmp/gradle11368370330674472490.bin offset 1490991 exists? true* Try:> Run with --stacktrace option to get the stack

In Android SDK version 15.7.1, the "Recent Message" and "Start Conversation" sections fail to appear on the Home Page when the device's language is set to Turkish.Screenshots are attached, taken on the same device, demonstrating the issue by only changing the language setting.Could anyone help us identify the potential cause of this problem or suggest any solutions? Any advice or insights would be greatly appreciated. 

I'm seeking assistance with a problem we've encountered after updating our application to Android SDK version 15.8.x. Previously, under SDK version 15.7.1, users were able to take photos and send them as attachments without any issues. However, following the upgrade to SDK 15.8.x, the functionality to take and send photos as attachments no longer works. This issue has been observed across devices running Android Version 14.Could anyone help us identify the potential cause of this problem or suggest any solutions? Any advice or insights would be greatly appreciated.

When submitting our app to App Store Connect I am still receiving some warnings about missing required reasons. Using the binary-based scanner script located here I am seeing the following:Used symbols in binary ./Debug.app/Frameworks/Intercom.framework/Intercom: NSFileCreationDate, NSFileModificationDate, NSFileSystemFreeSize, NSFileSystemSize, NSURLContentModificationDateKey, NSURLCreationDateKey, NSUserDefaults, statLooking at the Intercom PrivacyInfo.xcprivacy as of version 17.0.0 I see entries for UserDefaults and SystemBootTime, but not FileTimestamp even though the script shows there are references within the framework to NSFileCreationDate, NSFileModificationDate, NSURLContentModificationDateKey, NSURLCreationDateKey and stat.Is this something you are aware of? Do you intend to add the appropriate reason to your privacy manifest?Thanks!

I've noticed that carousels (the automatic ones, meaning one controlled by our marketing team triggered based off user properties) render in our android app before app loading is completed. When app loading does complete, they dismiss themselves. So, they become basically unusable.We use the react native SDK.I didn't see any methods that I could use to control the lifecycle to disable it until app loading has completed. I don't want to have to rely on programmatically launching them since it kind of limits our growth team's capabilities.Any recommendations? I know that there’s a way to manually show articles by using the ID, but I’d love to be able to use this out-of-the-box platform-y set up that can enable our marketing team to use articles without engineering’s involvement. Haven’t been able to figure out from the documentation whether there’s a way to control the lifecycle.

I am unable to run any lldb debugger commands with intercom because I get the following error: warning: Swift error in scratch context: error: compiled module was created by a different version of the compiler '5.9.0.128.108'; rebuild 'Intercom' and try again: Intercom Aside from this, the app builds fine. Its just super annoying because I can no longer debug I am using Intercom 16.6.0

Hello Intercom Team. On iOS, since Friday April 5th, we are experiencing the following error when trying to add Intercom dependency through Swift Package Manager. We are using the last version of the SDK. 17.0.0Error:```xcodebuild: error: Could not resolve package dependencies:checksum of downloaded artifact of binary target 'Intercom' (5ed58eb8dd4392896a2b3e56c5c66fd862c2f3d29fb6d575d6a98a276cf944f7) does not match checksum specified by the manifest (d874522d04ed130894ca7026021151465b1d5a77fdb96a7ba905aea36260dce3)```Thanks in advance.

It seems that the new Intercom SDK is not working on Android Lollipop as there’s no minSdkVersion field in the ApplicationInfo class. This happened after the DeviceUtils.getAppMinSdkVersionVersion method was added in 15.6.2.Fatal Exception: java.lang.NoSuchFieldError: No instance field minSdkVersion of type I in class Landroid/content/pm/ApplicationInfo; or its superclasses (declaration of 'android.content.pm.ApplicationInfo' appears in /system/framework/framework.jar) at io.intercom.android.sdk.utilities.commons.DeviceUtils.getAppMinSdkVersionVersion(DeviceUtils.java:32) at io.intercom.android.sdk.metrics.MetricTracker.<init>(MetricTracker.java:608) at io.intercom.android.sdk.metrics.MetricTracker.<init>(MetricTracker.java:597) at io.intercom.android.sdk.Injector.getMetricTracker(Injector.java:249) at io.intercom.android.sdk.Injector.getOverlayPresenter(Injector.java:272) at io.intercom.android.sdk.Injector.getResetManager(Injector.java:

Whenever we schedule a post from Intercom, user receives a push notification and opening it leads to a crash.It was working before we updated Intercom to 17.0.0, previous version we were on was 16.5.5. We are wondering if it's related to the change introduced in 16.6.0.iOS version we tested with: iOS 17.3.1, 17.4.1, 17.5Here's the stack trace: Last Exception Backtrace:0 CoreFoundation 0x1949cbf24 __exceptionPreprocess + 164 (NSException.m:249)1 libobjc.A.dylib 0x18c862018 objc_exception_throw + 60 (objc-exception.mm:356)2 Foundation 0x193897fe8 -[NSConcreteMutableAttributedString initWithString:attributes:] + 356 (NSAttributedString.m:1029)3 Intercom 0x105be84fc -[ICMActionButton initWithTitle:style:backgroundColor:foregroundColor:] + 3764 Intercom 0x105be82c4 -[ICMActionButton initFilledButtonWithTitle:] + 1405 Intercom 0x105c3cd24 -[ICMClosedConversationVie

All xcFrameworks on Intercom github have invalid signature hence apps using Intercom SDK can not compile at all  

Fatal Exception: android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.intent.action.VIEW dat=https://example.com/... } at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:2031) at android.app.Instrumentation.execStartActivity(Instrumentation.java:1686) at android.app.Activity.startActivityForResult(Activity.java:4506) at androidx.activity.ComponentActivity.startActivityForResult(ComponentActivity.java:780) at android.app.Activity.startActivityForResult(Activity.java:4464) at androidx.activity.ComponentActivity.startActivityForResult(ComponentActivity.java:761) at android.app.Activity.startActivity(Activity.java:4829) at android.app.Activity.startActivity(Activity.java:4797) at io.intercom.android.sdk.blocks.messengercard.MessengerCardWebViewInterface.openUrl(MessengerCardWebViewInterface.java:141) at io.intercom.android.sdk.blocks.messengercard.MessengerCardWebVie

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

We’ve been getting crash reports that the app is failing to start on iOS 16. Upon further investigation, we got to this stack trace. You can see that the culprit seems to be a method swizzling you’re doing on applicationDidFinishLaunching. We’ve already tried to opt out of swizzling by setting IntercomAutoIntegratePushNotifications in Info.plist but no luck. 

Hello, I’m trying to integrate Intercom push notifications into my react-native app. I’m using official wrapper in version 6.8.1 (most up to date one). I did all of the steps from iOS setup section and configured Push Notifications on intercom website - https://app.intercom.com/a/apps/myapp/settings/ios. I’m sure that uploaded .p8 key, bundle id, key id and apple team id are correct because I uploaded the same version to firebase console and I’m able to send notifications from there and using their HTTP API. On intercom I’m all the time getting BadDeviceToken. On Android everything works properly. Am I missing something on iOS? I tried both ways of sending token to Intercom - javascript version and Obj-C version.For js version I’m using `@react-native-firebase/messaging` and call `await messaging().getToken()`. Using this token I’m getting BadDeviceToken