Specs satisfying the `RNCAsyncStorage (from `../node_modules/#react-native-async-storage/async-storage`)` dependency were found, but they required a higher minimum deployment target.
I have changed the deployment target to 10.15 from xcode, but I still get this
The RNCAsyncStorage's min deployment target is 9.0.
Change the line in podfile to 9 or later. And I suggest marking it to 11
platform :ios, '9.0'
Related
I'm trying to add react-native-vision-camera to my React Native app, and it gave me the following error:
Specs satisfying the VisionCamera (from ../node_modules/react-native-vision-camera) dependency were found, but they required a higher minimum deployment target.
In my podfile I have platform :ios, '10.0'. Is there a way to find the minimum deployment target that this library requires? And is there ever a disadvantage to increasing the minimum deployment target?
If you look at the Podfile in the example project of the repo, the minimum deployment target is iOS 11.
https://github.com/mrousavy/react-native-vision-camera/blob/main/example/ios/Podfile
The disadvantage of increasing the minimum target is that your app won't work on devices that can't upgrade to your minimum OS version. Supporting two OS versions behind the latest major release is pretty common.
You can check Apple's compatibility chart here: https://support.apple.com/en-us/HT209574
Anything older than those devices won't work.
Open your iOS project in Xcode and then follow these steps:
I have implemented an app that uses react-native-branch and #config-plugins/react-native-branch with the expo-managed workflow but upon building with EAS in iOS (Expo Application Services), its throwing this error:
The Swift pod `ExpoAdapterBranch` depends upon `react-native-branch`, which does not define modules.
To opt into those targets generating module maps (which is necessary to import them from Swift when building as static libraries),
you may set `use_modular_headers!` globally in your Podfile, or specify `:modular_headers => true` for particular dependencies.
Is there a way to do this in expo-managed workflow?
Other details of our project:
Expo SDK: v44
react-native-branch: v5.0.0
#config-plugins/react-native-branch: v1.0.2
I finally get it to build in iOS without errors by updating my react-native-branch version from 5.0.0 to 5.4.0 without any other changes to the plugin. However, expo is now giving off a warning saying that
Some dependencies are incompatible with the installed expo package version:
- react-native-branch - expected version: 5.0.0 - actual version installed: 5.4.0
If anyone has a better solution to this, I would gladly hear it. Thanks!
Has anybody using Crashlytics been able to compile their iOS app for Mac Catalyst?
I tried building one of our iOS apps for Catalyst but I got the following error:
ld: in /Users/foo/bar/Pods/Crashlytics/iOS/Crashlytics.framework/Crashlytics(CLSInternalReport.o), building for Mac Catalyst, but linking in object file built for iOS Simulator, file '/Users/foo/bar/Pods/Crashlytics/iOS/Crashlytics.framework/Crashlytics' for architecture x86_64
I've updated to the latest version of Crashlytics using Cocoapods. Since CL already works on macOS, I would think it might be possible to link to the correct x86 library with Catalyst.
Previously Firebase Crashlytics was not supported by the Mac Catalyst. In the new version of Firebase Crashlytics (6.15.0), they have provided the support.
This is my current workaround. It does not let me use Crashlytics with Catalyst, but I can continue to create both Catalyst and iOS builds.
Clone your usual build target.
Enable Catalyst on the new target.
Add a section to the Podfile for the new target.
Include all required pods in the new target except Fabric and Crashlytics.
pod install
In the source code, conditionally build Crashlytics-dependent code using #if canImport(Crashlytics)
Continue to build the iOS app from the old target. Use the new target for Catalyst builds.
As CocoaPods 1.1.0+ is required to build Alamofire 4.0.0+,platform :ios, '10.0'.
how to use alamofire 4.0.0+ under iOS 10?
CocoaPods 1.1.0+ is indeed required but as stated in the Readme the minimum iOS version is 9.0. The Podfile given there is just an example so you should write platform :ios, '9.0' to target below iOS 10.
I tried installing my CocoaPods with pod install and a Podfile that looks like
platform :osx
pod 'ReactiveCocoa', '~> 2.1.8'
But I got the error
[!] The platform of the target `Pods` (OS X 10.6) is not compatible with `ReactiveCocoa (2.1.8)` which has a minimum requirement of iOS 5.0 - OS X 10.7.
My deployment target is OSX 10.9 and the SDK is 10.9 so I'm not sure where it's getting OSX 10.6.
The solution is to just specify a platform version in the Podfile
platform :osx, '10.7'
I found that the default platform for CocoaPods is 10.6 on OS X and 4.3 on iOS currently. The CocoaPods website describes it here. It does not seem to care about or sniff out platform versions from the Xcode Project file.
A similar error appears for iOS projects apparently.
[!] The platform of the target Pods (iOS 4.3) is not compatible with...