[Gutenberg] Apply workaround in gutenberg_post_install
to address build failure
#22658
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This workaround solves the issue related to redefining
clockid_t
in the podRCT-Folly
when using a local bundle. The issue was introduced when upgrading the React Native version to 0.71.15 in this PR, which includes further information about the workaround.To test:
gutenberg-mobile
at the same level as the folder where WordPress-iOS repository is located.rm -rf build && LOCAL_GUTENBERG=1 bundle exec pod install
Regression Notes
Potential unintended areas of impact
N/A
What I did to test those areas of impact (or what existing automated tests I relied on)
N/A
What automated tests I added (or what prevented me from doing so)
N/A
PR submission checklist:
RELEASE-NOTES.txt
if necessary.Testing checklist: