v0.62.2 Discussion

[alloy]

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.

[SaeedZhiany]

Can we cherry-pick this?
facebook/react-native@7980615

[sunnylqm]

facebook/react-native@449dc37

[guhungry]

Fix app crash due to flipper 0.33.1 in ios debug build when use base64 image facebook/react-native@17f025b

[christianbach]

Could we pick this?
facebook/react-native@7deeec7

For context:
react-native-community/cli#939
react-native-community/upgrade-support#26 (comment)

[ahce]

Can pick this?
facebook/react-native@28dce36
facebook/react-native@7757ad0

[zhongwuzw]

Could we pick this facebook/react-native@9cdc19a?

[chris-griffin]

Can we pick facebook/react-native@a2f8b9c which fixes an incorrect white text color being applied on TextInputs when an iOS device is set to dark mode even if the background of the input is white as well?

[glibenko]

Important info if you use Hermes
I updated from 61.5 to 62.2 and got a crash on android:
couldn't find DSO to load: libhermes-executor-debug.so

I fixed it by adding following string to android/app/build.gradle:
implementation "org.webkit:android-jsc:+"

[JLucasCAmorim]

Can we pick facebook/react-native@e5a6655 which fixes the Animated image crash when CADisplayLink target in RCTWeakProxy is nil?

[jakobvase]

Can we pick facebook/react-native@33b3a1a? Changes the launch screen from .xib to .storyboard, as required by Apple before June 30th (https://developer.apple.com/news/?id=03262020b).

[SaeedZhiany]

@alloy
Are all the requested cherry-picks in this issue included in 0.63.x? If yes, we can close this issue right? otherwise, I'm wondering which version will include those cherry picks?

Thanks.

[chris-griffin]

I would definitely love to see these cherry-picks added to a new 62.2.3 release. This seems necessary especially given #188 (comment) (which will break things starting tomorrow). But in general, we would be very grateful to see additional stability in releases by backporting fixes to the previous major/minor patch.

[radko93]

@chris-griffin this only affects new projects, if you have an existing project you need to migrate to a storyboard manually anyway. But it has to be included in 0.63.

[kelset]

echoing what @radko93 just said, cherry picking the commit won't autofix/autoupdate any already existing app. That change needs to be done manually anyway, so in all fairness since we are releasing 0.63.0 very soon I don't think it's necessary to release 0.62.3 (since it won't come out before 0.63 anyway and react-native init will use 0.63).

[sunnylqm]

Any chance for facebook/react-native@0a6f058#diff-5df8978d901ea853da66f065feee64ab which fixes facebook/react-native#25923 (comment)

[alloy]

Thanks for bearing with us and reporting issues/requests for picks 🙏 Due to available bandwidth, we decided to focus on getting a v0.63.0 release out rather than another v0.62.x patch release. I’ve gone through all the requested picks and have added those that are not yet slated for v0.63.0 to be picked for v0.63.1: #199