Over a million developers have joined DZone.

Locating Simulator Files in Xcode 6

DZone's Guide to

Locating Simulator Files in Xcode 6

· Mobile Zone
Free Resource

Launching an app doesn’t need to be daunting. Whether you’re just getting started or need a refresher on mobile app testing best practices, this guide is your resource! Brought to you in partnership with Perfecto

With Apple’s release of iOS 8 just around the corner, most developers have already gotten their hands on Xcode 6. Along with the obvious additions of Swift tools and resources, Apple has made a concerted effort to better organize .app files and documents.

Now, when you simulate your app for different devices, Xcode will automatically store the data in separate folders. Many in the community have been requesting this for years, so it’s certainly a welcome change. However, it is obviously important to get an understanding of exactly where your files will be to avoid any loss of productivity.

iOS Developer Tips has been dissecting Xcode 6 since its first beta, and you can find a more in-depth breakdown here. Some of you may be asking why any of this information is relevant. Here's an example:

Knowing the location of the .app file created by Xcode 6 can be helpful if you need to reference the file path. For example, I run UI Automation scripts from a command line (versus within Xcode) – one of the parameters required is the path to the .app file.

The article goes into greater detail about other path changes and how they'll benefit organizing your app development.

What do you think? Is this helpful? Share your thoughts below.

Keep up with the latest DevTest Jargon with the latest Mobile DevTest Dictionary. Brought to you in partnership with Perfecto.


Opinions expressed by DZone contributors are their own.


Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.


{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}