Today, I update the Xcode4.5 and install it on my computer which has a earlier version Xcode4.3, after installing I open Xcode4.5, when I want to run my app, there is only IOS Device, iPad 6.0 Simulator and iPhone 6.0 Simulator. How can I test my app on both iPhone 4-inch and iPhone 3.5-inch, thank you very much.
Change the setting in the iPhone simulator.
If you app will not will up the entire screen, you are probably missing the Default-568h#2x.png which needs to be 640 x 1136 pixels.
I am just starting to learn programming for the iPhone and I had a very general question.
I was wondering why is it that when I run my program in xcode, even though I am programming for iPhone 5, when I run the "iPhone 6.1 Simulator" instead of a iPhone 5 Simulator and iPhone 4 pops up?
I am on Mac OS X - 10.7.5
And Xcode version 4.6
Could it be because the apple id I used to download xcode with only has an iPhone 4 and not a 5?
Thanks for the help.
To change your simulator device to other screen resolutions go to Simulator - Device - Retina 4 inch (for iPhone 5) and Retina 3.5 inch for iPhone 4/4S. Use iPhone for iPhone 3GS resolution.
In the Window menu you can change the scale to fit your Mac's screen resolution. (I use 75% for iPhone Retina 3.5 inch).
I also suggest you download iOS 5.1 Simulator if you want to deploy apps for iOS 5.1 and up - it comes really handy and it actually does have some differences from iOS 6.
Choosing "iPhone 6.1 Simulator" is telling Xcode that you want to use the currently selected iPhone simulator with iOS 6.1.
To select the specific iPhone simulator you need to click on the Hardware then Device menu in the simulator.
Your Apple Id and your registered devices have nothing to do with this.
I have been using xcode 4.2 for last 3 months. For last two days it is not showing iPhone simulator .But when we change the device option in iOS simulator to retina display it is showing the simulator .i didn't change any settings of xcode.
As I experienced, in Xcode in the circumtances when the target of the Simulator is iPad but your sample code is in iPhone or the sample code(project) you are trying to compile has been compiled in an old version of iOS (or Xcode) the Simulator doesn't give response. But it still compiles the project and saves it to the main page of iPhone(iPad) simulator.. What you need to do is just compile an iOS 5 project and from main page see your app in Simulator
I just upgraded to iPhone SDK 3.2 Beta 4. Since doing so, I have not been able to get the app to launch in the iPhone simulator - it keeps launching in the iPad simulator. I have tried option-clicking the drop-down menu in the top left-corner of Xcode and setting 'Active Executable' to iPhone simulator 3.1.3 but it keeps going back to iPad simulator instead.
What gives? I have no interest in my app running on the iPad and I don't want to test it in the 2X mode in the simulator.
Thanks,
You can't really launch an iPhone app in 3.2.x - sometimes it will pop up - but basically right now it is only for iPad development.
Update for release version of Simulator.
First of all, the title of this question doesn't match the description: Xcode target isn't the same as the simulator hardware device.
If you are writing an app targeting 3.2, it can run on both iPad (using OS 3.2) and lower OS versions on the iPhone. You do this by setting the Base SDK to iPhone Device 3.2, the Targeted Device Family to iPhone/iPad, and the iPhone OS Deployment Target to 3.1 (lower than 3.2).
The iPhone simulator has a menu option for Hardware->Device, which can be set to iPhone or iPad. However, you can only run a 3.2 SDK target in iPad mode, and a Universal app that supports iPad can only use the 3.2 SDK to build.
You can of course set the simulator to iPhone mode and launch your app from Springboard, but that will lose the debugger connection. Switching mode during installation of your app will cause it to crash.
So the short answer is still the same: you can't run a Universal iPad app in the iPhone mode simulator while debugging.
Upper-left corner of the IDE find a dropdown list of Simulator versions - flipped to 3.2 - try to put it back to 3.1.3
and relaunch your app.
This was driving me nuts too, but the answer is right here:
http://quatermain.tumblr.com/post/517122761/running-universal-ipad-iphone-apps-in-the-simulator
In short, tell Xcode to Build for the 3.2 SDK, then switch the build menu to the 3.1 SDK and tell Xcode to Run the app. Presto, the app starts in the iPhone simulator!
From Apple's documentation: "iPhone OS 3.2 does not support iPhone and iPod touch devices. It runs only on iPad." There's no way to target 3.2 for iPhone, so there's no Simulator. Ergo, you'll have to wait for iOS 4. Fortunately, that's only 4 days away now... of course it won't support the first generation of iPhone devices, but for all other iPhone users it's a free upgrade. Not sure about iPod Touches.
You should be able to change your target platform in your Project Settings.
Changing the target platform and device makes no difference. It always launches the iPad simulator.
If you switch the simulator to iPhone mode, the app just disappears.
This dev environment is a mess.
Short answer: You can change the hardware setting in the simulator. Hardware->Device
Go to Project
Set Active Executable
There are 2 options: Ipad Simulator 3.2 or Iphone Simulator 4.0.
If you choose the Iphone simulator, then it will launch Iphone simulator.
If you choose the Ipad simulator, then it will launch Ipad simulator.
I finally solved this problem myself.
First, install new version of xCode, which is xCode 4.
Then set project scheme to iphone simulator and run app in xCode several times.
And re-install xCode 3 and the problem will be gone away!
i've installed new sdk 3.2 pre-release wich have iPad simulator, i have tried to launch an iPhone app created by me in iPad simulator; the main view of this app has an image as background; when launch it on iPad simulator this background(self.background = [[UImage..... ) it comes inverted, from top to bottom.
Any idea??
thanks in advance....:)
This was an early bug in the SDK, which was fixed somewhere around Beta 3.