Re: Deployment target problem with Xcode 7
Re: Deployment target problem with Xcode 7
- Subject: Re: Deployment target problem with Xcode 7
- From: sqwarqDev <email@hidden>
- Date: Tue, 10 Nov 2015 15:20:00 +0700
- X_v_e_cd: 438d10580db22ac9cd02aa713daba4ca
- X_v_r_cd: 723e8f66f0d55b695e3bd677277979d1
On Nov 9, 2015, at 20:26 , Lorenzo Thurman < email@hidden> wrote:
Are there issues with Xcode 7 and deployment targets?
I posted a similar story last week in Cocoa-Dev (see: "debugging AutoLayout exception with no build errors” ). All told, I spent over two weeks trying to determine why Xcode 7 thought my app was just fine & dandy but 10.9 thought the few minor changes I’d made now constituted a smorgasbord of AutoLayout errors and threw exceptions in protest.
In the end, I had to resort to zipping the project from 10.11 and building it in XCode 6 on 10.9 to see what the errors were.
The takeaway for me from this experience was to do the exact opposite of Apple’s advice of always using the latest SDK and setting your deployment target to the lowest supported OS. I can’t take Apple’s advice seriously when Xcode is so poor at warning about possible errors within the range of specified deployment targets.
Rather, I’m now aiming at forwards compatibility rather than backwards: coding in the Xcode (and on the machine) of my lowest supported deployment target and adding new features there. Then I'll test the app’s new features on later versions of OS X.
Obviously this won’t work if you’re hoping to add features depending on the available SDK on the user’s machine. In my app, the feature-set is intended to be the same on all versions of OS X, so I can’t add anything that isn’t available on the lowest deployment target anyway.
Best
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden