I am attempting to implement an iOS SDK on an Expo React Native venture.
- expo: 51.0.28
- react-native: 0.74.5
In accordance with the SDK documentation, after linking the SDK on my venture’s iOS bundle I’ve so as to add its dependencies to the podfile archive. Like this:
pod 'SQLCipher', '~> 4.5.4' pod 'SQLCipher', '~> 4.5.4' pod 'JOSESwift', '~> 2.4.0' pod 'SwiftSignalRClient', '~> 0.9.3' pod 'CryptoSwift', '~> 1.7.1'
The construct on Xcode works advantageous. Nevertheless, when the app is launched on the simulator it will get frozen on the splash display screen an I get the message:
dyld[11724]: Library not loaded: @rpath/CryptoSwift.framework/CryptoSwift Motive: tried: '/Volumes/T7_SAMSUNG/xcode/derivedData/myApp-ehbzoyzucsxvdiajmbdvmaooidcr/Construct/Merchandise/Debug-iphonesimulator/CryptoSwift.framework/CryptoSwift' (no such file)
For some purpose it retains searching for CryptoSwift.framework file and that does not exist.
I can’t determine the origin of the error. After I pod set up I can see the libraries received put in appropriately. I might say cocoapods manages all of the dependencies by itself, however one thing is mistaken. It could possibly be the podfile configuration (generated by Expo framework):
require File.be part of(File.dirname(node --print "require.resolve('expo/bundle.json')"), "scripts/autolinking") require File.be part of(File.dirname(node --print "require.resolve('react-native/bundle.json')"`), "scripts/react_native_pods")
require 'json'podfile_properties = JSON.parse(File.learn(File.be part of(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']
use_autolinking_method_symbol = ('use' + '_native' + '_modules!').to_symorigin_autolinking_method = self.technique(use_autolinking_method_symbol)self.define_singleton_method(use_autolinking_method_symbol) do |*args|if ENV['EXPO_UNSTABLE_CORE_AUTOLINKING'] == '1'Pod::UI.places('Utilizing expo-modules-autolinking as core autolinking supply'.inexperienced)config_command = ['node','--no-warnings','--eval','require(require.resolve('expo-modules-autolinking', { paths: [require.resolve('expo/package.json')] }))(course of.argv.slice(1))','react-native-config','--json','--platform','ios']origin_autolinking_method.name(config_command)elseorigin_autolinking_method.name()finish
finish
platform :ios, podfile_properties['ios.deploymentTarget'] || '13.4'set up! 'cocoapods',:deterministic_uuids => false
prepare_react_native_project!
goal 'newexpoapp' douse_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']
pod 'SQLCipher', '~> 4.5.4'pod 'JOSESwift', '~> 2.4.0'pod 'SwiftSignalRClient', '~> 0.9.3'pod 'CryptoSwift', '~> 1.7.1'
use_react_native!(:path => config[:reactNativePath],:hermes_enabled => podfile_properties['expo.jsEngine'] == nil || podfile_properties['expo.jsEngine'] == 'hermes',# An absolute path to your utility root.:app_path => "#{Pod::Config.occasion.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',)
finish
finish
finish
finish
post_integrate do |installer| start expo_patch_react_imports!(installer) rescue => e Pod::UI.warn e finish finish finish
Does anybody have any thought what’s mistaken? Thanks!