Zeya Peng

This commit **enables** the `enableViewTransitionForPersistenceMode` feature flag within the **React Native internal feature flags mock**. This **configuration change** activates a new capability related to **view transitions and persistence mode**, likely to improve user experience or performance in specific scenarios. By updating `ReactNativeInternalFeatureFlags.js`, this change facilitates internal testing and development of this new view transition behavior.

This commit **refactors** the **React Native renderer's ViewTransitionModule** to improve how layout metrics are captured and applied during view transitions. The `applyViewTransitionName` function now directly consumes layout metrics returned by `captureLayoutMetricsFromRoot`, rather than relying on a side effect or stored state. This **maintenance** change streamlines the measurement process for view transitions, making the data flow more explicit within the **rendering pipeline**. While the immediate runtime behavior is generally unaffected, this **refactoring** enhances the internal consistency and clarity of the view transition system.

This commit **fixes a bug** and **refactors** the **ViewTransitionModule** in React Native to prevent an iterator invalidation issue. Previously, the `startViewTransitionEnd` function could cause undefined behavior by removing entries from `nameRegistry_` while iterating over it. The `onTransitionAnimationEnd` function has been **inlined** into its single call site, and the `nameRegistry_` is now cleared *after* the iteration loop, eliminating the need for a copy and ensuring correct and stable handling of view transitions. This change improves the robustness and reliability of the view transition system.

This commit **reverts a problematic change** within the **iOS native animation system** to **fix a critical bug** causing an `Invariant Violation`. Specifically, it restores `RCTAnimatedModuleProvider` to always provide the `AnimatedModule` when `cxxNativeAnimatedEnabled` is true, regardless of the `useSharedAnimatedBackend()` flag. The previous change, intended for `DefaultTurboModules` fallback, inadvertently caused `RCTReactNativeFactory` on iOS to return `nullptr` for the animated module, leading to crashes on surfaces using `Animated.View` when `react_fabric.enable_shared_animated_backend_ios` was enabled. This **bug fix** ensures the **iOS TurboModule resolution chain** correctly supplies the native animated module, preventing runtime errors.

This commit introduces a **new capability** by adding the `unstable_getViewTransitionInstance` API to the **UIManagerBinding** and **FabricUIManager** within React Native. This allows JavaScript to imperatively retrieve position and dimension information for **view transition pseudo-elements**, which are crucial for advanced animation scenarios. The change primarily affects the **View Transition API** implementation, extending `UIManagerViewTransitionDelegate` and `ViewTransitionModule` to provide these layout metrics. This enhancement enables developers to implement custom, smooth animations for view transitions in React Native, similar to React's web `onEnter` callback for `<ViewTransition>`, by providing access to the underlying native view instances.

This commit **refactors** the **TurboModuleManager** in React Native's C++ platform layer by reordering its module lookup logic. Specifically, it moves the invocation of `DefaultTurboModules::get` to the end of the `TurboModuleManager::operator()` method, ensuring that default module resolution occurs last. This change **aligns the C++ implementation with Android and iOS counterparts**, allowing custom or platform-specific module registrations to **override default behaviors** more predictably. It also streamlines the lookup process by removing direct handling for `NativePerformance`, improving the overall consistency and extensibility of the **TurboModule system**.

This commit **adds** the **C++ AnimatedModule** to **DefaultTurboModules**, establishing it as the default animation module for open-source React Native applications when both C++ animated and shared backend feature flags are enabled. This **new capability** simplifies the adoption of the C++ AnimatedModule by acting as a fallback for apps not explicitly using legacy providers like `RCTAnimatedModuleProvider` or `AnimatedCxxReactPackage`. It involves **refactoring** existing animation module providers and the `TurboModuleManager` to ensure proper conditional initialization and prevent conflicts with the new default, while also updating iOS package dependencies. The change streamlines the animation setup, leveraging the shared backend to provide a cleaner, static initialization path for the `NativeAnimatedNodesManagerProvider`.

This commit introduces **new APIs and an interface** to the **UIManager** to support **declarative view transitions**. It adds the `UIManagerViewTransitionDelegate` interface and implements JSI bindings in `UIManagerBinding` for functions like `measureInstance`, `applyViewTransitionName`, and `startViewTransition`. This **new capability** enables the React Fabric renderer to integrate with the `<ViewTransition/>` component, allowing for orchestrated visual transitions between UI states. The delegate methods are gated by a feature flag, providing a foundation for advanced UI animations within the React Native ecosystem.

This commit **introduces** the foundational **`ViewTransitionModule`** within the **Fabric renderer** to enable native **view transitions** in React Native. It orchestrates enter, exit, and shared element transitions by managing view state, capturing layout metrics, and handling `view-transition-name` registration. The module is integrated into the **`Scheduler`** and activated via a feature flag, providing a new **capability** for rich UI animations. This **feature addition** also includes **refactoring** to `UIManager` interfaces, specifically updating `UIManagerViewTransitionDelegate` methods to pass `ShadowNode` by const reference. This work lays the essential native groundwork for sophisticated view transition effects.

This commit **introduces new capabilities** to the **React Native Animated API** by adding the `useAnimatedColor` and `useAnimatedValueXY` hooks. These new hooks allow developers to animate color values and XY coordinate pairs, respectively, expanding upon the existing `useAnimatedValue` which only supports number animation. By moving these into the main `react-native` package and exporting them from `index.js` (along with their Flow types), they are now **available for Open Source Software (OSS) consumption**, enabling more complex and expressive animations for the community.

This commit introduces a **new capability** by adding the `viewTransitionEnabled` feature flag across **React Native's core platform layers**. This flag is designed to gate the future **View Transition API**, which will provide animated transitions for a smoother user experience when navigating or updating UI. It impacts **JavaScript**, **Android Kotlin**, and **C++/JNI** feature flag implementations, as well as the central configuration file `ReactNativeFeatureFlags.config.js`. By defaulting to `false`, this flag enables controlled, opt-in experimentation and gradual rollout of the View Transition API.

This commit **refactors** the **Android native animation** and **scroll modules** by **decoupling** `ReactScrollViewHelper` from a direct dependency on `NativeAnimatedModule`. It introduces a new `ScrollEndedListener` interface and `ScrollEndedListeners` class within `ReactContext` to provide a **decoupled notification mechanism** for scroll end events. This change eliminates a **circular dependency** in the build system, improving the **modularity**, **maintainability**, and **testability** of these core components. `NativeAnimatedModule` now registers as a listener, receiving scroll end events without direct coupling to `ReactScrollViewHelper`.

This commit **fixes a critical security vulnerability** in the **`MapBuffer` component** by preventing **out-of-bounds memory reads** in **release builds**. Previously, accessor methods like `getInt()`, `getLong()`, and `getDouble()` could attempt to read from invalid memory locations when a requested key was not found, leading to potential **information disclosure or crashes**. The **fix** introduces robust **runtime checks** within `MapBuffer.cpp` to ensure safe access even when `react_native_assert` macros are stripped, thereby enhancing the stability and security of `React Native` applications in production. This **maintenance** update ensures that missing keys are handled gracefully, preventing memory corruption and unexpected application termination.

This commit **enables the new animation backend by default** across the React Native core, removing previous conditional compilation that made it an optional feature. It **refactors** the `NativeAnimatedNodesManagerProvider` and `Scheduler` to always initialize the animation backend, eliminating the need for the `-DRN_USE_ANIMATION_BACKEND` build flag. Additionally, the `React-Fabric.podspec` is updated to include the animation backend as a mandatory dependency, ensuring that all applications utilizing the **Fabric renderer** will now leverage this standardized animation system. This change streamlines the animation architecture, making the new backend an integral part of the platform and promoting consistent animation behavior.

This commit **enhances the robustness** of React Native's **animation backend** by introducing `default` cases to critical `switch` statements. Specifically, it adds error handling within `packBackfaceVisibility` and `packAnimatedProp` in `AnimatedPropSerializer.cpp` to catch unknown enum values during property serialization. Furthermore, the `updateProp` function in `AnimatedPropsRegistry.h` now includes a default case to manage unknown property names. This **fix** prevents unexpected behavior or potential crashes by gracefully handling unmapped values, ensuring more stable and predictable animation processing.

This commit introduces a **robustness improvement** and **bug fix** to the **React Native Animated module** on **Android**. It modifies `InterpolationAnimatedNode.kt` to detect and handle unsupported value types, such as `PlatformColor`, when they are passed to an interpolation's `outputRange`. This change **prevents a `ClassCastException` crash** by logging an informative error instead of terminating the application. Consequently, it enhances the **stability** and **debuggability** of animations, guiding developers to correct invalid animation configurations.

This commit **upgrades** the `node-forge` JavaScript cryptography library to version `1.3.2` within the `react-native-github` project, as reflected in the `yarn.lock` file. This essential **dependency upgrade** serves as a **security fix** to address `CVE-2025-12816`, which details an "Interpretation Conflict" vulnerability. By updating `node-forge`, the project significantly enhances its **security posture** and mitigates potential risks associated with cryptographic operations. This ensures more robust and secure handling of sensitive data within the affected modules.

This commit **adds new benchmark tests** for the **`Animated` module's backend performance** within `react-native`. It introduces a `fantom` benchmark test in `packages/react-native/Libraries/Animated/__tests__/AnimatedBackend-benchmark-itest.js` to evaluate performance. This **new capability** specifically covers various animation scenarios and component rendering, testing both with and without the dedicated animation backend. This **internal addition** helps monitor and ensure the efficiency and responsiveness of the `Animated` system.

This commit provides a **bug fix** to the **`NativeAnimated` module** within `react-native`, specifically addressing a potential crash in the animation system. It introduces **null checks** for the result of `getAnimatedNode` within the `NativeAnimatedNodesManager::updateNodes` function in `packages/react-native/ReactCommon/react/renderer/animated/NativeAnimatedNodesManager.cpp`. This change prevents crashes that could arise if an animated node is unexpectedly null, significantly improving the **stability** and reliability of native animations.

This commit **removes the `cxxNativeAnimatedRemoveJsSync` feature flag** from the codebase, signifying its permanent enablement. The flag, which previously controlled a specific JavaScript synchronization behavior within the **Native Animated** module, is no longer needed as it has been fully rolled out without issues. This **refactoring** simplifies the **React Native Feature Flags** system across JavaScript, Android (Kotlin/Java/JNI), and C++ implementations, and streamlines the logic within `Animation.js`, `createAnimatedPropsHook.js`, and `NativeAnimatedNodesManager.cpp` by removing conditional checks. The change ensures that the optimized C++ animated path is consistently active, improving code clarity and maintaining the established performance characteristics of **Native Animated** components.