![]() ![]() But for those looking for immediate relief, look into how often your components are re-rendering on text changes and try to eliminate/reduce that. Obviously it'd still be great to figure out the actual root cause of why this is only happening on Samsung devices. Since there's no state update.no re-render. We're using mobx as our data store and are simply updating the value in data store with onDataChanged, to be accessed when the form is submitted. ![]() This might be complex for some if you're doing something like updating state on the component onDataChanged. ![]() We refactored our component to remove Formik and make sure that zero re-renders happened while typing. Keyboard settings allow you to change languages, keyboard height and layout. Formik was causing double re-renders every time the user typed. When the keyboard is visible, select the Settings icon to access Keyboard settings. We've finally solved this issue for our app, the root cause was re-renders locking up the UI.Įchoing on this comment #35155 (comment), making the component fully uncontrolled makes a huge difference.įor us we had a class component using Formik, so memoizing wasn't possible. Snack, code example, screenshot, or link to a repository The app works properly when the user types.Xcode: 13.4.1/13F100 - /usr/bin/xcodebuildģ - Test release variant in a Samsung S22 with Android 13Ĥ - Start typing until you reach 3-4 lines of text. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |