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
Text component cuts part of the text if fontWeight bold is used #21729
In some devices when using a component with the syle fontWeight: 'bold'it removes the last word of the content of the text. My guess is that it's related with the latest android version, I could test and reproduce this bug in the OnePlus 6 device.
See how the hello world app renders with/without the font style bold.
Before adding bold style to text
After adding bold style to text
Reproducible Demo
1. react-native init bug
2. Connect an android device OnePlus 6 with latest version of android on the computer
3. Add `fontWeight: 'bold',` to App.js line 45 (instructions styles)
4. Run the app in the device
Reacted by Michał Matyas, MewX, Pham Dinh Vinh, Sreekesh, Ankur Gupta, Marko Troskot, hejun041, Valentin Hervieu, Giridhar, Rohit Rathi and 12 more
Reacted by atalon-kn, Anthony Wentzel and crafts69.guy
It looks like you are using an older version of React Native. Please update to the latest release, v0.57 and verify if the issue still exists.
The ":rewind:Old Version" label will be removed automatically once you edit your original post with the results of running react-native info on a project using the latest release.
I also use a OnePlus and I had this issue. A workaround I used is to set fontFamily to 'Roboto'
Reacted by Pranav vij, Jhamali, Petar Todorovic, Sreekesh, Vilfred (Will), Mudit Dangi, Arpan Sharma, Samuel Zeleke, Harshad M, Shubham Rana and 5 more
Reacted by Vinícius Lucas and David Florencio Dos Santos Junior
Any real solution to this problem? I've noticed using react-native-element's text component doesn't yield the same issue. Anyone had success with updating to a newer version?
(In my case I added a space at the end of my string and it worked, but that's not really a viable solution)
Still experiencing this in 2024. I noted that <Text> appears to remove the end node of each text string.
This works for some cases for me. In one case: like const category = ['Course Project ', 'Course Study ', 'ExtraCurricular ']; {category.map((item, index) => {
return (
{item}
);
})} you need to add space in both category and behind {item} so that you word will not be chopped off
Activity
react-native-bot commentedon Oct 11, 2018
It looks like you are using an older version of React Native. Please update to the latest release, v0.57 and verify if the issue still exists.
The ":rewind:Old Version" label will be removed automatically once you edit your original post with the results of running
react-native infoon a project using the latest release.kunal886496 commentedon Oct 20, 2018
This still exists. Any solution?
kunal886496 commentedon Oct 20, 2018
This is the config:
"babylon": "^6.18.0",
"react": "16.4.1",
"react-actioncable-provider": "^1.0.3",
"react-native": "0.57.0",
"react-native-android-keyboard-adjust": "^1.1.1",
"react-native-fs": "^2.11.15",
"react-native-image-picker": "^0.26.10",
"react-native-image-resizer": "^1.0.0",
"react-native-keyboard-aware-scrollview": "^2.0.0",
"react-native-loader": "^1.2.1",
"react-native-material-design": "^0.3.7",
"react-native-material-ui": "^1.30.1",
"react-native-photo-upload": "^1.2.0",
"react-native-push-notification": "^3.1.1",
"react-native-sound": "^0.10.9",
"react-native-vector-icons": "^5.0.0",
"react-native-websocket": "^1.0.2",
"react-redux": "^5.0.7",
"react-router-native": "^4.3.0",
"redux": "^4.0.0",
"redux-thunk": "^2.3.0",
"socket.io-client": "^2.1.1"
vitorreis commentedon Oct 20, 2018
No solution so far, I've workarounded it by removing the font bold style.
kunal886496 commentedon Oct 20, 2018
This is surprising.
ps2qwert commentedon Dec 4, 2018
I set the width to solve the problem
SanchezQb commentedon Dec 12, 2018
I also use a OnePlus and I had this issue. A workaround I used is to set fontFamily to 'Roboto'
faridhub95 commentedon Dec 19, 2018
I'm using oneplus 3t can confirm, the bug is still there even when using recent react version
adititipnis commentedon Jan 11, 2019
One plus 6t.. same issue.
This works though.
I've seen something similar happen on my Instagram as well! Now I see why...
31 remaining items
cglacet commentedon Nov 3, 2021
Any real solution to this problem? I've noticed using react-native-element's text component doesn't yield the same issue. Anyone had success with updating to a newer version?
(In my case I added a space at the end of my string and it worked, but that's not really a viable solution)
Merge 0.66 into master (#951)
Upgrade from 0.66.0 to 0.66.4 (#977)
emaborsa commentedon Jan 23, 2023
Still have the problem.
Mihai-github commentedon Jul 29, 2023
+1
chavanRk commentedon Dec 6, 2023
fontWeight : 500,700 is not working
fontStyle : 'Nunito-Bold' is also not working
Is it because of other dependency or what?
derekblank commentedon Jan 12, 2024
Still experiencing this in 2024. I noted that
<Text>appears to remove the end node of each text string.When there are two or more words in one
<Text>element, the last word is removed:When there is one word in a
<Text>element, the last letter is removed:When there are two or more words in one
<Text>element and a space is added, the space is removed:In our case, adding a space at the end of the string was a suitable workaround.
fix: Add space to text string to workaround RN text display bug
fix: Add space to text string to workaround RN text display bug (#57783)
moksaiho commentedon Apr 25, 2024
This works for some cases for me. In one case: like const category = ['Course Project ', 'Course Study ', 'ExtraCurricular ']; {category.map((item, index) => {
return (
{item}
);
})} you need to add space in both category and behind {item} so that you word will not be chopped off
amandaoneal commentedon Jul 22, 2025
Still experiencing this in 2025. This is pretty ridiculous.
agonsgd commentedon Sep 17, 2025
This is what worked for me, adding a
{" "}robgraeber commentedon Jun 26, 2026
Confirm this is still an issue as of RN 0.85.3. The extra space workaround seems to work well.
daaugusto commentedon Jul 28, 2026
+1 This issue should be reopened because the problem still persists.