-
Notifications
You must be signed in to change notification settings - Fork 25.1k
Last Character Randomly Missing in <Text> Component #53017
Copy link
Copy link
Closed as duplicate of#50916
Labels
Needs: AttentionIssues where the author has responded to feedback.Issues where the author has responded to feedback.Needs: ReproThis issue could be improved with a clear list of steps to reproduce the issue.This issue could be improved with a clear list of steps to reproduce the issue.Type: New ArchitectureIssues and PRs related to new architecture (Fabric/Turbo Modules)Issues and PRs related to new architecture (Fabric/Turbo Modules)
Metadata
Metadata
Assignees
Labels
Needs: AttentionIssues where the author has responded to feedback.Issues where the author has responded to feedback.Needs: ReproThis issue could be improved with a clear list of steps to reproduce the issue.This issue could be improved with a clear list of steps to reproduce the issue.Type: New ArchitectureIssues and PRs related to new architecture (Fabric/Turbo Modules)Issues and PRs related to new architecture (Fabric/Turbo Modules)
Type
Fields
Give feedbackNo fields configured for issues without a type.
Description
On React Native 0.78.0 with react 19.0.0, we've encountered an intermittent issue where the last character inside a component is not rendered on some Android devices. This only happens occasionally and is hard to consistently reproduce.
Steps to reproduce
Users using Xiaomi and OPPO devices occasionally encounter the text clipping issue (last character missing) upon initial app startup.
During my own debugging, I was able to reproduce the issue more reliably by changing the system font size or weight in Android settings. After adjusting the font settings and returning to the app, the last character of a component sometimes disappears.
React Native Version
0.78.0
Affected Platforms
Runtime - Android
Areas
Fabric - The New Renderer
Output of
npx @react-native-community/cli infoStacktrace or Logs
MANDATORY Reproducer
Screenshots and Videos
No response