reactjs – Failure to construct when simulating iOS react-native app


I’m trying to carry out react-native ios on an outdated venture and it simply can not seem to efficiently construct…

I am not solely certain which of the assorted console outputs is inflicting the difficulty.

The ultimate output is

** BUILD FAILED **
The next construct instructions failed:
CompileC /Customers/username/Library/Developer/Xcode/DerivedData/some-id/Construct-id/Intermediates.noindex/Pods.construct/Debug-iphonesimulator/FirebaseMessaging.construct/Objects-normal/arm64/GtalkExtensions.pbobjc.o /Customers/username/git/project-name/ios/Pods/FirebaseMessaging/FirebaseMessaging/Sources/Protos/GtalkExtensions.pbobjc.m regular arm64 objective-c com.apple.compilers.llvm.clang.1_0.compiler (in goal ‘FirebaseMessaging’ from venture ‘Pods’)
(1 failure)

I’m operating a M2 Macbook Professional whereas I imagine this was developed older {hardware}, probably mid-2016 Mac.

node -v: 16.10.0
yarn -v: 1.22.19
ruby -v: 2.7.6
xcode model: 14.1

I adopted the directions on the official docs on organising the atmosphere. I’ve run yarn set up on the primary root, cd‘d into the ios listing and run pod set up adopted by npx react-native run-ios --simulator="iPhone 14"

After operating the pod set up nonetheless I do see the next, speaking about Firebase model inconsistencies…

Including a customized script part for Pod RNFBApp: [RNFB] Core Configuration
Auto-linking React Native modules for goal `workspace-name`: Expo, RNCAsyncStorage, RNCMaskedView, RNFBAnalytics, RNFBApp, RNFBDynamicLinks, RNFBIid, RNFBMessaging, RNGestureHandler, RNRate, RNScreens, RNVectorIcons, react-native-app-auth, react-native-geolocation, react-native-safe-area-context, and react-native-webview
Utilizing Expo modules
Analyzing dependencies
Downloading dependencies
Producing Pods venture
Integrating shopper venture
Pod set up full! There are 67 dependencies from the Podfile and 83 whole pods put in.

[!] NPM package deal '@react-native-firebase/analytics' will depend on '@react-native-firebase/app' v10.0.0 however discovered v8.4.7, this would possibly trigger construct points or runtime crashes.

[!] NPM package deal '@react-native-firebase/dynamic-links' will depend on '@react-native-firebase/app' v9.0.0 however discovered v8.4.7, this would possibly trigger construct points or runtime crashes.

[!] NPM package deal '@react-native-firebase/iid' will depend on '@react-native-firebase/app' v8.4.1 however discovered v8.4.7, this would possibly trigger construct points or runtime crashes.

[!] NPM package deal '@react-native-firebase/messaging' will depend on '@react-native-firebase/app' v8.4.1 however discovered v8.4.7, this would possibly trigger construct points or runtime crashes.

[!] use_native_modules! skipped the react-native dependency 'react-native-apple-ads-attribution'. No podspec file was discovered.
    - Examine to see if there may be an up to date model that accommodates the mandatory podspec file
    - Contact the library maintainers or ship them a PR so as to add a podspec. The react-native-webview podspec is an effective instance of a package deal.json pushed podspec. See 
    - If needed, you'll be able to disable autolinking for the dependency and hyperlink it manually. See 

[!] NPM package deal '@react-native-firebase/analytics' will depend on '@react-native-firebase/app' v10.0.0 however discovered v8.4.7, this would possibly trigger construct points or runtime crashes.

[!] NPM package deal '@react-native-firebase/dynamic-links' will depend on '@react-native-firebase/app' v9.0.0 however discovered v8.4.7, this would possibly trigger construct points or runtime crashes.

[!] NPM package deal '@react-native-firebase/iid' will depend on '@react-native-firebase/app' v8.4.1 however discovered v8.4.7, this would possibly trigger construct points or runtime crashes.

[!] NPM package deal '@react-native-firebase/messaging' will depend on '@react-native-firebase/app' v8.4.1 however discovered v8.4.7, this would possibly trigger construct points or runtime crashes.

[!] use_native_modules! skipped the react-native dependency 'react-native-apple-ads-attribution'. No podspec file was discovered.
    - Examine to see if there may be an up to date model that accommodates the mandatory podspec file
    - Contact the library maintainers or ship them a PR so as to add a podspec. The react-native-webview podspec is an effective instance of a package deal.json pushed podspec. See 
    - If needed, you'll be able to disable autolinking for the dependency and hyperlink it manually. See 

[!] NPM package deal '@react-native-firebase/analytics' will depend on '@react-native-firebase/app' v10.0.0 however discovered v8.4.7, this would possibly trigger construct points or runtime crashes.

[!] NPM package deal '@react-native-firebase/dynamic-links' will depend on '@react-native-firebase/app' v9.0.0 however discovered v8.4.7, this would possibly trigger construct points or runtime crashes.

[!] NPM package deal '@react-native-firebase/iid' will depend on '@react-native-firebase/app' v8.4.1 however discovered v8.4.7, this would possibly trigger construct points or runtime crashes.

[!] NPM package deal '@react-native-firebase/messaging' will depend on '@react-native-firebase/app' v8.4.1 however discovered v8.4.7, this would possibly trigger construct points or runtime crashes.

There are earlier logs that state:

/Customers/username/git/project-name/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment goal ‘IPHONEOS_DEPLOYMENT_TARGET’ is about to 10.0, however the vary of supported deployment goal variations is 11.0 to 16.1.99. (in goal ‘React-RCTLinking’ from venture ‘Pods’)

Nevertheless there are a number of logs like this, some stating 10.0, some stating 9.0

There are some stories of manually linked dependencies, the place I do know they’ve been included through yarn

error React Native CLI makes use of autolinking for native dependencies, however the next modules are linked manually:
@react-native-community/geolocation (to unlink run: “react-native unlink @react-native-community/geolocation”)
appcenter (to unlink run: “react-native unlink appcenter”)
appcenter-crashes (to unlink run: “react-native unlink appcenter-crashes”)
react-native-screens (to unlink run: “react-native unlink react-native-screens”)
react-native-vector-icons (to unlink run: “react-native unlink react-native-vector-icons”)
react-native-webview (to unlink run: “react-native unlink react-native-webview”)

The remaining logs:

error Didn’t construct iOS venture. We ran “xcodebuild” command however it exited with error code 65. To debug construct logs additional, take into account constructing your app with Xcode.app, by opening workspace-name.xcworkspace.
Command line invocation:
/Functions/Xcode.app/Contents/Developer/usr/bin/xcodebuild -workspace worspace-name.xcworkspace -configuration Debug -scheme workspace-name -destination id=xxx

Person defaults from command line:
IDEPackageSupportUseBuiltinSCM = YES

Put together packages

Computing goal dependency graph and provisioning inputs

Create construct description
Construct description signature: 123
Construct description path: /Customers/username/Library/Developer/Xcode/DerivedData/worspace-name-xxx/Construct/Intermediates.noindex/XCBuildData/123-desc.xcbuild

warning: Constructing targets in handbook order is deprecated – select Dependency Order in scheme settings as a substitute, or set DISABLE_MANUAL_TARGET_ORDER_BUILD_WARNING in any of the targets within the present scheme to suppress this warning

Related Articles

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Latest Articles