xcodebuild

问题 Our goal is to create a framework that hides our internal code and provide SDK to our customers. We have thought of creating XCFramework which fulfills our requirement. Umbrella framework is also suggested over the internet but mostly suggested to avoid that approach. Our Framework is dependent on some third-party libraries which we are using via Pods. Issue: XCFramework does not compile pods framework. We got an error like "Xyz(Pod) module not found". Even if we add pods from the client-side

来源： https://stackoverflow.com/questions/64022291/ios-14-lipo-error-while-creating-library-for-both-device-and-simulator

来源： https://stackoverflow.com/questions/64022291/ios-14-lipo-error-while-creating-library-for-both-device-and-simulator

问题 Environment Server - Azure Pipelines Hosted MacOS agent Issue Description I'm using the following configuration in my Xcode project (w automatic code signing): Is it possible to have Pipelines build and sign a project using this configuration if I've manually installed all of the provisioning profiles and certs in my pipeline prior to building? Is there any documentation for this scenario or a how-to guide? Alternatively, if this is not possible perhaps a definitive statement on this and

问题 Environment Server - Azure Pipelines Hosted MacOS agent Issue Description I'm using the following configuration in my Xcode project (w automatic code signing): Is it possible to have Pipelines build and sign a project using this configuration if I've manually installed all of the provisioning profiles and certs in my pipeline prior to building? Is there any documentation for this scenario or a how-to guide? Alternatively, if this is not possible perhaps a definitive statement on this and

问题 Environment Server - Azure Pipelines Hosted MacOS agent Issue Description I'm using the following configuration in my Xcode project (w automatic code signing): Is it possible to have Pipelines build and sign a project using this configuration if I've manually installed all of the provisioning profiles and certs in my pipeline prior to building? Is there any documentation for this scenario or a how-to guide? Alternatively, if this is not possible perhaps a definitive statement on this and

问题 The project is in Objective-C and we recently added some swift files into it. It is a white label application and builds are generated from the server. When I submit the build to appstore it gave error :- ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it. When I debugged the issue I find out the build generated from automation is now having SwiftSupport in IPA while when I generate the build

问题 The project is in Objective-C and we recently added some swift files into it. It is a white label application and builds are generated from the server. When I submit the build to appstore it gave error :- ITMS-90426: Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it. When I debugged the issue I find out the build generated from automation is now having SwiftSupport in IPA while when I generate the build

问题 I'm using command line xcodebuild tool to export ad-hoc distribution ipa file out of my archive like this: xcodebuild -exportArchive -archivePath /path/Archive.xcarchive -exportPath /path -exportOptionsPlist /path/options.plist However, this command fails with error exportArchive: exportOptionsPlist error for key 'method': expected one of {}, but found ad-hoc No mater what 'method' I provide in my export options plist, it always fails with this error. It also fails if I remove the 'method'

问题 I'm using command line xcodebuild tool to export ad-hoc distribution ipa file out of my archive like this: xcodebuild -exportArchive -archivePath /path/Archive.xcarchive -exportPath /path -exportOptionsPlist /path/options.plist However, this command fails with error exportArchive: exportOptionsPlist error for key 'method': expected one of {}, but found ad-hoc No mater what 'method' I provide in my export options plist, it always fails with this error. It also fails if I remove the 'method'