0

Common question on SO but somehow despite following Apple's Guideline and following the guides for multiple questions on SO, I somehow couldn't get to resolve this issue and couldn't understand the error especially since I had my provisioning and code signing certificates sorted out.

So any help would be appreciated.

Steps I've done until now to resolve the error:

  • Provisioning profiles have been downloaded and validated as per App Store Guidelines
  • Code Signing Identities filled in the 'Build Settings' part of App Settings as shown in screenshot below
  • Revoked and Create New Certificates from Apple Developer
  • I had two accounts in my XCode 5 - Removed the Profile which I wasn't uploading the app to in order to reduce the possible conflicts.

Screenshots from Build Settings of XCode 5 - Current Project

Account Preferences

The following steps reproduce my error:

Error via Distribution using XCode Organizer : No identities are available for signing

  • App archived successfully
  • Click on 'Archive'
  • 'No identities are available for signing shows up'
  • Click on Download Identities > I choose my respective team
  • XCode suddenly quits

Error via Application Loader:

  • App Archived Successfully
  • Click on 'Archive'
  • Choose 'ad hoc or enterprise option'
  • Choose Profile to Sign in with
  • Choose the Team Provisioning Profile associated with Distribution and Development
  • Load ipa into Application Loader
  • Click on 'Send'
  • Application Upload Process start
  • Then I get 'ITMS-9000' error with the following message:

    ERROR: ERROR ITMS-9000: "Invalid Provisioning Profile. The provisioning profile included in the bundle co.xxxxxxxxxxxx.Perinatologie [Payload/Perinatologie.app] is invalid. [Missing code-signing certificate.] For more information, visit the iOS Developer Portal." atSoftwareAssets/SoftwareAsset (MZItmspSoftwareAssetPackage)

The following questions were my resources from SO:`

Community
  • 1
  • 1
stefbmt
  • 111
  • 1
  • 2
  • 14

1 Answers1

0

Question resolved by redownloading an App Store Distribution Profile.

Thanks for the outside perspective. Sometimes being tired doesn't help at all.

stefbmt
  • 111
  • 1
  • 2
  • 14