Reputation: 10329
I am using XCode 3.2.5. Due to a problem in Flurry I would realy like to test my apps on iOS 3.x, and since I updated all my test devices to 4.x I don't have any 3.x handsets left.
I have tried to follow this guide on how to install extra SDKs into newer xcodes, but when installing previouse SDKs and launcing them the simulation doesn't work. It notifies that the SDK failed to launch and lets me choose either to Quit, switch SDK or Relaunch the simulator.
Is there anything that I am forgetting or missing? Did someone managed to install earlier SDK's into 3.2.5?
Br, Paul Peelen
Upvotes: 5
Views: 1487
Reputation: 19869
i think its important to know that the simulator is a "forgiver" a lot more then the device. i have released an app that worked great when tested on simulator for 3.1 but crashed on lunching when downloaded...you defiantly don't want that to happen.
i have mailed apple about that and the official answer i got was to test it on real devices. thats a problem if you cant afford buying the devices. but try to get them second hand.
just don't trust the simulator alone.
Upvotes: 0
Reputation: 2127
The best thing you can do is to get a used 1st/2nd gen iPod touch - they can be upgraded and downgraded just fine and are better for testing than the simulator.
But if you want to test with the old SDK anyway, assuming you have a disk image with an old SDK on it, you can install the previous SDK to somewhere other than the default directory of /Developer
(e.g. something like /Developer3.2
), then open your project in the copy of Xcode from /Developer3.2/Applications
.
I don't know if there are any negative effects from doing this, but I often install beta SDKs to /DeveloperBeta
for testing and haven't run into any problems.
Upvotes: 2
Reputation: 29524
Not sure if this is your problem, but when you are building in Xcode make sure you change the active target to the older SDK.
To change the target, hit alt-cmd-e, switch to Build
, and under Base SDK
select the SDK you want.
Upvotes: 0