Expo Changelog

Bug Fixes

• update customerio-reactnative to 6.6.2 (#384) (c690ac3)
  • Android 4.20.1 — Geofence enter/exit event accuracy (release notes)
  • iOS 4.7.2 — Geofence enter/exit reliability and in-app page route rule matching (release notes)

Features

• Enable Live Notifications feature (#382) (b80ac4e)
• geofence: add support for geofencing feature (#379) (0dc528e)
• Visual Notification Inbox overlay

Bug Fixes

• update customerio-reactnative to 6.5.2 (#367) (80572f9)

Bug Fixes

• update customerio-reactnative to 6.5.1 (#366) (1b78fa7)
  • Android 4.18.1 — Harden push notification activity and in-app message WebView (release notes)
  • iOS 4.5.1 — Internal test-isolation refactor; no runtime impact (release notes)

Features

• bump customerio-reactnative to 6.5.0 (#365) (1e61e76)

Bug Fixes

• bump customerio-reactnative to 6.4.3 (#364) (267288f)

Bug Fixes

• cover AppDelegate.swift per pinned SDK with fixtures (#363) (9d49819)
• logging: keep plugin diagnostics off stdout (#362) (cb24e14)

Bug Fixes

• ios: Corrected PBXContainerItemProxy bucket aliasing (#359) (6ecd751)

Features

• tests: fixture-based scenario suite + CI cleanup (#358) (2e869ff)

Features

• pnpm support (#339) (ab06bcd)

Bug Fixes

• inject killed-state deep link workaround before factory.startReactNative (https://github.com/customerio/customerio-expo-plugin/pull/337)

Features

• Push delivery reslience improvement (#333) (791b847)

Features

• Locaiton enrichment (#328) (53db70e)

Features

• Added support for Notification Inbox (#327) (e8bb3a7)

Bug Fixes

• Downgrade okhttp to v4.x (#325) (60a5b89)

⚠ BREAKING CHANGES

• remove React Native old architecture support (#323)

Features

• remove React Native old architecture support (#323) (0f96132)

RN

• Exposed trackMetric method for manually tracking push notification metrics. This is useful when using multiple push providers or displaying notifications without relying on Customer.io SDK. (#539) (43deefe)
• In-app messages now support SSE (Server-Sent Events) as an alternative to polling, reducing latency and improving message delivery efficiency (#555) (a777c69)

Features

• auth: DX-809 update to use preferred OIDC for npm publish in github actions #321 (#321) (d595723)

Bug Fixes

• in-app listener for android (#320) (352cc5e)

Features

• Updated the SDK and dependencies for Android 16 compatibility, including minor updates to better support newer OS restrictions and behavior changes. (#319) (2537f17)

⚠️ Notes

• Apps now may need to update their compileSdk version to 36 and Gradle version to at least 8.9.3 to ensure compatibility with updated dependencies and to successfully build against Android 16.
• Apps not using the required compileSdk or Gradle versions may experience issues. The plugin attempts to downgrade dependencies automatically. If issues persist, Android 16 support can be disabled by setting android.disableAndroid16Support to true in plugin configuration.

Bug Fixes

• prevent message type crash in release builds (#318) (71e40d7)

Bug Fixes

• remove deprecated maven dependency (#316) (cb2f8b5)

Features

• Use latest RN SDK version and internally use CioFirebaseWrapper (#314) (0fb27c3)

Features

• You can now send banners, modals, pop-ups, and surveys to anonymous visitors —no ID or email required.
• Improve push notification delivery receipts delay for android (#313) (ad96c18)

Breaking Features

• Support for Kotlin 2+ is added (#591) (b5f94ff)

but this also means apps needs to have the following minimum requirement, which should already be covered in Expo 53 and above

• Gradle: 8.0 or later
• Android Gradle Plugin (AGP): 8.0 or later (8.2+ recommended)
• Kotlin: 1.9.20 or later (2.0+ required if using Kotlin Multiplatform or K2-specific features)

Bug Fixes

• Resolved a crash when dismissing in app messages using back press during initial loading phase. Users can now safely navigate away from messages without encountering unexpected app crashes
• Fix in-app inline tabbed bug

Bug Fixes

• Disabled native logging on armeabi devices using new architecture to prevent rare crashes from low level C++ code, no functional impact to end users. (#312) (f970974)

Bug Fixes

• Improved plugin logging and is now limited to node development environments by default and can be enabled manually by setting CUSTOMERIO_DEBUG_MODE=true in env (#306) (aa32215)
• Auto initialization config is now lenient and only runs during prebuild. To enforce strict checks, set CUSTOMERIO_STRICT_MODE=true in env (#307) (d57d650)
• Push config is now optional if app includes a valid google-services.json using other means, auto-initialization will work as long as the build succeeds (#300) (548bc01) (#309) (a69e62b)

Bug Fixes

• Removed the need to import React Native SDK header on iOS in auto generated code to resolve compatibility issues. (#303) (0f16213)

Improvements

• Updated React Native SDK from 4.7.0 to 4.8.0 which includes following updates: (#294) (a0e6190)
  • Added support for queueing sticky sessions on iOS
  • Aligned iOS public API with other Customer.io SDK platforms
  • Fixed build issues on Xcode 26 beta that only affected apps using CocoaPods
  • Fixed an issue where custom scheme URLs were not opening when using FCM with CioAppDelegateWrapper
• When setHighPriorityPushHandler is explicitly set to false, Firebase Messaging service is now added to Android manifest with a lower priority (-10, previously -1) to reduce the chance of conflicts with other push handlers (#297) (cb72527)

✨ Expo Plugin: Auto Initialization Support for React Native SDK

• Customer.io React Native SDK can now be configured directly from app.json, removing the need to call CustomerIO.initialize() manually in JavaScript. This update enables automatic SDK initialization at app startup when a valid config is present, requiring only the cdpApiKey (region is needed for EU, siteId for in-app messaging). It is compatible with Expo SDK 53+ and fully backward compatible, manual initialization continues to work without any warnings. Read more in plugin docs. (#292) (529306b)

Utilizing React Native New Architecture

• This release fully adopts React Native's new architecture using Fabric and TurboModules while maintaining compatibility with old architecture. No changes to public API, apps will automatically use appropriate setup based on their configuration. (#278) (96e4069)

Fixes and Tooling update

• Support for FCM 12.x is added which requires a minimum iOS deployment target of 15. If you're using FCM module, ensure your deployment target and tooling are up to date. Or lock Firebase to 11.x to avoid compatibility issues
• Fixes a crash when build attributes from device are nullable

Features

• Add ability to configure messaging channels for local notifications (#277) (4d7b620)

Bug Fixes

• Preserve numeric types when doing sanitization for JSON (#276) (6384279)

Features

• Includes new system for accessing device-token and tracking notifications events. This replaces old Swizzling-based system, in iOS SDK. The change increases stability and improves compatibility with other SDKs (like Firebase) (#273) (44fa3fc)

Features

• Added support for inline in-app messages. Inline in-app messages act like a part of the content on your page. They let you dynamically populate parts of your app and talk to your customers without interrupting their experience. (#274) (8133e7d)

Features

• Expo 53 support (#268) (fba26e3) #264 #265 #266 The CIO plugin now supports Expo 53 but it remains backward compatible for folks who aren't ready to upgrade to Expo 53 yet

Bug Fixes

• sample apps workflows to run with xcode 16.2 (#261) (7f17c03)

Bug Fixes

• Improves clarity and reduces configuration errors by grouping all iOS push notification settings under a unified pushNotification property; the previous configuration pattern has been deprecated (but not yet removed) and will be unsupported in future releases.(#247)