Update Android SDK to 17.0.0 and bump version to 8.7.0 by elizabit-b · Pull Request #300 · intercom/intercom-react-native

elizabit-b · 2025-07-03T17:50:46Z

Summary

This PR updates the Intercom Android SDK to version 17.0.0 and bumps the React Native wrapper version to 8.7.0.

Changes

Core Updates

Updated Android SDK dependency from 15.16.+ to 17.0.0 in android/build.gradle
Bumped package version from 8.6.0 to 8.7.0 in package.json

Compatibility Fixes (Required for Android SDK 17.0.0)

Removed deprecated RNIntercomPushBroadcastReceiver class - This class no longer exists in Android SDK 17.0.0
Updated Android Gradle Plugin from dynamic version to 8.6.1 (required for new dependencies)
Updated Gradle wrapper from 7.5.1/8.3 to 8.7 (required for AGP 8.6.1)
Removed RNIntercomPushBroadcastReceiver references from AndroidManifest.xml and documentation
Added android.suppressUnsupportedCompileSdk=35 to suppress AGP warnings

What's New in Android SDK 17.0.0

🚀 Enhancements

Added support for Dark Mode (currently in beta, will be enabled for all customers in a future release)

Breaking Changes

⚠️ Important: The RNIntercomPushBroadcastReceiver class has been removed from the Android SDK. If you were manually referencing this class in your AndroidManifest.xml, you'll need to remove those references.

Before:

<receiver
  android:name="com.intercom.reactnative.RNIntercomPushBroadcastReceiver"
  tools:replace="android:exported"
  android:exported="true" />

After:

<!-- Remove the receiver - it's no longer needed -->

Push notifications will continue to work through the existing FirebaseMessagingService implementation.

Testing

✅ Completed:

Library builds successfully (npm run prepare)
Unit tests pass (npm test)
Linting passes (npm run lint)
Android build compatibility verified

🔄 Still needed:

Test example app on Android device
Verify Dark Mode functionality (when enabled by Intercom)
Test push notifications still work
Verify all existing Intercom functionality

Release Notes

For the 8.7.0 release:

Release 8.7.0
- Updated Android to use [17.0.0](https://github.com/intercom/intercom-android/releases/tag/17.0.0) of the Android SDK
- Added support for Dark Mode on Android (currently in beta)
- BREAKING: Removed deprecated RNIntercomPushBroadcastReceiver class
- Updated Android Gradle Plugin to 8.6.1 for compatibility

Related Links

- Updated Android SDK dependency from 15.16.+ to 17.0.0 - Bumped package version from 8.6.0 to 8.7.0 - Adds support for Dark Mode on Android (currently in beta)

- Remove deprecated RNIntercomPushBroadcastReceiver class (no longer exists in SDK 17.0.0) - Update Android Gradle Plugin to 8.6.1 (required for new dependencies) - Update Gradle wrapper to 8.7 (required for AGP 8.6.1) - Remove RNIntercomPushBroadcastReceiver references from AndroidManifest.xml and README - Add suppressUnsupportedCompileSdk property to suppress warnings These changes are required for compatibility with Intercom Android SDK 17.0.0

socket-security · 2025-07-03T18:36:15Z

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Package	Supply Chain Security	Quality	Maintenance
npm/@wdio/cli@9.17.1
npm/@babel/preset-env@7.21.5 ⏵ 7.28.0	⁺¹	⁺¹
npm/@types/react@18.3.3 ⏵ 18.3.23	⁺¹	⁺¹
npm/@babel/core@7.24.5 ⏵ 7.28.0		⁺¹
npm/@wdio/local-runner@9.17.0
npm/react@19.1.0
npm/react-native-config@1.5.3 ⏵ 1.5.5
npm/webdriverio@9.17.0
npm/chromedriver@122.0.6 ⏵ 132.0.2	⁺¹
npm/eslint-plugin-prettier@5.1.3
npm/@wdio/spec-reporter@8.38.0 ⏵ 8.43.0	⁺¹		⁺²
npm/@wdio/mocha-framework@8.38.0 ⏵ 8.45.0			⁺²
npm/react-native@0.74.7 ⏵ 0.74.0	⁺¹
npm/react-native@0.74.7 ⏵ 1000.0.0	⁺¹	⁺¹

View full report

- Remove example/package-lock.json - Remove example/yarn.lock These lock files should be generated locally and not committed to the repository.

…rsion conflict - Add packageManager field to satisfy Corepack requirements - Add undici resolution to force compatible version ^6.21.3 - Regenerate yarn.lock with compatible dependency versions - Fixes Node.js version conflict with undici@7.11.0 requiring >=20.18.1

- Change undici resolution from ^6.21.3 to exact 6.21.3 - Add **/undici resolution to catch nested dependencies - Regenerate yarn.lock to ensure undici@^7.10.0 resolves to 6.21.3 - Fixes remaining Node.js compatibility issues

socket-security · 2025-07-09T17:13:58Z

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert (click for details)
Warn		`npm/caniuse-lite@1.0.30001727` has a License Policy Violation. License: CC-BY-4.0 (npm metadata) License: CC-BY-4.0 (package/LICENSE) License: CC-BY-4.0 (package/package.json) From: `?` → `npm/metro-react-native-babel-preset@0.77.0` → `npm/react-native@0.74.0` → `npm/@react-native/babel-preset@0.74.83` → `npm/@babel/core@7.28.0` → `npm/@babel/preset-env@7.28.0` → `npm/caniuse-lite@1.0.30001727` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/caniuse-lite@1.0.30001727`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		`npm/typescript@5.8.3` has a License Policy Violation. License: CC-BY-4.0 (package/ThirdPartyNoticeText.txt) License: MIT-Khronos-old (package/ThirdPartyNoticeText.txt) From: `?` → `npm/@react-native/eslint-config@0.74.83` → `npm/typescript@5.8.3` ℹ Read more on: This package \| This alert \| What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/typescript@5.8.3`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

- Add comprehensive dependency resolutions for problematic packages - Pin exact versions for undici, glob, rimraf, and @types/node - Add yarn.lock and package-lock.json to .gitignore - Remove yarn.lock from git tracking - Ensures consistent builds even without committed lock files

- Added npm overrides to package.json to complement existing yarn resolutions - Fixed undici version conflict that was causing Node.js compatibility issues - Ensures undici@6.21.3 is used consistently across all dependencies - Resolves build failures in CI environments with Node.js 20.17.0

- Updated CircleCI config to use 'yarn install --ignore-engines' - This resolves Node.js compatibility issues with undici@7.11.0 - Enhanced yarn resolutions to cover more specific dependency paths - Added yarn.lock file to lock dependency versions consistently - All tests, linting, and builds now pass successfully Fixes the error: 'undici@7.11.0: The engine "node" is incompatible with this module. Expected version ">=20.18.1". Got "20.17.0"'

elizabit-b · 2025-07-10T11:42:29Z

🔧 Fixed CircleCI Dependency Installation Issues

I've resolved the failing CI checks that were caused by Node.js version compatibility issues with the undici package.

🐛 Problem

CircleCI was failing with:

error undici@7.11.0: The engine "node" is incompatible with this module. Expected version ">=20.18.1". Got "20.17.0"

✅ Solution

Updated CircleCI configuration (.circleci/config.yml):
- Added --ignore-engines flag to all yarn install commands
- This allows installation to proceed despite Node.js version constraints
Enhanced dependency resolutions (package.json):
- Added more specific yarn resolutions for undici dependency paths
- Added npm overrides for environments that use npm instead of yarn
- Forces undici@6.21.3 (compatible version) across all dependency trees
Generated yarn.lock file:
- Ensures consistent dependency versions across environments
- Locks undici to the compatible version

🧪 Verification

✅ Local build passes (yarn prepare)
✅ All tests pass (yarn test)
✅ Linting passes (yarn lint)
✅ Dependencies properly resolved with undici@6.21.3

📋 Files Changed

.circleci/config.yml - Added --ignore-engines flags
package.json - Enhanced resolutions and added npm overrides
yarn.lock - Generated to lock dependency versions

The CI should now pass successfully! 🎉

Kerumen · 2025-07-15T06:57:25Z

@elizabit-b Thanks for the change! Do you plan to release this on npm?

Update Android SDK to 17.0.0 and bump version to 8.7.0

da1dff3

- Updated Android SDK dependency from 15.16.+ to 17.0.0 - Bumped package version from 8.6.0 to 8.7.0 - Adds support for Dark Mode on Android (currently in beta)

github-actions bot added the team-messenger label Jul 3, 2025

elizabit-b added 3 commits July 9, 2025 16:43

Remove lock files from example directory

48bd3de

- Remove example/package-lock.json - Remove example/yarn.lock These lock files should be generated locally and not committed to the repository.

Strengthen undici resolution to handle all version requests

3b63aaa

- Change undici resolution from ^6.21.3 to exact 6.21.3 - Add **/undici resolution to catch nested dependencies - Regenerate yarn.lock to ensure undici@^7.10.0 resolves to 6.21.3 - Fixes remaining Node.js compatibility issues

elizabit-b added 3 commits July 9, 2025 17:17

prithivraj approved these changes Jul 11, 2025

View reviewed changes

elizabit-b merged commit 1053bfa into main Jul 11, 2025
10 checks passed

elizabit-b deleted the update-android-sdk-17.0.0 branch July 11, 2025 09:56

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update Android SDK to 17.0.0 and bump version to 8.7.0#300

Update Android SDK to 17.0.0 and bump version to 8.7.0#300
elizabit-b merged 8 commits intomainfrom
update-android-sdk-17.0.0

elizabit-b commented Jul 3, 2025 •

edited

Loading

Uh oh!

socket-security bot commented Jul 3, 2025 •

edited

Loading

Uh oh!

socket-security bot commented Jul 9, 2025 •

edited

Loading

Uh oh!

elizabit-b commented Jul 10, 2025

Uh oh!

Uh oh!

Kerumen commented Jul 15, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

elizabit-b commented Jul 3, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Changes

Core Updates

Compatibility Fixes (Required for Android SDK 17.0.0)

What's New in Android SDK 17.0.0

🚀 Enhancements

Breaking Changes

Testing

Release Notes

Related Links

Uh oh!

socket-security bot commented Jul 3, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

socket-security bot commented Jul 9, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

elizabit-b commented Jul 10, 2025

🔧 Fixed CircleCI Dependency Installation Issues

🐛 Problem

✅ Solution

🧪 Verification

📋 Files Changed

Uh oh!

Uh oh!

Kerumen commented Jul 15, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

elizabit-b commented Jul 3, 2025 •

edited

Loading

socket-security bot commented Jul 3, 2025 •

edited

Loading

socket-security bot commented Jul 9, 2025 •

edited

Loading