Open aansheng opened 2 years ago
Have you tried building it directly inside xcode? Do you see any different errors that way?
Have you tried building it directly inside xcode? Do you see any different errors that way?
I don't have an M1 for testing. Can you guys confirm react-native-macos supports M1?
@landabaso Yes, I have it working on an M1.
I get the same issue on my M1
$ react-native run-macos --verbose
info Found Xcode workspace "myapp.xcworkspace"
info Building (using "xcodebuild -workspace myapp.xcworkspace -configuration Debug -scheme myapp-macOS")
.............
error Failed to build macOS project. We ran "xcodebuild" command but it exited with error code 65. To debug build logs further, consider building your app with Xcode.app, by opening myapp.xcworkspace.
Command line invocation:
/Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -workspace myapp.xcworkspace -configuration Debug -scheme myapp-macOS
User defaults from command line:
IDEPackageSupportUseBuiltinSCM = YES
note: Using new build system
note: Planning
Analyze workspace
Create build description
Build description signature: e4b76d3b03b522c8d30e1ea076c01f0e
Build description path: /Users/evanion/Library/Developer/Xcode/DerivedData/myapp-gbsdlzvlumumohhajmgiwxtexbby/Build/Intermediates.noindex/XCBuildData/e4b76d3b03b522c8d30e1ea076c01f0e-desc.xcbuild
note: Build preparation complete
note: Building targets in dependency order
/Users/evanion/Projects/Personal/myapp/clients/macos/macos/Pods/Target Support Files/Pods-myapp-macOS/Pods-myapp-macOS.debug.xcconfig:1:1: error: unable to open file (in target "myapp-macOS" in project "myapp")
/Users/evanion/Projects/Personal/myapp/clients/macos/macos/Pods/Target Support Files/Pods-myapp-macOS/Pods-myapp-macOS.debug.xcconfig:1:1: error: unable to open file (in target "myapp-macOS" in project "myapp")
/Users/evanion/Projects/Personal/myapp/clients/macos/macos/Pods/Target Support Files/Pods-myapp-macOS/Pods-myapp-macOS.debug.xcconfig:1:1: error: unable to open file (in target "myapp-macOS" in project "myapp")
2022-07-22 16:57:44.961 xcodebuild[97658:7995743] Requested but did not find extension point with identifier Xcode.IDEKit.ExtensionSentinelHostApplications for extension Xcode.DebuggerFoundation.AppExtensionHosts.watchOS of plug-in com.apple.dt.IDEWatchSupportCore
2022-07-22 16:57:44.961 xcodebuild[97658:7995743] Requested but did not find extension point with identifier Xcode.IDEKit.ExtensionPointIdentifierToBundleIdentifier for extension Xcode.DebuggerFoundation.AppExtensionToBundleIdentifierMap.watchOS of plug-in com.apple.dt.IDEWatchSupportCore
--- xcodebuild: WARNING: Using the first of multiple matching destinations:
{ platform:macOS, arch:x86_64, id:0381D851-C885-5BB0-9B75-144A387A0EC4 }
{ platform:macOS, arch:arm64, id:0381D851-C885-5BB0-9B75-144A387A0EC4 }
{ platform:macOS, name:Any Mac }
** BUILD FAILED **
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
In xcode it just says:
/Users/evanion/Projects/Personal/myapp/clients/macos/macos/Pods/Target Support Files/Pods-myapp-macOS/Pods-myapp-macOS.debug.xcconfig:1:1: unable to open file (in target "myapp-macOS" in project "myapp")
This is a clean codebase generated using:
$ npx react-native init myapp --template react-native-template-typescript@^6.6.5
$ cd myapp
$ npx react-native-macos-init
should note that the project name in package.json differs from the registered app name (@myapp/macos)
@Evanion what version of RN did you select when starting the project?
@Evanion what version of RN did you select when starting the project?
0.64 as per the specification in the react-native-template-typescript
readme
It might be typescript. I remember when I set it up I had versioning mistmach with SQLite that threw a similar error.
Try running the following and see if it builds: npx react-native init testm1 --template react-native@^0.64.0
Also, make sure you ran the pod install step.
I just faced the same on a Intel Macbook, and upgrading the react-native-macos version to 0.68 did the trick, as shown on this PR: https://github.com/react-native-webview/react-native-webview/pull/2828
Environment
Steps to reproduce the bug
error message
Expected Behavior
No response
Actual Behavior
No response
Reproducible Demo
No response
Additional context
No response