build-settings

iOS: Universal App - Release as iPhone only

时间秒杀一切 提交于 2019-12-03 15:04:09
问题 A customer is interested in releasing a universal app. However, the first release will contain only the iPhone version, the second release will contain both versions. I found a few links where ppl figured out how to make this work in the simulation environment. However, i could not find claims about apps that finally were released to the AppStore successfully. I need verification of this. Do you have links of people claiming to have universal apps released for iphone only or did you do it

“Use Legacy Swift Language Version” (SWIFT_VERSION) is required to be configured correctly for targets which use Swift."

别来无恙 提交于 2019-12-03 07:59:29
问题 Ever since I've updated to Xcode 8.2 (GM seed, from the App Store), I have been stuck at the following error: Use Legacy Swift Language Version” (SWIFT_VERSION) is required to be configured correctly for targets which use Swift. Use the [Edit > Convert > To Current Swift Syntax…] menu to choose a Swift version or use the Build Settings editor to configure the build setting directly. So I went to my target's Build Settings , and searched for SWIFT_VERSION to see where I was erring. However, I

iOS: Universal App - Release as iPhone only

喜夏-厌秋 提交于 2019-12-03 04:47:18
A customer is interested in releasing a universal app. However, the first release will contain only the iPhone version, the second release will contain both versions. I found a few links where ppl figured out how to make this work in the simulation environment. However, i could not find claims about apps that finally were released to the AppStore successfully. I need verification of this. Do you have links of people claiming to have universal apps released for iphone only or did you do it yourself? It's not possible to only release the iPhone version via iTunes Connect, but you can set the

“Use Legacy Swift Language Version” (SWIFT_VERSION) is required to be configured correctly for targets which use Swift.\"

拜拜、爱过 提交于 2019-12-02 21:50:33
Ever since I've updated to Xcode 8.2 (GM seed, from the App Store), I have been stuck at the following error: Use Legacy Swift Language Version” (SWIFT_VERSION) is required to be configured correctly for targets which use Swift. Use the [Edit > Convert > To Current Swift Syntax…] menu to choose a Swift version or use the Build Settings editor to configure the build setting directly. So I went to my target's Build Settings , and searched for SWIFT_VERSION to see where I was erring. However, I was surprised to find that it was already set to No ! How do I fix this? Please select the target in

iOS: Clarify different Search Paths

两盒软妹~` 提交于 2019-12-02 15:16:29
There are three different search paths in XCode Build Settings: Framework Search Path Header Search Path Library Search Path Could anyone clarify what those paths do and what they are used for? Framework search path : where to search frameworks ( .framework bundles) in addition to system frameworks paths. Not used very much in iOS development, officially there is no developer iOS frameworks. In Mac development, it's set automatically if you drag a 3rd party framework into the project. Otherwise, just set it to the container directory where you saved the framework. In xcconfig files you use

Accessing Deployment Target in unit test code

天大地大妈咪最大 提交于 2019-12-02 07:22:41
I need to know my deployment target in my unit test cases. Is there any way to get the iOS deployment target programmatically (using Objective-C)? Displays as a 'big' int: NSLog(@"Deployment target: %i", __IPHONE_OS_VERSION_MIN_REQUIRED); e.g. for iOS 5.1 as the deployment target Deployment target: 50100 This is available as an Xcode build variable called IPHONEOS_DEPLOYMENT_TARGET . All you need to do is create a preprocessor macro holding that value: and then you can refer to AMIT_DEPLOYMENT_TARGET in your code. (Note: this is a float , rather than the string you might expect.) 来源: https:/

Accessing Deployment Target in unit test code

孤人 提交于 2019-12-02 07:11:19
问题 I need to know my deployment target in my unit test cases. Is there any way to get the iOS deployment target programmatically (using Objective-C)? 回答1: Displays as a 'big' int: NSLog(@"Deployment target: %i", __IPHONE_OS_VERSION_MIN_REQUIRED); e.g. for iOS 5.1 as the deployment target Deployment target: 50100 回答2: This is available as an Xcode build variable called IPHONEOS_DEPLOYMENT_TARGET . All you need to do is create a preprocessor macro holding that value: and then you can refer to AMIT

XCode 4 “add build setting condition” not enabled

白昼怎懂夜的黑 提交于 2019-12-01 10:48:23
I am trying to include Layar Player in the iPhone application I am developing in XCode 4. One of the steps of section "1.3.1.2 Universal build configuration" asks to click on "Add Build Setting Condition". But that option is not enabled (it is shown in grey). Only the "Add User-defined Setting" is enabled. How can I make this option to be enabled or what could be wrong? Thanks a lot in advance. Cristina To enable the Add Build Setting Condition menu item in Xcode 4, you must select a specific build configuration for a build setting. Click the disclosure triangle next to the build setting to

How to set default compiler options for XE2?

此生再无相见时 提交于 2019-12-01 03:53:42
I am unable to figure out how to change default build/compile settings. The little default checkbox in the lower left of the project options dialog is gone. The documentation states: The Default checkbox that appeared at the lower edge of many Project Options pages has been removed from the product. If you want to specify options as the default for multiple projects, the suggested alternative is to use option sets instead. I'm going round and round about " Options Sets ", " Configuration Manager " etc.. Is this even possible? What does "specifying options as the default for multiple projects"

Can no longer import app module into unit tests after changing deployment target

拈花ヽ惹草 提交于 2019-11-30 19:27:00
For unit testing public classes of my main app target in my swift unit tests, I have to import my main app module in my tests like so: #import MyAppModuleName This worked just fine until I changed my deployment target from 7.0 to 8.4. Now building and running my app still works perfectly, but running unit tests stopped working. The compiler complains about the above import statement: Swift Compiler Error: Module file's minimum deployment target is iOS8.4 v8.4 I have no clue why. Did I forget to change the deployment target somewhere else? My workspace (Xcode 6.4.) contains my own project and a