Repository navigation
0.83 regressions (TextInput, Text) #55059
Description
Activity
- addedComponent: TextInputRelated to the TextInput component.Related to the TextInput component.Impact: RegressionDescribes a behavior that used to work on a prior release, but stopped working recently.Describes a behavior that used to work on a prior release, but stopped working recently.
on Jan 6, 2026 And yes, on iOS for Text if numeric value specified, for example 200 or 300, text will always be bold.
If I specify "normal" string prop, it works as expected.Seems like another regression issue on Text component
The same in my project. If I use autoFocus for an input, after
onFocus- immediatelyonBluris triggering.Reacted by Oleksandr Dziuban, Nakshatra Singh, Christophe Menager, Filip Hoško and Shane SaundersReacted by Oleksandr Dziuban and Filip Hoško- addedIssue: Author Provided ReproThis issue can be reproduced in Snack or an attached project.This issue can be reproduced in Snack or an attached project.and removed
on Jan 9, 2026 Thank you for reporting the issue. I simulated it here, without expo and in the latest version as well (0.84.0-rc.0).
Reacted by bigcupcoffee, Nakshatra Singh and Oleksandr DziubanCan we have a quick patch like v0.83.2 with the regression issue fix for Input component?
RN Team, could you please check that regression issues for TextInput? Seems like a blocker for migration to RN v0.83.0
CC: @migueldaipre are you be able to repro autoFocus issue as well?
Thanks a lot guys
Is there an update to these breaking bugs? Thank you
Reacted by Nakshatra Singh, Erick Bazán, Oleksandr Dziuban and aleguern-azivko- added 2 commits that reference this issue
on Mar 13, 2026 This workaround seems to be working for now
<TextInput + key={value} value={value} editable={false} />@ShanavasPS don’t do that, it’s a terrible anti-pattern
Reacted by Shanavas Shaji@efstathiosntonas Thanks for the response. Is there is a better workaround or a fix for this?
Sorry to ping you @cortinico @cipolleschi but can we have some eyes on TextInput components 🥺? Controlled are usually laggy and can't handle cursor properly when typing faster, switching to uncontrolled makes them not grow anymore, it's barely functioning outside of basic cases and feels like we need to add workaround after workaround since 0.8x
For those looking for (yet another) workaround - I've found that double updating the TextInput helps, can be achieved via
setNativeProps({ text: newState })for example. So either add that right next to your setState, which will update it twice, or even just calling setNativeProps twice (with sametext) works, it's somewhat acceptable workaround for the specific case, but for some frequent updates, e.g. from user input, I'd probably refrain from this oneReacted by Elmo Tanu Miharja, Givi Tkemaladze and Tao ZengSorry to ping you @cortinico @cipolleschi but can we have some eyes on TextInput components 🥺? Controlled are usually laggy and can't handle cursor properly when typing faster, switching to uncontrolled makes them not grow anymore, it's barely functioning outside of basic cases and feels like we need to add workaround after workaround since 0.8x
For those looking for (yet another) workaround - I've found that double updating the TextInput helps, can be achieved via
setNativeProps({ text: newState })for example. So either add that right next to your setState, which will update it twice, or even just calling setNativeProps twice (with sametext) works, it's somewhat acceptable workaround for the specific case, but for some frequent updates, e.g. from user input, I'd probably refrain from this oneThanks. the setNativeProps solution works for now
Greetings. Any updates regarding this issue? Would RN team tackle it in future releases.
We do have a workaround with an adding a hidden text to calculate the width and put it for the original input, but it looks like a hardcoded fix and I would prefer to have a proper solution from the RN :) Or to whom should I address this question.
Thanks a lot.
Is this still an issue in React Native v0.87.x?
Description
I've noticed at least 2 regressions with 0.83
❗[attached video below] TextInput layout change issues: changing
valueonTextInputdoesn't seem to update layout correctly and reposition the views around it. We mainly noticed it when usingTextInputto vertically align the phone number prefix text (+1) with real inputLess important but still,
fontWeighton iOS kinda snaps between Bold/Normal, completely ignoring values like 500 600. I noticed #54976 which seems to address this issue but I'm not 100% confident if that's the cause. Wanted to highlight it while I get the chanceSteps to reproduce
BrokenLayoutOnInputChangescomponent from the repro snack to the App.tsx and render itTextInputvalue between+1and+52to see that it layouts it incorrectlyReact Native Version
0.83.1
Affected Platforms
Runtime - iOS
Output of
npx @react-native-community/cli infoStacktrace or Logs
MANDATORY Reproducer
https://snack.expo.dev/@bigcupcoffee/broken-input-layout-repro
Screenshots and Videos
0.82.1 (working fine):
82.mp4
0.83.1 (not working fine):
83.mp4