Is it possible to use iPhone Simulator 3.1 from XCode 3.2.3?

XCode 3.2.3 does do iPhone simulation. You need to make sure that your project settings are correct though. I have the following settings and it works for me.

Up vote 3 down vote favorite 1 share g+ share fb share tw.

Because the Simulator 3.2 and 4.0 in the SDK 4 do NOT actually work for iPhone simulation (which always comes out iPad and not responding at all), I ended up with 2 SDK installations, using SDK 3.1.3/Simulator 3.1 for simulation, and SDK 4 for building onto the iPhone with OS 4. (More details here. ) I tried to use the old Simulator 3.1 from the SDK4-XCode 3.2.3, e.g. By copying the full "iPhoneSimulator.

Platform/Developer/SDKs/iPhoneSimulator3.1.3. Sdk" directory into the corresponding XCode3.2.3 directory, and choose the Simulator-3.1.3 (which does appear in the "Active Executable" list), but it cannot build, with more than 30 errors, e.g. Undefined symbols: "_OBJC_CLASS_$_NSURLConnection", referenced from: objc-class-ref-to-NSURLConnection in GRACEViewController. O "_OBJC_CLASS_$_NSString", referenced from: objc-class-ref-to-NSString in GRACEViewController.

O Is there a way to use Simulator 3.1 (instead of Simulator 3.2 or 4.0) when using XCode 3.2.3 (which is a must to build into iPhones on OS 4)? Iphone ios-simulator ios4 xcode3.2 link|improve this question asked Jun 25 '10 at 16:43lionfly189113 55% accept rate.

I'm having the same problem. – gyozo kudor Aug 30 '10 at 8:18 1 I finally installed 2 versions of XCode. The old version 3.2.1 for using the simulator 3.1.3, and the new version 3.2.3 to build into the device only.

– lionfly Sep 1 '10 at 0:23.

XCode 3.2.3 does do iPhone simulation. You need to make sure that your project settings are correct though. I have the following settings and it works for me: Base SDK: iPhone Device 4.0 Targeted Device Family: iPhone Deployment Target: iPhone OS 3.0 With that, you should have the option to run your project in the iPhone Simulator.

I had some trouble after upgrading, as my older project would no longer build or run. The menu selections weren't working. I had to go into the Target's info and make the settings there.

– mbmcavoy Jun 25 '10 at 17:05 2 I have the same settings, and while I can run in the simulator, the simulator is emulating iOS4. The only options in the Hardware->Version menu are 4.0 and 3.2 (which switches it to the iPad simulator). I think the OP was looking for a way to test 3.1 compatibility in the 4.0 simulator.

– Christopher Pickslay Jul 1 '10 at 15:49 I see what you're saying now. You will need an actual device running 3.1. X to test compatibility. This apple dev forum thread may provide further insight: devforums.apple.com/message/244347 – keno Jul 1 '10 at 18:38 No, I tried the setting but the Simulator executable generated by "Base SDK Device/Simulator 4.0" does not work at all, i.e.

Table do not scroll, map does not pan, etc. For example it has also another problem e.g. The alertView window is put in the wrong position BEFORE the keyboard is popped up: iphonedevsdk.com/forum/iphone-sdk-development/… – lionfly Jul 6 '10 at 14:31.

I find that by fully protecting any OS3.2 code, I can choose to compile as either 3.1.3 or 3.2 simply by changing the Active SDK when I compile. The 3.1.3 will always come up in the iPhone Simulator and the 3.2 will always come up in the iPad simulator. Here's an example of fully protected code: #ifdef UI_USER_INTERFACE_IDIOM if (UI_USER_INTERFACE_IDIOM() == UIUserInterfaceIdiomPad) { // iPad Only Code Goes here deviceType setString:@"ipad"; } else { #endif // iPhone Only Code Goes Here deviceType setString:@"iphone"; #ifdef UI_USER_INTERFACE_IDIOM } #endif.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.