Skip to content

fix(macos): run useNativeDriver animations on the new architecture - #3145

Open
Bron Davies (brondavies) wants to merge 1 commit into
microsoft:mainfrom
brondavies:fix/turbo-animated-module-macos
Open

Bron Davies (brondavies) wants to merge 1 commit into
microsoft:mainfrom
brondavies:fix/turbo-animated-module-macos

Conversation

@brondavies

Copy link
Copy Markdown

Summary:

Fixes #3079.

shouldUseTurboAnimatedModule() picks NativeAnimatedTurboModule only when Platform.OS === 'ios'. On macOS under the new architecture, Animated falls back to NativeAnimatedModule, whose operation queue only the bridge flushes, so no useNativeDriver: true animation starts and its callback never fires.

Test Plan:

RNTester-macOS (Debug, arm64, Xcode 27.1, macOS 26.6.2), Playground running Animated.timing(opacity, {toValue: 1, duration: 300, useNativeDriver: true}) on an Animated.View:

  • On main, the view stays invisible and the start callback never fires.
  • With this change, it fades in and the callback reports finished: true.

@brondavies
Bron Davies (brondavies) requested a review from a team as a code owner October 23, 2026 18:33
@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

useNativeDriver: true animations never run on the New Architecture

1 participant