Upcoming v0.63.5 cherrypicks discussion about releases HOT 23 CLOSED

@kelset I'll see if I can do that then: facebook/react-native#30688
So far it's working properly on our internal test case

from releases.

@anchi20: Please read the first post:

Conversations on this thread are limited to 0.64 releases major issues and backport (cherry-pick) requests from commits that are already on master.

Please let us know when your PR has landed on master.

from releases.

update: it's not likely we'll do a 0.63.5 patch, but since the Xcode 12.5 issue is fairly big it could be the case. We are still waiting for a commit to land in master, but I've started to update the top post with the list of commits we should cherry pick.

from releases.

I am going to cherry-pick the aforementioned commit and test whether it fixes the issue on this branch as well, as a part of my testing of the same commit for the 0.64 branch!

from releases.

When facebook/react-native#30543 lands, we will need to cherry-pick it to this branch too. It is affecting users on older React Native versions as well that upgraded to latest Xcode.

Edit: there it is: facebook/react-native@fdcacd7

from releases.

This should also be cherry-picked facebook/react-native#30592 to avoid adding a whole new post install hook to a Podfile.

from releases.

Really wait for these changes facebook/react-native@b7b0e23

To have an opportunity to get tap location on the <TextInput/> component

from releases.

Just a reminder, please use the latest Flipper pod, as we have solved the issues related to Apple M1 machines and arm compatibilities. Latest Flipper pod is 0.75.1

from releases.

@retyui that commit adds new functionality so it's not a candidate for a patch release.

from releases.

@sandfox I've already attempted cherry-picking it during the last round, but it's really complicated because the files involved changed a lot - so it's not achievable. The only option would be for someone to do a PR against the 0.63 branch with the fix "repurposed" to work on it.

from releases.

@priteshrnandgaonkar a bit off-topic, but does the latest Flipper pod also fix facebook/react-native#30836?

from releases.

potential cherry pick: facebook/react-native@3399896

from releases.

p.s. @kelset seem you recommend a legacy ruby syntax

-use_flipper!('Flipper' => '0.75.1')
+use_flipper!({ 'Flipper' => '0.75.1' })

from releases.

@todorone if you are on 0.63 you only need to tweak your podfile to address the Xcode 12.5 issue, see details here: facebook/react-native#31480

from releases.

Could we backport in facebook/react-native@d85d5d2 from facebook/react-native#29882
It's a fix for Modal onDismiss behaviour. It's already in 0.64

from releases.

@mrousavy from the comments in the issue seems like it did. In my experience, you can just change your podfile to

use_flipper!('Flipper' => '0.75.1')

To change the Flipper version

from releases.

Still waiting for a fix for Modal::onDismiss on iOS facebook/react-native@d85d5d2

from releases.

We are getting closer to 0.64.0 so atm we are fully focused on that - no ETA for a new patch for 0.63.x.

from releases.

@retyui - there's an open (mine) PR for it facebook/react-native#30688 that can be used if 0.63.5 gets the go ahead (assuming poeple are ok with merging it of course).

from releases.

potentially useful to consider: facebook/react-native@0e9296b

from releases.

here, facebook/react-native#29070

from releases.

@kelset Not everybody can migrate to 0.64 yet, so releasing a fix to XCode 12.5 will be a lifesaver... 🥺

from releases.

Given how the update for Xcode 12.5 didn't require an update for 0.63, I'm going to close this off. We are currently focused on 0.64 and 0.65 so there won't be new 0.63 releases for the time being.

from releases.