-
Notifications
You must be signed in to change notification settings - Fork 404
0.59.4 Discussion #113
Comments
Can we get facebook/react-native@6508b88 cherry-picked to remove the annoying |
facebook/react-native@60c0a60 fixes a bug where TextInput's caret position resets when toggling on/off the secureTextEntry prop. |
facebook/react-native@33b55cc Is a fix to calculate correct window dimensions for iOS (e.g. split view apps). Can this be cherrypicked? Thanks! |
facebook/react-native@f01c4e2 please! This will bring Android closer to iOS in terms of specifying |
facebook/react-native@c953e0b fixes a problem with Android JSStacktraces that causes apps to crash. Can this be added? Thanks! |
facebook/react-native@f149426 fixes several UIImplementation related crashes on Android |
There has been some regression where you are not able to have a full view (centered) as an empty view for a FlatList. This fixed it facebook/react-native#24339. Can we cherry pick it @grabbou ? :) |
@RuairiOliver already pulled as of 0.59.2 https://github.com/facebook/react-native/releases/tag/v0.59.2 Worth noting that I was all excited about that one myself but I found that for instance react-native-fs does not use the built-in react-native networking primitives so my library (which uses react-native-fs) was unable to take advantage of this and I still use the Google-Play-dependent Provider patch as a workaround 🤷♂️ |
Great stuff, thanks for that. Will check it out, I'm on 0.59.1 just now so hopefully it sorts my issue. |
Going to cut 0.59.5 tomorrow. Thanks for your participation. |
@kekenvunz, I didn't cherry-pick this commit. I need to test it with the CLI and @mikehardy, this commit is not part of 0.59.2 (at least that's what Git tells me). I am re-doing it myself (adding synchronised methods), because it can't be cherry-picked - it depends on a Yoga-related commit that I am not really sure whether I can import. |
Waiting for the tests now. Will keep you posted. |
@grabbou can you pick react sync? |
I might have confused things there. I had commented about a second commit to cherry pick but deleted that comment after Mike mentioned it was in 0.59.2. Looking forward to trying out 0.59.5, thanks! |
Correct - and no worries, my comment about 0.59.2 was about the new ability to include Conscrypt and react-native would use it if avaiable, for networking. I'm most excited about the JSStackTrace / NoSuchKey exception fix :-). Thanks @grabbou ! |
@mikehardy & @RuairiOliver - no worries, appreciate the explanation :) @ahce, React sync commits are usually hard to cherry-pick. I've followed up with Facebook team to check whether it's safe to do. |
Waiting for FB team to answer. Meanwhile, decided to do 0.59.5 w/o React sync. We will release 0.59.6 once we know it's safe and okay to do the bump. |
Up and running on 0.59.5, thanks @grabbou ! |
Conversation on this thread are limited to 0.59.4 release's major issues and cherry-pick requests from commits that are already on master.
An example of a good such request is a bug fix for a serious issue that has been merged into master but did not make the 0.59.4 cut.
In other words, if you cannot point to a particular commit on master, then your request likely belongs as a new issue in http://github.com/facebook/react-native/issues.
If the commit you request to cherry pick is a complicated port, you will be asked to create the PR to the 0.59-stable branch yourself, in order to ensure that the process proceeds smoothly.
The text was updated successfully, but these errors were encountered: