Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix: OSS builds can accidentally using coreutils cp (#44097)
Summary: Pull Request resolved: #44097 There are two places where we use a feature specific to the system version of 'cp', the: -X Do not copy Extended Attributes (EAs) or resource forks. This feature isn't available in GNU's cp, which is commonly installed on macOS using: brew install coreutils && brew link coreutils We can avoid the problem alltogether by being specific about the path of the system cp. Changelog: [General][Fixed] don't break script phase and codegen when coreutils installed on macOS Reviewed By: cipolleschi Differential Revision: D56143216 fbshipit-source-id: f1c1ef9ea2f01614d6d89c4e9eedf43113deb80c
- Loading branch information
e079953
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Possible Solutions for React Native Upgrade Issue
If you're encountering issues after upgrading React Native from version
0.72.x
to0.73.x
or0.74.x
, please consider the following solutions:Quick Solution: Remove the
.xcode.env.local
file located atapp/ios/.xcode.env.local
and attempt to run the project again. The reason for this is that the React Native upgrade helper does not include this file, which might be causing conflicts.Additional Information: A fix for this issue is mentioned in this GitHub thread. The fix is expected to be included in React Native version 0.74.4, which should be available soon.
I hope these steps help resolve the issue.