[0.84] Fix crash in tracking spring animations when toValue node is detached

Open
#1,242 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
android, react-native
Domain
mobile

Research direction

Start with commit 45de7109fe93db8052e9ba06e53807f89cbd7fd9 and trace the Android Native Animated spring path involved in detached toValue nodes. Review the regression test added there and run it. Done means teardown no longer propagates a null toValue into the spring configuration and the regression test passes.

Written by the indexing model from the issue text.

Description

Type Pick Request
Target Branch

0.84

Link to commit or PR to be picked

https://github.com/facebook/react-native/commit/45de7109fe93db8052e9ba06e53807f89cbd7fd9

Description

This fixes an Android Native Animated crash in a core animation path.
During teardown (unmount/re-render/navigation), a tracked toValue node can be detached and RN may pass toValue = null into spring config, causing NullPointerException.

This change prevents null propagation and adds a regression test. It is a single, low-risk fix with no reliable app-level workaround.

Dominant language
No language data
Stars
428
Forks
11
Avg merge
13m
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from reactwg/react-native-releases

All issues in reactwg/react-native-releases

Similar issues

More Mobile Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.