feat!: remove support for React Native old architecture

[mrehan27]

closes: Remove Support for React Native Old Architecture

Summary

This PR removes all remaining code and logic related to React Native's old architecture, simplifying the SDK codebase to fully support and rely on New Architecture (TurboModules + Fabric). This aligns with React Native's direction of deprecating old architecture and simplifies maintenance, and future feature work.

Changes

• This includes previously approved changes:
  • chore: update example app to React Native 0.83 #545
  • chore: remove old architecture event listener callbacks #546
  • chore: remove old architecture support in Android implementation #547
  • chore: remove old architecture support in iOS implementation #548
• Example app now only targets New Architecture and uses React Native 0.83
• Updated Android SDK from 4.13.0 to 4.14.0

Notes

• ⚠️ This completely removes support for old architecture to reduce codebase complexity and align the SDK with React Native's roadmap and direction
• Customers still using old React Native architecture will be affected and must upgrade to new architecture to continue using the SDK
• Customers already using the new architecture will not be impacted
• No changes to public JavaScript APIs, this is entirely internal to native module setup

References

• React Native 0.83 blog post

---

Note

Fully removes React Native old-architecture paths and consolidates the SDK on new-architecture modules and Fabric UI components.

• Unifies Android modules under BaseReactPackage (no old/new split); always apply com.facebook.react; removes new-arch toggles/sourceSets; updates cioSDKVersionAndroid to 4.14.0
• Rewrites native modules (NativeCustomerIO*, Logging, In-App, Push) to TurboModules-only; replaces legacy impl helpers with direct modules; aligns APIs (setProfileAttributes/setDeviceAttributes) and event emission via codegen EventEmitter
• iOS wrappers cleaned to TurboModules-only (no RCT_EXTERN/legacy paths); inline in-app view uses Fabric RCTViewComponentView and proper protocol; removes legacy view manager
• TypeScript specs drop legacy addListener/removeListeners; JS listeners now attach via codegen EventEmitter with try-catch fallbacks (no NativeEventEmitter)
• Example app upgrades to React Native 0.83 and React 19.2; lockfiles bumped (Hermes, Metro, eslint configs, etc.) and minor iOS script quoting fix

^{Written by Cursor Bugbot for commit 8bd725c. This will update automatically on new commits. Configure here.}

[github-actions]

Sample app builds 📱

Below you will find the list of the latest versions of the sample apps. It's recommended to always download the latest builds of the sample apps to accurately test the pull request.

---

• Android APN: 553.6.0 (29441758)
• iOS APN: 553.6.0 (29441758)

[cursor]

Removed armeabi crash protection in logging module

The previous new architecture logging module (src/newarch/.../NativeCustomerIOLoggingModule.kt) included explicit protection to skip TurboModule event emission on armeabi/armeabi-v7a devices with the comment "avoid known native (C++) crashes on unsupported ABIs". This isABIArmeabi check and runOnSupportedAbi wrapper have been removed in the consolidated module. While the code is wrapped in runWithTryCatch, Java try-catch cannot intercept native C++ crashes (SIGSEGV). On affected architectures, logging events could now trigger crashes that were previously avoided. This may be acceptable given React Native 0.83's new architecture focus, but the protection was explicitly added for a reason.

 

[mrehan27]

That's correct. At some point we might remove this try-catch too since it doesn't really help with C++ crashes and isn't something we can control. For now, we'll keep the simple try-catch and re-evaluate once this version is rolled out more widely and we see how it behaves.

[mahmoud-elmorabea]

💯

[Shahroz16]

should we probably make it a breaking change? as we are removing the support for old arch?