StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Apple provides an easy solution to working on multiple machines.</p> <p>You can <a href="http://developer.apple.com/library/mac/#recipes/xcode_help-devices_organizer/articles/export_signing_assets.html" rel="nofollow noreferrer">export your developer profile</a> from your work iMac and move it onto your Macbook Pro. </p> <ol> <li><p>In Xcode 4, bring up the Organizer. Click on "Devices"/</p></li> <li><p>Now, click on "Developer Profiles" in the sidebar. </p></li> <li><p>Then, on the bottom of the screen you will see a button called "Export" and a button called "Import". On the computer with the original certificates click "export" and save the profile. You may be prompted to enter a password. </p></li> <li><p>On the second computer, use "import" to install the certificates.</p></li> </ol> <p><img src="https://i.stack.imgur.com/JAOaY.png" alt="Exporting a developer profile"></p> <p>You should be able to develop and test seamlessly between the two machines now.</p> <p><strong>Edit:</strong></p> <p>According to <a href="https://stackoverflow.com/users/85309/topher-fangio">Topher Fangio</a> in <a href="https://stackoverflow.com/questions/7057644/developing-for-ios-on-multiple-computers-testing-on-a-single-device-advice/7057661#comment12810084_7057661">the comments below</a>, you may need to:</p> <blockquote> <p>open Keychain Access, then find [your] iPhone Developer Certificate on my desktop, and export it. Then import it on your [second machine]. If you see the dropdown and associated private key on one machine, but not the other, then you need to export it apparently.</p> </blockquote> <p>Hopefully Topher's insight will help anyone who has trouble with using Xcode to do this.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload