-
Notifications
You must be signed in to change notification settings - Fork 404
V0.63.2 Discussion #200
Comments
Campeon @grabbou! This one just landed and makes it so the default new app template doesn't crash everything Android<API21 facebook/react-native@7694b32 |
Based on this comment by @JoshuaGross here are 3 more commits: |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This issue is to track cherry-pick requests - a valid request is the commit hash of a change that has landed on master. It is not for tracking open issues. If you can point to the commit hash in the react-native repo of a landed commit, it can be requested here |
Can we do this, it will help fix this -> |
This comment has been minimized.
This comment has been minimized.
@lorenzoangelini as explained by @mikehardy a few comments above:
Please open an issue to report the issue in the main repo. This conversation is for requesting commits that can be cherry picked. |
Can we cherry-pick facebook/react-native@23036b3? This fixes facebook/react-native#29397. tl;dr is that without this, Android apps that specify |
Can we cherry pick facebook/react-native@123423c? This fixes showing images on IOS 14. |
That would be great. We are also experiencing this. |
All commits cherry-picked. No more requests for this release. We're doing tests right now. |
Conversations on this thread are limited to 0.63 releases major issues and backport (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.63.1 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.
The text was updated successfully, but these errors were encountered: