xcodebuild

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

帅比萌擦擦* 提交于 2019-11-27 10:30:19
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 updated so that it does not call /usr/bin/codesign with resource-rules arguments when the CODE_SIGN

Running xcodebuild from a forked terminal

扶醉桌前 提交于 2019-11-27 10:04:57
I'm trying to setup an automated build server for an iPhone application. I'd like to be able to have nightly adhoc beta builds so that testers can follow the development. I've setted up xcode successfully xcode to perform adhoc builds and I can also launch the build from the command line: xcodebuild -configuration AdHoc -sdk iphoneos2.2 clean build The problem I'm having is that the following line doesn't work from a forked terminal (using nohup or screen) and failed with the following CodeSign error: Code Signing Identity 'iPhone Distribution: XXXXX' does not match any code-signing

Xcode : Adding a project as a build dependency

让人想犯罪 __ 提交于 2019-11-27 07:23:26
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? 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), check it. Right-Click on your Target (under the targets item in the file explorer) and choose Get Info On the

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

…衆ロ難τιáo~ 提交于 2019-11-27 06:43:45
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 (iOS 6.0) Build Active Architecture Only: Debug Yes, Release No Valid Architectures: armv7 armv7s After

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

落花浮王杯 提交于 2019-11-27 06:03:09
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 target directly, since it depends on the application itself. However, running: xcodebuild -target TestAppTests -sdk

Steps to upload an iPhone application to the AppStore in xcode4

梦想的初衷 提交于 2019-11-27 05:26:39
问题 as xcode 3 and xcode 4 is totally different. i'm a bit lost to submit app to app store. Do i still need to duplicate "Release" to create "iphoneDistrubition" configuration. Or can I straight away use Release? Is Archive in xcode4 = Build in xcode3 for the purpose of submission app. If Archive = Build, the icon of the app is very blur in xcode4 organizer. Is that normal? Is there any other additional steps to follow in xcode4 to submit app to appstore. Thanks for any help. =) 回答1: Xcode 4

xcodebuild: simulator or device?

南笙酒味 提交于 2019-11-27 04:59:46
问题 How do I specify to xcodebuild (the command line tool) whether I want to build for the simulator or device? 回答1: An XCode build from the command line looks like: xcodebuild -configuration ${BUILD_TYPE} -target ${TARGET_NAME} -arch ${CPU_ARCHITECTURE} -sdk ${SIMULATOR_OR_IOS_SDK} BUILD_TYPE is something like "Release" or "Debug" (those are the defaults, you may have added others to the project) TARGET_NAME is the name of the target you are building (by default the same name as your project)

llvm-gcc-4.2: error

房东的猫 提交于 2019-11-27 04:34:46
问题 The Project build & runs fine on a real device but a build for the iphone simulator finishes in this error 'llvm-gcc-4.2: error'. Any ideas? llvm-gcc-4.2: error trying to exec '/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin/../llvm-gcc-4.2/bin/arm-apple-darwin10-llvm-gcc-4.2': execvp: No such file or directory Command /Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin/llvm-gcc-4.2 failed with exit code 255 thx, Fabian 回答1: The first thing to do when things don't

Building with LLVM and any optimization causes app to crash on startup

删除回忆录丶 提交于 2019-11-27 04:28:55
问题 When I try to build my app with LLVM 2.0 in XCode 4.0.1 and any level or optimization that is not none (anything but -O0), the app crashes after i launch it on the device (simulator is ok). I can't seem to debug the crash as it does not happen when i build in xcode and attach via GDB/LLDB. Also, the crash only happens when i build the app on the command line with xcodebuild; building via the XCode IDE doesn't crash even with the exact same project settings. I can't see any useful information

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

三世轮回 提交于 2019-11-27 03:39:56
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 ZIP File was properly done When I've tried to upload through the iTunes connect interface I got the simple