V0.63.1 Discussion

[alloy]

⚠️ NOTE: v0.63.0 stable has not been released yet, but the changes it will include are final; so we have this issue ahead of time for people to already start tracking changes they need.

Conversations on this thread should be limited to reporting issues that are new in this minor version or requests to cherry-pick bug fixes that have landed in master.

In all other cases, please report the issue to http://github.com/facebook/react-native/issues.

Picks requested previously:

• facebook/react-native@449dc37
• facebook/react-native@9c32140
• facebook/react-native@f23fece
• facebook/react-native@f28c750
• facebook/react-native@4aaf629
• facebook/react-native@28dce36
• facebook/react-native@7757ad0
• facebook/react-native@9cdc19a
• facebook/react-native@a2f8b9c
• facebook/react-native@e5a6655

[mikehardy]

For anyone else like me realizing all of the sudden you need to convert .xib to .storyboard in relation to the above comments, I will say there are lots of ways to do it, all of which are fine I am sure. Very specifically though I can report not just success but a pleasant experience using https://github.com/zoontek/react-native-bootsplash - there are little Xcode screenshots of the manual parts you need to do and a CLI even. Great work @zoontek and @MoOx I think. So I am no longer concerned about iOS launch screens and am back to my default state of anticipation for 0.63 to release ;-)

[grabbou]

Thanks for cherry-picks. I will look at them later this week and we will begin working on v0.63.1.

[lorenzoangelini]

@grabbou on the 0.63 version, when in ios i launch a build in release mode, it seems that the absolute path cannot resolved, because research it into node_modules

[TheSavior]

Only commits that have landed to master can be considered for picks to a release branch. Open PRs can't be considered

[owinter86]

I personally did not have this issue in any previous RN versions, but its 100% reproducible in simulator and device on Version 0.63.

facebook/react-native#29021

[grabbou]

@lorenzoangelini, that sounds interesting. Can you link to an issue in the React Native repository where we can read more about it and follow this?

@owinter86, it has been reported in 0.61.5, so while you couldn't reproduce it on older versions yourself, it looks like the issue was there already.

[grabbou]

I have cherry-picked all commits listed here so far that were bug fixes. Please see the first comment for the whole list. I am now waiting for the CI to pass.

Since it's already quite late here in Europe, I'll postpone the final release for tomorrow.

[lorenzoangelini]

@grabbou there is a similar issue here
[https://github.com/react-native-community/upgrade-support/issues/87]

[grabbou]

I see. Thanks for reporting. Let's keep tracking it there on inside React Native. I was afraid that this was some high-profile CLI related issue. Fortunately though, seems like a Babel/bundler-related issue.

[grabbou]

0.63.1 will be out soon, closing this issue.