麻烦调试反应本机iOS构建错误“ expomodulescore”
我一直在使用fastlane在M1 Mac上使用GitHub操作来建立构建系统,以实现构建系统。
我不断遇到以下错误:
CompileSwiftSources normal arm64 com.apple.xcode.tools.swift.compiler (in target 'ExpoModulesCore' from project 'Pods')
PhaseScriptExecution [CP-User]\ Generate\ Specs /Users/runner/Library/Developer/Xcode/DerivedData/LbSiteDiary-fpatcoydpffbmtegkcojxxcexlzc/Build/Intermediates.noindex/ArchiveIntermediates/LbSiteDiary/IntermediateBuildFilesPath/Pods.build/Release-iphoneos/FBReactNativeSpec.build/Script-46EB2E00025480.sh (in target 'FBReactNativeSpec' from project 'Pods')
(2 failures)
使用Xcode 13.2和13.3发生。我已经尝试了所有通常的情况,例如重置node_modules + pods。
我很难遇到实际错误...任何要调试的指示都将受到赞赏,因为我目前没有线索...
I've been running into an issue while setting up a build system for react-native using github actions on a M1 mac using fastlane.
I keep running into the following error:
CompileSwiftSources normal arm64 com.apple.xcode.tools.swift.compiler (in target 'ExpoModulesCore' from project 'Pods')
PhaseScriptExecution [CP-User]\ Generate\ Specs /Users/runner/Library/Developer/Xcode/DerivedData/LbSiteDiary-fpatcoydpffbmtegkcojxxcexlzc/Build/Intermediates.noindex/ArchiveIntermediates/LbSiteDiary/IntermediateBuildFilesPath/Pods.build/Release-iphoneos/FBReactNativeSpec.build/Script-46EB2E00025480.sh (in target 'FBReactNativeSpec' from project 'Pods')
(2 failures)
This occurs using Xcode 13.2 and 13.3. I've tried all the usual, such as resetting node_modules + pods.
I'm having trouble getting to the actual error... Any pointers to debugging this are appreciated, as I am currently out of clues...
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
我能够通过查看位于〜/logs/logs/gym/appname.log中的 build_app build_app 。
该日志文件强调,基本问题是NVM的异位。
I was able to find out more information by looking at the
gym
/build_app
logfile located in ~/Logs/gym/AppName.log.This logfile highlighted that the underlying issue was a misconfiguration of nvm.