title: Xcode 13 - Cannot Submit Archive - Errors occurred while locating signing assets
body: <p>This issue only started after updating to Xcode 13. Never had it under 12.x and no other changes. I am tying to send an Archive to Appstore Connect for a client. I have the &quot;App Manager&quot; role which has always been enough for this activity. However, when trying to send or even validate in Xcode, I receive an error related to &quot;locating signing assets&quot; with the log indicating the following:</p>
  <blockquote>
  <p>2021-10-02 18:18:38 +0000 [MT] Failed to locate signing assets with
  errors: (
  &quot;Error Domain=DeveloperAPIServiceErrorDomain Code=5 &quot;Communication with Apple failed.&quot;
  UserInfo={IDEDistributionIssueSeverity=3,
  NSLocalizedRecoverySuggestion=You are not allowed to perform this
  operation.  Please check with one of your Team Admins, or, if you need
  further assistance, please contact Apple Developer Program Support.
  <a href="https://developer.apple.com/support" rel="nofollow noreferrer">https://developer.apple.com/support</a>,
  NSLocalizedDescription=Communication with Apple failed.}&quot;,
  &quot;Error Domain=IDEProfileLocatorErrorDomain Code=1 &quot;No profiles for 'com.company.app' were found&quot;
  UserInfo={IDEDistributionIssueSeverity=3, NSLocalizedDescription=No
  profiles for 'com.company.app' were found,
  NSLocalizedRecoverySuggestion=Xcode couldn't find any iOS App Store
  provisioning profiles matching 'com.company.app'.}&quot; )</p>
  </blockquote>
  <p>I have tried to remove my account from Xcode and re-add, but to no effect. Again, I have had the App Manager role forever and never had a problem until upgrading to Xcode 13. I was thinking of having him elevate me to &quot;Administrator&quot; but that really should not be necessary. I also created a new distribution cert through Xcode (no errors there) but that didn't help either.</p>
  <p>As an update. I went the manual route and created a profile and chose to select it manually rather than having Xcode handle it automatically. That worked. However, of course it should not have to work that way and I still don't understand why the automatic method is failing.</p>
  <p>Anything else I can try?</p>