From a694e3018b4335cbaa822fe4bac92817c0d49ce3 Mon Sep 17 00:00:00 2001 From: supun_yasantha034 Date: Tue, 6 Oct 2026 11:17:11 +0530 Subject: [PATCH] docs: clarify UIManager LayoutAnimation scope and New Architecture behavior --- docs/layoutanimation.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/layoutanimation.md b/docs/layoutanimation.md index b69454098f6..75860c9c6c9 100644 --- a/docs/layoutanimation.md +++ b/docs/layoutanimation.md @@ -7,7 +7,8 @@ Automatically animates views to their new positions when the next layout happens A common way to use this API is to call it before updating the state hook in functional components and calling `setState` in class components. -Note that in order to get this to work on **Android** you need to set the following flags via `UIManager`: +:::note +On **Android**, when using the **Legacy Architecture**, you need to enable layout animations via `UIManager`. This flag enables layout animations globally and only needs to be called once (for example, in your app's root entry file `index.js` or root component) before triggering any layout animation: ```js if (Platform.OS === 'android') { @@ -17,6 +18,9 @@ if (Platform.OS === 'android') { } ``` +On the **New Architecture**, layout animations are enabled automatically, and calling `setLayoutAnimationEnabledExperimental` is unnecessary (it is a no-op). +::: + ## Example ```SnackPlayer name=LayoutAnimation%20Example&supportedPlatforms=android,ios