I've been digging around the net to see if there was a simple way to copy a Simulator build from one Mac to another. We basically need a build to work on a different Mac in the office for video capture purposes.
One post I found suggests that it's basically a matter of creating a release Simulator build, deploying it and copying the app's folder from:
We've tried to copy the folder alone, as well as together along with the apps associated .sb file.
We've tried that, but our app hangs on our startup screen when we try to execute the app on another Mac. The app builds and executes fine on the build machine's Simulator as well as on our provisioned devices (iPhone and Touch). We don't believe that there are any file system dependencies in the app.
The secondary Mac's sdk/Simulator version (OS 2.2.1, Simulator V2.2 [v77.4.9]) is basically identical.
There was some discussion on another thread about editing the .plist entry for the app, but it was conclusive as to whether that was necessary.
Anyone have any experience with this? Does the method described above actually work?
Smasher and I were talking about it in a thread. As long as you don't need to edit your app and only want to use it, copying the file should work. The two macs I have are basically mirrors of eachother so that might have been why I was succesful, not sure.
Indeed, I read you and smasher's thread on the subject before posting my question above because I was stumped on why it didn't work for us.
Drat. I guess we'll need to go debug the app and our setups to figure out what's causing our problem. At this point, methink's it a problem with the app, as it will boot and show our title screen but not progress to our loading screen.
If anyone else has experience regarding this matter, any advice would be appreciated!
I'd be interested in knowing a simple solution to this as well. I had terrible trouble just making a copy of a project on the same machine for versioning, but I am going to need to be able to send copies of my working project to my client so they can run it and see progress on two other systems.
FYI - For the versioning, the solution I came up with was to simply keep my current working build the same, in the same folder and the same name, and just make copies of the entire folder and name it for previous versions (ie: Project 001, 002 etc). If I then need to go back to a previous version I rename my current working project as "temp" and then rename an older version back to the current working name. A bit of a hack, but it works.
Copying a Simulator build to another machine?
Linear Mode
