TakayukiCho
commented
3 weeks ago Hi.
Cloud you take a look at this page for troubleshooting Privacy manifest support of KARTE SDK?
If following the steps in the document doesn't work, let us know.
Open shenyingyin opened 4 weeks ago
TakayukiCho
commented
3 weeks ago Hi.
Cloud you take a look at this page for troubleshooting Privacy manifest support of KARTE SDK?
If following the steps in the document doesn't work, let us know.
shenyingyin
commented
3 weeks ago @TakayukiCho
Hi.
Cloud you take a look at this page for troubleshooting Privacy manifest support of KARTE SDK?
If following the steps in the document doesn't work, let us know.
Hi. Thank you for your advise.
Here's what my Podfile and Podfile.properties.json look like.
Podfile:
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'] = podfile_properties['newArchEnabled'] == 'true' ? '1' : '0'
ENV['EX_DEV_CLIENT_NETWORK_INSPECTOR'] = podfile_properties['EX_DEV_CLIENT_NETWORK_INSPECTOR']
platform :ios, podfile_properties['ios.deploymentTarget'] || '13.0'
install! 'cocoapods',
:deterministic_uuids => false
prepare_react_native_project!
# If you are using a `react-native-flipper` your iOS build will fail when `NO_FLIPPER=1` is set.
# because `react-native-flipper` depends on (FlipperKit,...), which will be excluded. To fix this,
# you can also exclude `react-native-flipper` in `react-native.config.js`
#
# ```js
# module.exports = {
# dependencies: {
# ...(process.env.NO_FLIPPER ? { 'react-native-flipper': { platforms: { ios: null } } } : {}),
# }
# }
# ```
flipper_config = FlipperConfiguration.disabled
if ENV['NO_FLIPPER'] == '1' then
# Explicitly disabled through environment variables
flipper_config = FlipperConfiguration.disabled
elsif podfile_properties.key?('ios.flipper') then
# Configure Flipper in Podfile.properties.json
if podfile_properties['ios.flipper'] == 'true' then
flipper_config = FlipperConfiguration.enabled(["Debug", "Release"])
elsif podfile_properties['ios.flipper'] != 'false' then
flipper_config = FlipperConfiguration.enabled(["Debug", "Release"], { 'Flipper' => podfile_properties['ios.flipper'] })
end
end
target 'DevRN' do
use_expo_modules!
config = use_native_modules!
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']
# Flags change depending on the env values.
flags = get_default_flags()
use_react_native!(
:path => config[:reactNativePath],
:hermes_enabled => podfile_properties['expo.jsEngine'] == nil || podfile_properties['expo.jsEngine'] == 'hermes',
:fabric_enabled => flags[:fabric_enabled],
# An absolute path to your application root.
:app_path => "#{Pod::Config.instance.installation_root}/..",
# Note that if you have use_frameworks! enabled, Flipper will not work if enabled
:flipper_configuration => flipper_config
)
post_install do |installer|
react_native_post_install(
installer,
config[:reactNativePath],
:mac_catalyst_enabled => false
)
__apply_Xcode_12_5_M1_post_install_workaround(installer)
# 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
end
post_integrate do |installer|
begin
expo_patch_react_imports!(installer)
rescue => e
Pod::UI.warn e
end
end
end
Podfile.properties.json:
{
"expo.jsEngine": "hermes",
"EX_DEV_CLIENT_NETWORK_INSPECTOR": "true",
"ios.deploymentTarget": "15.0",
"ios.useFrameworks": "static"
}I assume the deployment target is correctly configured to 15.0 according to the value of ios.deploymentTarget.
Unfortunately after trying following steps which are provided in the troubleshooting page,
I can see the Minimum Deployments of RNKRTCore still sets to 11.0 from Xocde.
pod update KarteCore inside ios directorypod update KarteUtilities before pod update KarteCore inside ios directorypod repo update and then run pod update KarteCore againTakayukiCho
commented
2 weeks ago @shenyingyin
We tried to reproducte your situation, but haven't made it yet.
Could you submit the form here for reaching out with our support team?
Our project is using Karte SDK with Expo plugin and getting following error when build from Xcode due to incompatible deployment target issue.
KarteCore > iOS12.0 RNKRTCore > iOS11.0 RNKRTInAppMessaging > iOS11.0 RNKRTNotification > iOS11.0
Local workaround is manually changing deployment target one by one. But won't resolve the problem while using CI/CD.
Please kindly take a look into this.