Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to test the release build on device with Xcode 4.2?
    text
    copied!<p>I've just finished writing an update for my app, and now I want to submit it to the app store.</p> <p>I've thoroughly tested it in debug mode on multiple devices, but I want to test it with the release build just to make sure nothing screws up.</p> <p>In Xcode 4.0.2, when I wanted to <strong>test</strong> the release build (i.e. not distribute), I would just do the following</p> <ol> <li>In the project settings, make sure that the release code signing is set to "iPhone Developer" not "iPhone Distribution"</li> <li>Go to <code>Edit scheme...</code>, and change the <strong>Run</strong> scheme to <strong>Release</strong> instead of <strong>Debug</strong>.</li> <li>Make sure my distribution provisioning profile is installed in Xcode</li> <li>Run it on the device, make sure everything works.</li> </ol> <p>If it all works, I would then distribute with the following:</p> <ol> <li>Change the code signing to "iPhone Distribution"</li> <li>Make sure the <strong>Archive</strong> scheme is set to <strong>Release</strong></li> <li>Archive</li> <li>Submit</li> </ol> <p>Now the problem is, with Xcode 4.2, I can't test the release build on my device. - When I build it with release to my iPod, I get an alert:</p> <blockquote> <p>A valid provisioning profile for this executable was not found.</p> </blockquote> <p>So, I checked my provisioning profiles under the main "Library" section of the Devices pane (all provisioning profiles), and I found my distribution profile there.</p> <p>The problem is, the provisioning profile says <strong>"This profile cannot be installed on deivces"</strong>.</p> <p>So, if I can't use the distribution profile with a device - how am I supposed to test the release build?</p> <p>I would appreciate any advice with this issue - sorry if there's something obvious I'm missing!</p>
 

Querying!

 
Guidance

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