mirror of
https://github.com/hanzoai/insights-js.git
synced 2026-10-30 18:34:19 +00:00
Anna GarciaandGitHub
7e94fc558c
Xcode 26.4's Apple Clang 21 is stricter about consteval call sites, which rejects fmt's FMT_STRING usages and breaks pod install for the Expo 53 example. fmt's base.h redefines FMT_USE_CONSTEVAL based on compiler detection, so a -D flag in xcconfig isn't enough — patch the header in the post_install hook to force it off. See: - https://github.com/fmtlib/fmt/issues/4740 - https://github.com/facebook/react-native/issues/55601 - https://github.com/expo/expo/issues/44229
84 lines
3.3 KiB
Ruby
84 lines
3.3 KiB
Ruby
require File.join(File.dirname(`node --print "require.resolve('expo/package.json')"`), "scripts/autolinking")
|
|
require File.join(File.dirname(`node --print "require.resolve('react-native/package.json')"`), "scripts/react_native_pods")
|
|
|
|
require 'json'
|
|
podfile_properties = JSON.parse(File.read(File.join(__dir__, 'Podfile.properties.json'))) rescue {}
|
|
|
|
ENV['RCT_NEW_ARCH_ENABLED'] = '0' if podfile_properties['newArchEnabled'] == 'false'
|
|
ENV['EX_DEV_CLIENT_NETWORK_INSPECTOR'] = podfile_properties['EX_DEV_CLIENT_NETWORK_INSPECTOR']
|
|
|
|
platform :ios, podfile_properties['ios.deploymentTarget'] || '15.1'
|
|
install! 'cocoapods',
|
|
:deterministic_uuids => false
|
|
|
|
prepare_react_native_project!
|
|
|
|
target 'exampleexpo53' do
|
|
use_expo_modules!
|
|
|
|
if ENV['EXPO_USE_COMMUNITY_AUTOLINKING'] == '1'
|
|
config_command = ['node', '-e', "process.argv=['', '', 'config'];require('@react-native-community/cli').run()"];
|
|
else
|
|
config_command = [
|
|
'npx',
|
|
'expo-modules-autolinking',
|
|
'react-native-config',
|
|
'--json',
|
|
'--platform',
|
|
'ios'
|
|
]
|
|
end
|
|
|
|
config = use_native_modules!(config_command)
|
|
|
|
use_frameworks! :linkage => podfile_properties['ios.useFrameworks'].to_sym if podfile_properties['ios.useFrameworks']
|
|
use_frameworks! :linkage => ENV['USE_FRAMEWORKS'].to_sym if ENV['USE_FRAMEWORKS']
|
|
|
|
use_react_native!(
|
|
:path => config[:reactNativePath],
|
|
:hermes_enabled => podfile_properties['expo.jsEngine'] == nil || podfile_properties['expo.jsEngine'] == 'hermes',
|
|
# An absolute path to your application root.
|
|
:app_path => "#{Pod::Config.instance.installation_root}/..",
|
|
:privacy_file_aggregation_enabled => podfile_properties['apple.privacyManifestAggregationEnabled'] != 'false',
|
|
)
|
|
|
|
post_install do |installer|
|
|
react_native_post_install(
|
|
installer,
|
|
config[:reactNativePath],
|
|
:mac_catalyst_enabled => false,
|
|
:ccache_enabled => podfile_properties['apple.ccacheEnabled'] == 'true',
|
|
)
|
|
|
|
# This is necessary for Xcode 14, because it signs resource bundles by default
|
|
# when building for devices.
|
|
installer.target_installation_results.pod_target_installation_results
|
|
.each do |pod_name, target_installation_result|
|
|
target_installation_result.resource_bundle_targets.each do |resource_bundle_target|
|
|
resource_bundle_target.build_configurations.each do |config|
|
|
config.build_settings['CODE_SIGNING_ALLOWED'] = 'NO'
|
|
end
|
|
end
|
|
end
|
|
|
|
# Xcode 26.4+ Clang rejects fmt's FMT_STRING consteval. fmt's base.h redefines
|
|
# FMT_USE_CONSTEVAL based on compiler detection, so a -D flag is not enough —
|
|
# patch the header directly to force it off.
|
|
# Upstream:
|
|
# https://github.com/fmtlib/fmt/issues/4740
|
|
# https://github.com/facebook/react-native/issues/55601
|
|
# https://github.com/expo/expo/issues/44229
|
|
# Remove once RN/Expo pull in a fmt release that builds cleanly on Apple clang 21.
|
|
fmt_base_h = File.join(installer.sandbox.root, 'fmt', 'include', 'fmt', 'base.h')
|
|
if File.exist?(fmt_base_h)
|
|
contents = File.read(fmt_base_h)
|
|
patched = contents.gsub(/^(#\s*define FMT_USE_CONSTEVAL )1$/, '\10')
|
|
if patched != contents
|
|
File.chmod(0644, fmt_base_h)
|
|
File.write(fmt_base_h, patched)
|
|
Pod::UI.puts "Patched #{fmt_base_h} to disable FMT_USE_CONSTEVAL (Xcode 26.4 fix)"
|
|
end
|
|
end
|
|
end
|
|
end
|