<p>Since Xcode 9, Apple provides automatic code signing identity management from the command line by using the xcodebuild command.</p>
<p>Using the &#8220;allowprovisioningupdates&#8221; flag, you can enable code signing; however you may get errors like:</p>
<ul>
<li>Your session has expired. Please log in.</li>
<li>The operation couldn’t be completed. Unable to log in with account</li>
<li>There are no accounts registered with Xcode. Add your developer account to Xcode</li>
<li>No profiles for &#8216;ID&#8217; were found: Xcode couldn&#8217;t find any iOS App Development provisioning profiles matching &#8216;ID&#8217;</li>
</ul>
<h3>Some possible solution points for the xcodebuild -allowprovisioningupdates error are as follows:</h3>
<h4>1. Access to the Apple Developer Account:</h4>
<p>It&#8217;s likely that your machine cannot connect to the Apple Developer Portal for some reason such as internet connectivity problems or invalid Apple credentials. In such a case, you can check your connection to developer.apple.com and if it is working, make sure that your correct credentials are entered in the build machine.</p>
<h4>2. Certificate type checks:</h4>
<p>It is also possible that the certificate type is causing conflicts with the <em>allowprovisioningupdates</em> flag. This may happen with in-house/enterprise certificates. In such a case, you can try to change the certificate type or use another developer account with the App Store Distribution</p>
<div class="post-content" tabindex="-1" data-post-id="328090022" data-post-type="ANSWER" data-action="content-post-body-content" data-focus="mouse">
<p>Therefore the answer seems to be that we shouldn&#8217;t be using automatic signing for in-house/enterprise distibution, but instead only for App Store deployments.</p>
</div>
<div>
<h4>3. Using a mobile CI/CD tool:</h4>
<p>Actually, the best solution may to use a specialized tool for iOS CI and CD. Tools like Appcircle automate the full build and sign process in the cloud, even without the need for a Mac.</p>
<p>You can use the <a href="https://docs.appcircle.io/signing-identities/ios-certificates-and-provisioning-profiles" target="_blank" rel="noopener noreferrer">signing identities module in Appcircle</a> to manage your iOS certificates and provisioning profiles centrally instead of depending on the automatic management provided by Apple.</p>
<h4>4. If nothing else works, removing and readding the Apple Developer account may also work:</h4>
</div>
<div>The following steps may also help with the error (though using a mobile CI/CD tool is still preferable):</div>
<div>
<ol>
<li>Remove the developer account in the preferences section of Xcode</li>
<li>Quit Xcode</li>
<li>Launch the terminal and use the following command to set the preference to not use the keychain service: <code>defaults write com.apple.dt.Xcode DVTDeveloperAccountUseKeychainService_2 -bool NO</code></li>
<li>Launch Xcode and readd the developer account</li>
</ol>
</div>


Save time, reduce costs and increase developer productivity now.

Solutions to the “xcodebuild allowprovisioningupdates” Error

Related Posts

Transforming Appcircle’s Enterprise App Store into Alternative App Marketplaces with Apple Sideloading

iOS Code Review Practices for Efficient Pull Requests

Re-Signing App Binaries Made Easy with Appcircle

Automate App Store Deployment to App Store, Google Play, and Huawei App Gallery with Appcircle

Solutions to the “xcodebuild allowprovisioningupdates” Error

Related Posts

Transforming Appcircle’s Enterprise App Store into Alternative App Marketplaces with Apple Sideloading

iOS Code Review Practices for Efficient Pull Requests

Re-Signing App Binaries Made Easy with Appcircle

Automate App Store Deployment to App Store, Google Play, and Huawei App Gallery with Appcircle

Subscribe to Appcircle Circle