Skip to main content

Upgrading to xCode 6.4

After you upgrade to xCode 6.4 you will notice that the SDK for iOS 7.1 is no longer available. If you still want to be able to build for iOS7 and run a simulator for iOS7 then you will need to do a little bit of manual work.

First if you go to Preferences --> Downloads within xCode you should see a component listed for the iOS 7.1 simulator.  Click on the download arrow in order for it to be downloaded and installed.

However you will notice that there is no download for the base SDK for 7.1.  You will need to manually install it in order for it to be available to xCode 6.4.

You will want to check and confirm what SDKs are actually installed.  You can check by opening a terminal on your MAC and then proceeding to the directory /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs.

If you do not see a folder for iPhoneOS7.1.sdk you will want to extract a copy of the SDK into your Xcode SDK directory structure.  You could either attempt to copy a version from an install of xCode 5.1 or you can search the web for publicly available copies of the SDK.  Here is one I found download here .  Once you have the download, copy the SDK folder, iPhoneOS7.1.sdk to the SDKs directory indicated above.

Note: Make sure the permissions are appropriate on the folder.  Check the permission on the other SDK folders and replicate both the owner and group if necessary.

Once you have it in place restart/start xCode.  You should now be able to select from either the 8.x or 7.1 SDK now when building or running from within xCode.

Comments

Post a Comment

Popular posts from this blog

Where to start on AngularJS for Java Developer

Background: If you are a Java developer who is comfortable using Eclipse (JEE Developer version) you may be asking yourself where to start with AngularJS. There is all kinds of documentation out there in regards to AngularJS and https://angularjs.org/ provides, to the point, tutorials on how to get started. You can certainly go that route and use node.js embedded server and possibly a Javascript focused IDE like WebStorm. However I wanted to try and stay in a comfort zone, my comfort zone, of Eclipse and be in a position to deploy an Angular application to a container like Tomcat. This blog entry will present the trail I took to try and accomplish it. Note: This is an adventure into Angular 1.x, not 2.x.  I would imagine this could all work with 2.x as well as it is focused on the dev environment setup. Start: Well the one consistent thing you will find to get started is to install the AngularJS Plugin, provided by Angelo ZERR.  You can use the Eclipse 4.5 (Mar...
18 comments
Read more

WSO2: Simple Pass through proxy (REST to REST with HTML Reply)

Today I set out on trying to set up a simple passthrough proxy that would allow for a GET request to be made to REST style backend services that replies with HTML content. The proxy services was being set up on WS02 ESB v4.8.0.  I thought this was really going to be as simple as walking though their wizard and setting up a new proxy endpoint that just handed off to the behinds the scene service. It was straight forward to set up the proxy, but then unfortunately when called it just didn't respond. It took quite awhile to figure out what the issues was.  At first I was using the ESB admin console and review the System and Application Logs.  The Application Logs were certainly more useful, but they still truncated stack traces which made it hard to clue in on the real issue. It wasn't until I went and review the logs on the server that I was able to detect the cause.   <wso2_esb_root>/repository/logs/wso2-esb-errors.log 2015-03-19 16:09:43,00...
2 comments
Read more

Database Leak: getConnection() within Spring Transaction

I recently encountered an issue where one of my teammates was experiencing an issue where an application datasource would periodically become exhausted.  After discussing it a few times, we hypothesized that it was a situation where there was a database connection leak.  It was suspected the leak was within boundaries of some application code with a low call rate.  This would line up with, why the application would run for an extended period and then all of a sudden max out its database connections. By inspecting the logs around the times of the database connection pool becoming exhausted it became pretty clear the potential location of the problematic code. The cause of the issue was not a result of necessarily bad code writing, but more of a case of not knowing how legacy semantics would work within the context of a spring transactional boundary. The semantics of how a call to DataSource.getConnection() behaves within the Spring transaction boundary is probably not ...
Post a Comment
Read more