views:

280

answers:

2

iPhone Apps built for the simulator are stored here:

/Users/<username>/Library/Application Support/iPhone Simulator/User/Applications

Is it possible to copy the <GUID>.sb and <GUID> directory and install them on a different computer (with Development tools installed)?

This would be very useful for testing/demoing with out having to buy iPhones for all the managers and external clients.

+3  A: 

Yes, if you send those files to another person, and they put them into that directory, they can test the applications in the iPhone Simulator as well :)

AriX
+2  A: 

I found a way that requires just a little more setup, but is much easier for non-developers:

Instructions for your users/testers:

  1. Install Xcode following Apple's instructions
  2. Double-click the attached application - the iPhone simulator will launch, install the app and start it automatically.

How to set it up:

  1. Download and unzip (to a folder on your desktop or wherever) 'Simulator Bundler' from: http://github.com/landonf/simlaunch/downloads
  2. Do a 'Build and archive' in Xcode
  3. Find it: select 'Archived applications' in the Organizer, right click the relevant build, select "Reveal archived application in Finder"
  4. Drag the application (yourAppName, no extension) onto the Simulator Bundler app

Done. This will create a self-contained Mac OS X yourAppDisplayName.app file in the same folder (with your app's icon as the icon - though for some reason you have to run it once for the icon to appear) that you can stick up on an FTP server or email to your users/testers.

--

I think it's much neater/slicker than having to explain where to copy files, how to launch the simulator and so on.. And if anything gets messed up they can just uninstall from the simulator and double-click the icon again.

You can also very easily produce builds with different bundle identifiers, so that you can send two or more slightly different builds that can be installed side-by-side for comparison; say for getting some user feedback on different structures of your menu system, or so you can have two builds that are otherwise identical but pointed at your Live and Staging/QA servers, so your team can check recent content changes before they go live or whatever..

It's also very convenient for localisation testing: launch the simulator, uninstall the app if present, set the required region format and language, double click the icon on your desktop, test; repeat for each required locale. (guarantees a fresh install each time, I've found that switching language with the app installed can result in all sorts of strange behaviour)

dsmudger