You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are currently using a patch in our Podfile named __apply_Xcode_12_5_M1_post_install_workaround which set the IPHONEOS_DEPLOYMENT_TARGET to 11 for all Pods using a lower target. Unfortunately for my latest Xcode Version 14.3 on M1 architecture the build fails with missing 'butter/map.h' file not found until I set the Pods target to 12 at minimum.
I changed the file node_modules/react-native/scripts/react_native_pods.rb containing the patch to this code (just exchanging 11 to 12) - I have not yet found a good way to persist this change for our repository:
...
def__apply_Xcode_12_5_M1_post_install_workaround(installer)# Flipper podspecs are still targeting an older iOS deployment target, and may cause an error like:# "error: thread-local storage is not supported for the current target"# The most reliable known workaround is to bump iOS deployment target to match react-native (iOS 11 now).installer.pods_project.targets.eachdo |target|
target.build_configurations.eachdo |config|
# ensure IPHONEOS_DEPLOYMENT_TARGET is at least 12.0deployment_target=config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'].to_fshould_upgrade=deployment_target < 12.0 && deployment_target != 0.0ifshould_upgradeconfig.build_settings['IPHONEOS_DEPLOYMENT_TARGET']='12.0'endendend
...
The text was updated successfully, but these errors were encountered:
We are currently using a patch in our
Podfile
named__apply_Xcode_12_5_M1_post_install_workaround
which set theIPHONEOS_DEPLOYMENT_TARGET
to 11 for all Pods using a lower target. Unfortunately for my latest Xcode Version 14.3 on M1 architecture the build fails with missing'butter/map.h' file not found
until I set the Pods target to 12 at minimum.I changed the file
node_modules/react-native/scripts/react_native_pods.rb
containing the patch to this code (just exchanging 11 to 12) - I have not yet found a good way to persist this change for our repository:The text was updated successfully, but these errors were encountered: