Is it possible to update iOS simulator to the latest version of iOS? Now it is 7.0.6, but my simulator is 7.0.3, I have XCode 5.0.2 and updated all downloads in Preferences.
Apple has not released any further 7.0.X SDK than 7.0.3. The reason for that is because the API has not changed, and neither has behavior changed significantly enough to warrant a new SDK release. 7.0.6 in particular is only a security update and would not be applicable to the simulator at all; the simulator uses the underlying OS X infrastructure for network connections. You should wait for the upcoming OS X security fix.
You can, however, download beta releases of Xcode 5.1 with 7.1 beta SDK, and make sure your app is ready for the upcoming iOS 7.1 release.
the simulator is definitely still vulnerable to gotofail even on macs that have been updated with the security fix. this is easily testable by using it to browse to gotofail.com on osx 10.9.2: https://twitter.com/visnup/status/444992820915363840
Related
I am not using beta Xcode software. I have always been able to submit to the app store regardless of mac osx version, as long as I used the latest GM Xcode release. All of a sudden, from what I can tell, a few days ago itunes connect is now failing when submitting for review.
Before you respond by "You cannot use beta software to submit applications to the app store" please read the official copy from Apple.
Submitting Apps Apps that are created using beta versions of Xcode or
that are built for beta versions of operating systems will not be
accepted on the App Store and Mac App Store. Apps that you submit
should be developed using the latest version of Xcode from the Mac App
Store and should be built for publicly available versions of iOS, OS
X, and watchOS — except when GM seeds are available. When a GM Seed of
Xcode becomes available, use it to develop your app for submission.
When GM seeds of iOS, OS X, or watchOS become available, build your
app for these versions.
Nowhere in this text requires you to build ON publically released versions of OS X, and has never been the case.
Radars filed #22116787 and #22116676
Xcode 6.4 is no longer supported on El Capitan.
I can't even launch Xcode 6.4 on El Capitan anymore.
How can I obtain and use 10.6 as base SDK in Xcode 4.5.2?
I downloaded Xcode 4.5.2 from the Mac App Store (through a link on the Apple developer site).
Is there a way I can somehow download the 10.6 SDK separately and start using it as a base SDK?
Strangely enough, I can download the documentation for the 10.6 SDK through Xcode's Preferences window, but not the SDK itself. Any ideas?
No, you can't download the 10.6 SDK separately.
Is there a reason you can't use the 10.8 or 10.7 SDK?
Keep in mind that just because you build against the 10.8 SDK, that doesn't mean you can't also have that built application work on 10.8, 10.7 and 10.6. (This is often a cause of confusion among new developers). You control backwards-compatibility through the Deployment Target setting like shown in the image below.
By default, the deployment target is generally set to the same version of OS X as the SDK is, but changing it to 10.6, for example, should allow it to run on a machine with OS X 10.6. (Of course, you should really test to make sure that's the case).
Download xcode with MacOSX10.6.sdk. Now copy MacOSX10.6.sdk inside /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs
Its also working fine with Xcode 5.0.
I have developed an ios4 app and now want to upgrade it to ios5. What are the sort of things i need to be aware of in terms of the switch being successful and not causing any pains? My most important question is that if i do push a new change to apple, what will ios4 users see when an upgrade is available that supports only ios5 and up? Can they just ignore that update and continue using the ios4 version they had installed? Will the appstore error out if they try to download the ios5 upgrade anyway? What exactly will happen?
Thanks
The biggest change in IOS 5.0 is the ARC project, so if you converted it to ARC it won't work with older devices like 3g (3gs can have ios 5.0 so it's safe).
Other than that, a user that has an iOS 5.0 device (or an upgraded one) would be able to get the update as soon as it is made available from apple store.
Keep in mind that lower end ios 5.0 devices might not have enough memory for the application though, it's the same that applies for ios 3 / ios 4 and sequentially ios 5/ios 6.0.
I need to debug a crash that happens at a fundamental part of the app experience on a particular iOS version, but when I use the (newer) dev tools for that version, the crash does not occur.
How can I get a GDB session on version of an app that was installed with another SDK version?
See if you can build the app in Xcode 4.1 and deploy it to an iOS 5.0 device via TestFlight: https://testflightapp.com/
Ok, there have been some questions alluding to this before, and I've even read some second-hand reports of people successfully doing this, but so far I haven't found a concrete answer.
Basically, I want to build an application for simulator using iOS 4.x, and then run it on a 3.x simulator.
I have both SDKs installed, so all I need is the last mile of getting the app to show up in the 3.x simulator.
I tried just copying the app across from Library/Application Support/iPhone Simulator/4.2/Applications to Library/Application Support/iPhone Simulator/3.0/Applications but it doesn't show up when I load the 3.x simulator. There's a binary plist called applicationstate.plist, which I'm guessing keeps track of what apps are installed on the simulator, but I don't know what the binary format is so I'm kind of stuck at this point.
Has anyone managed to load a 4.x app onto a 3.x simulator? And if so, how did you do it?
Why are you even trying to do this? What are you trying to achieve? If what you really just want to do is ensure the app works on iOS 3.x then simply state that in xcode and don't worry about the actual simulator. The simulator could be running iOS 5.0 for all you should care as long as you have set 'iOS Deployment Target' to '3.0' in xcode's project settings. That will ensure the application is compatible with iOS 3.x and above. Obviously you then still need to ensure you're not calling methods from SDK 4.x when it will run on an iOS 3.x device. If that is what you're trying to test then what you're doing won't actually work. You should (as Apple advises) always grab hold of a real device running the target firmware version and test it on that. Grab an old iPod for example with iOS 3.x and try testing your app on that to ensure you haven't called iOS 4.x methods when running under an older firmware.
The answer is: No, you cannot build for 4.x simulator and run on a 3.1.x simulator or earlier due to fundamental changes in the way the simulator works.
The only way to test 3.x support is to either run it on a 3.x device (after setting min deployment target), or build on an older xcode that supports 3.x simulator (which isn't feasible if you use Xcode 4, except for iPad 3.2).
Note: Setting the deployment target does not test compatibility with older operating systems. It's the operating system that it actually RUNS on that matters (such as "iPhone 4.3 Simulator", "iPhone 4.0 Simulator", "iPad 3.2 Simulator", or an actual device).
Of course, now that 3.x users make up less than 10% of the total population, it's not really worth the trouble to support it anymore.