>> No, that's not something that the deployment target affects. The whole >> point of specifying one version via the SDK but an earlier version via >> deployment target is that you can use the features of the later version >> corresponding to the SDK _if you detect at runtime that they're actually >> available_.
This is a problem on the iOS, because Apple doesn't support installing earlier firmware in our devices, in an effort to defeat jailbreaking. The only way I've found to test what firmware my app is compatible with is to use jailbreaking tools. I shouldn't have to do that. So far I'm satisfied that my app is compatible with iOS 3.0 and later, but I would like to ensure that it is compatible with 2.0 and later. There's no reason it shouldn't be, but I cannot get such an earlier firmware to install. The only way I can see to test on such early firmware is to buy a used device from eBay or some such, that has never had a firmware update. -- Don Quixote de la Mancha quix...@dulcineatech.com Custom Software Development for the iPhone and Mac OS X http://www.dulcineatech.com/custom-software-development/ _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
