xcodebuild

问题 I am trying to build and run test cases using command line for iOS test cases. I have given the following command: xcodebuild -target AppEngineTests -configuration Debug -sdk iphonesimulator TEST_AFTER_BUILD=YES clean build It builds the app but the testcases are not run. could someone please help? Thanks 回答1: I've found the name property to require more specification. xcodebuild test -workspace #{WORKSPACE_FILE} -scheme #{TEST_SCHEME} -destination 'platform=iOS Simulator,name=iPhone Retina

问题 I am trying to build and run test cases using command line for iOS test cases. I have given the following command: xcodebuild -target AppEngineTests -configuration Debug -sdk iphonesimulator TEST_AFTER_BUILD=YES clean build It builds the app but the testcases are not run. could someone please help? Thanks 回答1: I've found the name property to require more specification. xcodebuild test -workspace #{WORKSPACE_FILE} -scheme #{TEST_SCHEME} -destination 'platform=iOS Simulator,name=iPhone Retina

问题 I am using phonegap CLI 3.1 and XCode5. I am trying to generate the build for release mode through Phonegap CLI and Xcrun. I don't want to use Phonegap Build to upload the mobileprovision or whatever the process of them. I want to do it by xcrun to assign the mobileprovison to release build. 1) cordova build ios --release Compiling app on platform "ios" via command "/Applications/MAMP/htdocs/MyTest/MyTestApp/platforms/ios/cordova/build" --release Platform "ios" compiled successfully. 2) sudo

问题 I'm building a Mac Desktop/Cocoa Application to archive my iOS project, the core implementation uses NSTask with xcodebuild command, followed by raywenderlich's this guide. The root cause is the CoreData model file compile, I used this app to build my another project which didn't contain any CoreData files and no issue there. More interesting comparison is, I tried the same xcodebuild command in my terminal and it just succeed! Then I start to diff the two xcodebuild output and found some

问题 we have an app integrated with today extension, we use xctool and Jenkins to do continuous build and in-house distribution. In command line, before we use xctool -workspace our_workspace.xcworkspace -scheme app_schme -xcconfig path_to_xcconfig -configuration Release build archive -archivePath path_to_archive to generate archive and then export to .ipa, it works fine. But right now with today extension, we have to build it with another scheme and xcconfig, we put certificate and provisioning

问题 I recently updated Xcode to 7.1 And downloaded iOS 8.4 And iOS 9.0 Simulator. When I run xcodebuild -showsdks I get OS X SDKs: OS X 10.11 -sdk macosx10.11 iOS SDKs: iOS 9.1 -sdk iphoneos9.1 iOS Simulator SDKs: Simulator - iOS 9.1 -sdk iphonesimulator9.1 tvOS SDKs: tvOS 9.0 -sdk appletvos9.0 tvOS Simulator SDKs: Simulator - tvOS 9.0 -sdk appletvsimulator9.0 watchOS SDKs: watchOS 2.0 -sdk watchos2.0 watchOS Simulator SDKs: Simulator - watchOS 2.0 -sdk watchsimulator2.0 I want iOS Simulator SDKs

问题 Whenever I run 'build and archive' from XCode I get the following message: Unable to copy dSYM file into archive. Please make sure that your application has set the “Debug Information Format” build setting to “DWARF with dSYM File”. I have checked my Debug format and it is set to the suggested value(DWARF with dSYM). Has anyone else ran into this issue, if so how did you fix it? 回答1: Try setting 'Generate Debug Symbols' to true in the build settings of the target you're trying to build and

问题 I'm working with an existing project that produces a dynamic library (Cocoa API). I'd rather generate a static library, but if I change the [Linking|Mach-O Type] field from "Dynamic Library" to "Static Library", both the Clean Project and Build Project complain that the target has an invalid MACH_O_TYPE value of 'staticlib'. Is there a straightforward way to get the build to produce a static .a file? Thanks, Eric 回答1: Opens up the project.pbxproj file in YourProjectName.xcodeproj folder using

问题 I have a multi-target iPhone app which currently includes a header file with constant definitions that are conditionally included at build time depending on which target is being built. However, I was wondering if it might be better to instead include this information in the info.plist for the build, as this generally holds target-specific meta, so logically seems more appropriate. Therefore, my questions are: Is it acceptable to include custom (non-Apple defined) keys in the info.plist file?

问题 I have Jenkins with the Xcode plugin configured to run unit tests by adding the test build action to the Custom xcodebuild arguments setting. For more information on getting Jenkins to run the unit tests at all with Xcode 5, see this question. Now that I have it running, it seems to mix console output from NSLog statements or the final ** TEST SUCCEEDED ** message with the test results, thus occasionally tripping up the parser that converts unit test results to the JUnit format required for