Hey @Jeet Vani, Emily here from Support Engineering at Intercom 👋🏼
The error you're seeing, java.lang.NullPointerException: Cannot invoke "String.length()" because "<parameter1>" is null, is likely related to a known issue in the Intercom Android SDK where a parameter (such as composeView) is unexpectedly null. This can cause crashes in methods like addInappNotificationCardToView in the InAppNotificationCardKt class.
To address this:
- Ensure that the parameter in question is not null before passing it to the method. Adding a null check can help handle this scenario gracefully as a workaround.
- This issue has been fixed in newer versions of the Intercom Android SDK. Upgrading to at least version 16.2.0 is recommended.
If you are using version 15.10.3, updating to the latest SDK version should resolve the crash. If you cannot update immediately, implement a null check as a temporary workaround :)
Hello,
I noticed that the React Native library often links to older versions of the Intercom native SDKs for both iOS and Android, which may still include bugs that have already been fixed in more recent releases.
For example, the latest version of intercom-react-native (8.5.0) targets version 15.16.1 for Android and 18.6.1 for iOS. However, I encountered an issue in iOS 18.6.1 that causes the app to freeze when a user closes a post.
To address this, I created a Yarn patch to use 18.7.3 on iOS, which appears to resolve the issue.
My question is:
Is it safe to upgrade (and what’s the recommended way) to newer native SDK versions manually, even if they aren't officially targeted by the current version of intercom-react-native?
Thank you!
