Closed abz-denys-z closed 1 year ago
valentynhalkinreteno
commented
1 year ago Hello @abz-denys-z
Thank you for contacting.
I've created test project with your dependencies from package.json, and for now I can not reproduce your issue.
Could you please help me a little bit here:
Bundle React Native code and images or something else?
abz-denys-z
commented
1 year ago Can you please provide your Podfile dependencies in comments?
require_relative '../node_modules/react-native/scripts/react_native_pods'
require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'
platform :ios, '12.4'
install! 'cocoapods', :deterministic_uuids => false
use_frameworks! :linkage => :static
target 'matin_target' do
config = use_native_modules!
# Flags change depending on the env values.
flags = get_default_flags()
pod 'Firebase', :modular_headers => true
pod 'FirebaseCore', :modular_headers => true
pod 'GoogleUtilities', :modular_headers => true
pod 'Reteno', '1.3.0'
$RNFirebaseAsStaticFramework = true
use_react_native!(
:path => config[:reactNativePath],
# Hermes is now enabled by default. Disable by setting this flag to false.
# Upcoming versions of React Native may rely on get_default_flags(), but
# we make it explicit here to aid in the React Native upgrade process.
:hermes_enabled => true,
:fabric_enabled => flags[:fabric_enabled],
# Enables Flipper.
#
# Note that if you have use_frameworks! enabled, Flipper will not work and
# you should disable the next line.
# :flipper_configuration => FlipperConfiguration.enabled(["Debug"]),
# An absolute path to your application root.
:app_path => "#{Pod::Config.instance.installation_root}/.."
)
pod 'react-native-splash-screen', :path => '../node_modules/react-native-splash-screen'
target 'targetTests' do
inherit! :complete
# Pods for testing
end
# use_flipper!({ 'Flipper' => '0.125.0', 'Flipper-Folly' => '2.6.10', 'Flipper-RSocket' => '1.4.3' })
post_install do |installer|
react_native_post_install(
installer,
# Set `mac_catalyst_enabled` to `true` in order to apply patches
# necessary for Mac Catalyst builds
:mac_catalyst_enabled => false
)
installer.pods_project.targets.each do |target|
target.build_configurations.each do |config|
config.build_settings['APPLICATION_EXTENSION_API_ONLY'] = 'NO'
# config.build_settings['ONLY_ACTIVE_ARCH'] = 'YES'
# config.build_settings['SDKROOT'] = 'iphoneos'
# config.build_settings["EXCLUDED_ARCHS[sdk=iphonesimulator*]"] = "arm64"
end
end
__apply_Xcode_12_5_M1_post_install_workaround(installer)
end
end
target 'share' do
use_react_native!(:hermes_enabled => true)
pod 'RNShareMenu', :path => '../node_modules/react-native-share-menu'
# Manually link packages here to keep your extension bundle size minimal
end
target 'notificationsReteno' do
pod 'Reteno', '1.3.0'
endOn which phase script do you have this PhaseScriptExecution error? Is it Bundle React Native code and images or something else?
If I understand correctly, I can check here (https://scr.abz.agency/8Lug0Lnk) If so, the same state for the Run command
@valentynhalkinreteno I hope this helps you to reproduce my mistake too
abz-denys-z
commented
1 year ago @valentynhalkinreteno Also perhaps useful, I went by the documentation name AppDelegate.mm
abz-denys-z
commented
1 year ago Found the cause, the problem was in Sentry They fixed the bug in 5.0.0-alpha.10, but after conflicts we had to downgrade the version (wrote above), which caused the problem to appear again
Or update the shellScript
@valentynhalkinreteno Thank you for your time
Description During integration an error occurred with Sentry(https://scr.abz.agency/6quNZwqp) because two libraries were installed after the pod install command After that we downgraded Sentry (React Native) and the conflicts disappeared
At the moment there is an error with launching the script Tried to get rid of it this way:
Version: 1.0.0 Output of
npx react-native infoСode example, Screenshot