You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[0.89] Enable the shared animation backend in open source #1523
Turns on the shared animation backend in open source. The OSS stable overrides set useSharedAnimatedBackend and optimizedAnimatedPropUpdates to true, and both flags become canary. Meta's internal defaults do not change. With the backend on, C++ Animated drives its updates through the shared animation backend. That lets the native driver animate layout props, and Reanimated builds on it.
This depends on #1520, which picks react/react-native#59936 (C++ Native Animated to stable). The backend needs C++ Native Animated.
On 0.89-stable, with or without #1520, the pick conflicts only in the @generated SignedSource headers of ReactNativeFeatureFlagsOverridesOSSCanary.h and ReactNativeFeatureFlagsOverrides_RNOSS_Canary_Android.kt. Running yarn featureflags --update regenerates them.
changed the title [-][0.89] Promote the shared animation backend to stable[/-][+][0.89] Enable the shared animation backend in open source[/+]on Nov 12, 2026
Picked into 0.89-stable for 0.89.0-rc.2 as cd1c75ec5a3.
The cherry-pick conflicted on two generated flag-override files. Resolved by regeneration: ReactNativeFeatureFlags.config.js applied cleanly, the generated files were reset to the branch state, and scripts/featureflags/index.js regenerated them. The result matches the original commit exactly: same 7 files, 33 insertions, 13 deletions.
For the record: this moves useSharedAnimatedBackend and optimizedAnimatedPropUpdates to ossReleaseStage: canary, not stable, and both keep defaultValue: false. They are on in canary and nightly builds only. The shipped 0.89.0-rc.2 does not enable them.
Activity
[-][0.89] Promote the shared animation backend to stable[/-][+][0.89] Enable the shared animation backend in open source[/+]gabrieldonadel commentedon Nov 16, 2026
Picked into
0.89-stablefor 0.89.0-rc.2 ascd1c75ec5a3.The cherry-pick conflicted on two generated flag-override files. Resolved by regeneration:
ReactNativeFeatureFlags.config.jsapplied cleanly, the generated files were reset to the branch state, andscripts/featureflags/index.jsregenerated them. The result matches the original commit exactly: same 7 files, 33 insertions, 13 deletions.For the record: this moves
useSharedAnimatedBackendandoptimizedAnimatedPropUpdatestoossReleaseStage: canary, notstable, and both keepdefaultValue: false. They are on in canary and nightly builds only. The shipped 0.89.0-rc.2 does not enable them.