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.88] Rebuild the content description when accessibilityValue is removed on Android #1538
On 0.88.1 Android, a view without accessibilityLabel that was once accessibilityState={{ busy: true }} is still announced as "busy" after it goes back to busy: false. TalkBack keeps reading the stale word instead of the view's text. BaseViewManager.updateViewContentDescription only sets the description when it is non-empty, so the old one stays.
#59540 (commit 25b05acd73) fixes this on main (and in 0.89.0-rc.2). I applied it to 0.88.1 and built React Native from source. It applies cleanly; the only change in BaseViewManager.java is a line offset. On a device (Redmi, Android 16, release APK) the stale "busy" is gone:
Case
0.88.1
0.88.1 + #59540
busy: true → busy: false, no label
"busy" stays
view text read
same with a label
label read
label read
Raw readings (content description of each view, Turkish TalkBack words: "meşgul" = busy)
0.88.1 busy=true after busy goes away
busy -> busy:false "meşgul" "meşgul" stuck
labelled busy->false "Labelled row, meşgul" "Labelled row" ok
0.88.1 + #59540 busy=true after busy goes away
busy -> busy:false "meşgul" "A · busy true → busy false" fixed
labelled busy->false "Labelled row, meşgul" "Labelled row" ok
Thank you for opening a new React Native Pick Request.
These are the criteria we follow when accepting or rejecting a code change into a React Native release branch (source).
If your Pick Request does not satisfy the criteria below, please close it as it will not be considered.
✅ Which Pick Requests we accept
✅ Fixes for regressions to core APIs. Examples:
A core component is behaving differently between versions 0.X and 0.X-1
The TurboModule.getEnforcing function is throwing an unexpected assertion error.
✅ Fixes to bugs in core React Native. Examples:
Breakpoints in React Native DevTools not working correctly in the debugger
Fast Refresh not working as expected
Metro bundler not starting properly or ignoring the configuration file
Buttons that are not clickable
✅ Fixes to APIs used by third-party libraries and out-of-tree platforms. Examples:
An API used by react-native-macos is not behaving as expected or is regressing
✅ Bump of patch version of dependencies. Example:
Bump Gradle from 8.11.0 to 8.11.1
✅ Fixes for low/high severity security vulnerabilities. Example:
Bump Gradle from 8.11.0 to 8.12.0 if there is a security vulnerability in 8.11 and no 8.11.x version contains the same fix.
✅ Fixes and reverts of accidental breaking changes. Example:
Reverting or fix-forwarding a Kotlin migration of a file (e.g. ReactRootView.java) if it is causing a breaking change for the React Native ecosystem.
✅ Performance improvements. Examples:
Fixing unnecessary re-renders in FlatList.
✅ Any Pick Request if the release is still in RC0 (after RC1, the previously listed criteria apply)
❌ Which Pick Requests we don't accept
❌ Any Pick Request that introduces a breaking change after RC1. Example:
A bugfix that contains a refactoring, resulting in changes to the public API of a class
❌ Any Pick Request that introduces a new feature after RC1. Example:
A commit that introduces a new API or a specific feature for a component.
❌ Bump of major or minor version of dependencies. Examples:
Bump Gradle from 8.11.0 to 8.12.0
Bump Gradle from 8.11.0 to 9.0.0
❌ Bump of a dependency to a pre-release version. Example:
Bump Gradle from 8.11.0 to 8.11.1-beta.1
❌ Any Pick Request that introduces changes to the React Native testing infrastructure after RC1. Examples:
Changes to GitHub Actions workflows to optimize them, even if they are on main.
Changes to the logic used to publish packages to NPM or Maven Central
❌ Pick Request composed of multiple commits that have several merge conflicts.
If your Pick Request is too complex to apply to the release branch, it will be rejected.
❌ Any non-critical improvement that landed on main.
These will generally ship in the following version unless they fit one of the criteria above.
❌ Any Pick Request considered a "nice to have".
Even one-line changes carry a risk of destabilizing and further delaying the release.
ℹ️ What makes for a good Pick Request
In order for your Pick Request to be considered, please do the following:
ℹ️ Limit your Pick Request to one commit from main, or one PR against the release branch.
ℹ️ Include a clear explanation of why your Pick Request should be considered, ideally referencing one of the criteria above.
ℹ️ Target only one minor version of React Native (e.g. [0.76]). To have your Pick Request applied to more versions, please open separate Pick Requests.
Activity
github-actions commentedon Nov 19, 2026
Thank you for opening a new React Native Pick Request.
These are the criteria we follow when accepting or rejecting a code change into a React Native release branch (source).
If your Pick Request does not satisfy the criteria below, please close it as it will not be considered.
✅ Which Pick Requests we accept
TurboModule.getEnforcingfunction is throwing an unexpected assertion error.react-native-macosis not behaving as expected or is regressingReactRootView.java) if it is causing a breaking change for the React Native ecosystem.❌ Which Pick Requests we don't accept
ℹ️ What makes for a good Pick Request
In order for your Pick Request to be considered, please do the following:
main, or one PR against the release branch.