xcodebuild

Xcode 10: unable to attach DB error

蹲街弑〆低调 提交于 2019-11-26 15:41:21
问题 When updating to Xcode 10, iOS static library target fails to build. Way how I am trying to build it is following: xcodebuild -target TargetName -configuration Release clean build With Xcode 9 everything runs smoothly, but when Xcode 10 is used for build, I am getting following error (after clean runs smoothly): note: Using new build system note: Planning build note: Constructing build description Build system information error: unable to attach DB: error: accessing build database "/Users

iOS builds / ipa creation no longer works from the command line

帅比萌擦擦* 提交于 2019-11-26 15:13:44
问题 Overview Our command line builds (to build and create the .ipa) are no longer working. iTunesConnect has started rejecting builds that use the CODE_SIGN_RESOURCE_RULES_PATH build setting. If we build WITHOUT that setting the PackageApplication tool (which we use to create the signed .ipa) fails. It seems that PackageApplication calls /usr/bin/codesign with resource-rules arguments even if the CODE_SIGN_RESOURCE_RULES_PATH build setting is excluded I suspect the PackageApplication needs to be

Xcode 4: Run tests from the command line (xcodebuild)?

喜欢而已 提交于 2019-11-26 12:51:06
问题 I\'ve created a brand new iOS project in Xcode 4, and included unit tests. The default app has 2 targets, the main application and the unit test bundle. Using \"Product > Test\" (Command-U) builds the application, builds the unit test bundle, launches the iOS simulator and runs the tests. Now I\'d like to be able to do the same thing from the command line. The command line tool (xcodebuild) doesn\'t have a \"test\" action, but it seems like I should be able to build the unit test bundle

No architectures to compile for (ONLY_ACTIVE_ARCH=YES, active arch=x86_64, VALID_ARCHS=armv7 armv7s)

有些话、适合烂在心里 提交于 2019-11-26 12:08:31
问题 Running in Xcode is correctly, but when I want to use command line with $ /usr/bin/xcodebuild -scheme projectA -workspace projectA.xcworkspace -configuration Debug clean build And come up with the following. === BUILD NATIVE TARGET projectA OF PROJECT projectA WITH CONFIGURATION Debug === Check dependencies No architectures to compile for (ONLY_ACTIVE_ARCH=YES, active arch=x86_64, VALID_ARCHS=armv7 armv7s). In Build Settings are: Architectures: Starndard (armv7, armv7s) Base SDK: Latest iOS

Xcode : Adding a project as a build dependency

跟風遠走 提交于 2019-11-26 10:57:13
问题 Im playing around with the soundcloud api, in its instructions it says to drag SoundCloudAPI.xcodeproj into your project add it as a build dependency I can drag the project in pretty easily, but how does one accomplish the next step? 回答1: To add it as a dependency do the following: Highlight the added project in your file explorer within xcode. In the directory browser window to the right it should show a file with a .a extension. There is a checkbox under the target column (target icon),

How to solve “Application failed codesign verification” when uploading to iTunes Connect?

亡梦爱人 提交于 2019-11-26 10:35:46
问题 I\'ve got a problem that I couldn\'t solve with a deep search in different resources as most of the \"similar\" points out to be an error with Icon.png size, etc... I\'ve tried to upload my application after verifying that: Correctly builds and run on my device That my certificates are installed properly That my certs / profiles are not expired. That the Icon.png has the proper size and format of 57x57 PNG. And several other things. Ran codesign --verify -vvvv MyApp.app which worked fine. My

Use xcodebuild (Xcode 8) and automatic signing in CI (Travis/Jenkins) environments

ぐ巨炮叔叔 提交于 2019-11-26 10:07:32
问题 With the release of Xcode 8, Apple introduced a new way of managing the signing configuration. Now you have two options Manual and Automatic . According to the WWDC 2016 Session about Code signing (WWDC 2016 - 401 - What\'s new in Xcode app signing), when you select Automatic signing, Xcode is going to: Create signing certificates Create and update App IDs Create and update provisioning profiles But according to what Apple says in that session, the Automatic Signing is going to use

xcodebuild different provisioning profile for target dependency

▼魔方 西西 提交于 2019-11-26 08:12:58
问题 I\'m trying to build my app with xcodebuild: xcodebuild -workspace \"RG.xcworkspace\" -scheme \"Production\" -configuration \"Release\" build CONFIGURATION_BUILD_DIR=\"${TEMP_DIR}\" PROVISIONING_PROFILE=\"1234-5678-9098-7654-3210\" My scheme has two targets. One target is the app, the other is the app extension (I built an extension for Safari). The app extension is a target dependency. Each target requires a separate provisioning profile. I don\'t know how to specify the PROVISIONING_PROFILE

How do I run an terminal command in a swift script? (e.g. xcodebuild)

末鹿安然 提交于 2019-11-26 06:53:24
I want to replace my CI bash scripts with swift. I can't figure out how to invoke normal terminal command such as ls or xcodebuild #!/usr/bin/env xcrun swift import Foundation // Works println("Test") // Works ls // Fails xcodebuild -workspace myApp.xcworkspace // Fails $ ./script.swift ./script.swift:5:1: error: use of unresolved identifier 'ls' ls // Fails ^ ... etc .... If you don't use command outputs in Swift code, following would be sufficient: #!/usr/bin/env swift import Foundation @discardableResult func shell(_ args: String...) -> Int32 { let task = Process() task.launchPath = "/usr