Base SDK 3.0 to SDK 4.0 - iphone

I installed SDK 4.0 and found that I lost access to all previous SDK versions prior to 3.2.
I have found a link to download SDK 3.1.3 so I have both .dmg install files.
Questions:
Does SDK 4.0 not allow access to earlier version?
If the answer above is no then does that mean I have to have two versions of SDK installed?
If yes to the above....how?
Thanks in hope

The terminology is confusing but once you understand this it's easy.
The 'Base SDK' is just the version of the SDK that you are compiling against. So you can use any classes, properties, or methods in the Base SDK.
The Deployment Version is earliest version of the OS that you want users to be able to run your code against. If you use a feature available in the Base SDK version but not in the Deployment version then your code will launch on both versions but will crash on the earlier OS version when you use the new feature, so you need to check if the new feature is present if you want to do this.
So you don't need Base SDK of 3.0 to run on 3.0 - just set Base SDK to 4.0 and Deployment Version to 3.0 and don't use any features of the SDK that weren't present beyond 3.0.

The deployment target can be set to anything (even 2.2), but the Base SDK has nothing except 3.2 and 4.0. I would have thought if you set the deployment target to 3.0 for example, that the Base SDK could also be set to 3.0.
So if the deployment SDK is 3.0, and the base SDK is 4.0, which one is being compiled for?
Note in the new SDK, you can't select anything other than 3.2 and 4.0 as mentioned above.

Looks like a problem with apple. I am also getting:
"Base SDK Missing" after installing Snow Leopard and the iPhone SDK 4.
There is no Base SDK in my case.
I'm a newbie to the system and meant to make this a comment, not an Answer.
UPDATE:
After reading the readme that comes with the SDK 4 a little closer, I see that it (xCode 3.2.3 and it's iPhone SDK4) does not support iPhone prior to 3.2 - the solution is to install the older SDK in a different directory. Also, don't forget to update your device if you use the newer xCode/SDK.
ANOTHER UPDATE:
Please ignore this ANSWER and see the one above that was provided by aizuchi. Don't forget to read the part about Base SDK area being a different thing from Deployment.

As I understand it, using any SDKs other than 3.2 and 4.0 is now deprecated for app store submissions. Therefore, logically, those other SDKs are no longer options in xCode (3.2.3) either. IMO, trying to get around this is futile. I've written a community wiki that explains it more fully here.

You need to set the Base SDK to the latest version and set the iPhone Deployment Target to 3.0 for example.
It's recommend to test your application for earlier versions.

Related

How to support different iOS versions?

I just uploaded a beta of my app to http://testflightapp.com. I noticed that it is only for iOS 4.3.
How can I support devices from iOS 4.0? Do I have to make the ipa for each framework version?
Any suggestions?
Set the iOS Deployment Target in your build settings to the oldest version you want to support.
Please note that this doesn't automatically make sure that your code actually works on the older API (for example if you use stuff in the frameworks that's only available in the latest version ... )

Xcode SDK IOS 4.2 installation and missing iOS 4.1 in build settings

i have download Xcode SDK 4.2(xcode_3.2.5_and_ios_sdk_4.2_final.dmg) from Apple developer site and installed successfully . when open my old xcode project it shows baseSDk missing ,when i try to change project setting ,i have found and set base SDk as 4.2 it works fine
my problem is ,in Base SDk list it shows
(iOS 2.1, iOS 2.2, iOS 2.2.1, iOS 3.0, iOS 3.1, iOS 3.1.2, iOS 3.1.3, iOS 4.2)
There is no iOS 4.0 and iOS 4.1 (which i have used before 4.2). anything wrong in my installation???? Plz help me to correct my mistake
Thanks in advance
This does happen. I generally just use the latest SDK as base SDK. You support the latest version and forget abt the older versions[apple style]. This way your app can take advantage of all the latest functionality.
One thing you must remember is that the Base SDK is different from the deployment target.
base SDK is the latest SDK your project will use and support.
deployment target is found in target->getInfo; this is the minimum version that your app will support.
4.2 is a free upgrade and most of them would upgrade, so i'd set the deployment target as 4.0 or at the least 3.0. who uses 2.x anymore?
if you really want 4.0 and 4.1 as well, you have to install the old 4.1 GM as a parallel Xcode IDE or follow this link and get support for all the versions in a single XCode IDE.
http://chris-fletcher.com/2010/08/28/howto-install-iphone-sdk-2-0-3-1-for-xcode-3-2/
I'd suggest building using 4.2 but follow the link and install all the simulator SDKs for old versions so that you can test the app on those versions of the simulator.
Nothing went wrong here. That's how Apple forces the developers to always use the latest SDK to develop.

XCode and recent iOS SDK

I am currently using XCode 3.2.2 and iOS SDK 3.2. With these I can produce binary which works on iPhone 3.1.3. If I upgrade to XCode 3.2.4 and iOS 4.1, would I still be able to build binaries for iPhone 3.1.3 device? If no, can I install both, or it's tricky?
Eiko is correct, what's more I believe that apple will no longer accept applications built with pre 4.x SDK.
To get this set up you need to change the following settings
Set the "Base SDK" in your projects settings to the newest version number of iOS whose features you may want.
Set the "iPhone OS Deployment Target" to the oldest version number of iOS that you will support.
Courtesy of CocoaWithLove
Regarding installing multiple versions, it's not tricky... just awkward. The release versions of XCode are installed into the /Developer directory. To install multiple versions you need to move the /Developer directory to something else e.g. /OldXCode and then install the new version (Which is put into /Developer)
Hope that helps
You can, and you should, always use the latest SDK.
You can easily build agains 4.1 and still target 3.x - in fact most developers do this at the moment.

How to get iPhone SDK 2.2.1 for Xcode 3.2?

After my upgrade to Snow Leopard and Xcode 3.2 (which I really regret a lot!!), Xcode lost all the SDK's. I'm one of those old-fashioned idiots who still want to develop for 2.2.1. But Apple does not offer me an old SDK download.
Now I was clever and made tons of time machine backups. But: What's the preferred way to get iPhone SDK 2.2.1 running with Xcode 3.2? Some guys said that's generally possible. I do hope so because I still don't believe in all those "faked" stats, and besided that, my app doesn't benefit from 3.x additional features so I would not want to constrain my market just for that lazyness.
Any idea?
Regardless of whether or not you're targeting iPhone OS 3.0 or not using any 3.0 specific features, you should always compile your app against the latest SDKs to benefit from bug fixes and performance improvements.
You can compile against the 3.0 SDK and set the iPhone OS Deployment Target to 2.2.1 and still cater for users who are using 2.2.1.
You may find that some methods have been deprecated, but that doesn't stop you from using them until you're ready to move on.
Get the 3.1 final sdk, it has the 2.2.1 sdk in it. On disk its usual location is:
/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS2.2.1.sdk
Also included is 3.0 and 3.1.
XCode 3.2 should have the prior iPhone SDKs available, just make sure you are setting your project's Base SDK setting to "iPhone OS 2.2.1". (Right-click on your top-level project icon in the Groups & Files browser in XCode and choose "Get Info", then go to the Build tab.)
Raffaello and others are correct: you can use the latest SDK and still target (and test on) older SDKs. For example, I'm using iOS4.0 (xcode 3.2.3) and testing on my iPhone 3g running 3.1.3.
To clarify the procedure:
- go to project info > build tab
- set Architectures:Base SDK (most likely) the latest
- set Deployment:iPhone OS Deployment Target to what ever you want (I have the option to go as far back as 2.0).
Hope this helps someone.
Like I said on other threads, the SDK and Deployment Target are different.
You can still use the latest SDK to build for an older OS.
Just go to your Target settings and under the Deployment section set the iPhone OS Deployment Target to whatever you'd like.
Cheers,
Raffaello Colasante

iPhone application compatibility, compiled using 3.1 sdk. Can resubmitt binary compiled using 3.0?

Hello I have recently uploaded an application to the app store and it got approved. The issue is the application has been compiled using the 3.1 sdk, and thus is not working on 3.0 devices. Would there be any problems if i resubmitted the application compiled using the 3.0 sdk? (I want to support 3.0 because a lot of people still have not upgraded their devices, and I don't have any feature that differ between 3.1 and 3.0)
Depending on whether or not you're using any APIs that are restricted to version 3.0 or 3.1 you should set your base SDK as the highest version that the latest official SDK supports (not beta SDKs).
After doing that, you should then set your deployment target in your build settings to the lowest version of iPhone OS that you want your app to run on.
So if you're not using any API's that are specific to 3.0 you could compile against the 3.0 SDK and then set your deployment target to 2.0.
This way you benefit from most of the bug fixes brought along in the SDK update, but still retain the wide user base of people who didn't upgrade.
You can resubmit to 3.0 if you wish, I remember the NYTimes application was at 2.2.1 and a future update released as 2.2 since a large number of people were still using 2.2. So long as your application has been tested to work properly on 3.0 and the 3.0 binary works on 3.1 you'll be fine. Just you'll need to wait for the approval process again.
You can compile your app using whatever version you like. It just has to run on 3.1.
This answer is somewhat related as to what you can compile with versus what you have to test against for compatibility.