14

Using Xcode 9.

  1. Working on app store build validation.
  2. Created an app with app store profile.
  3. Archived successfully
  4. Trying to validate build in Organizer, I am getting the following error on selecting the profile.

enter image description here This is the same profile used to archive and it is an app store profile.

2 Queries

  1. How to identify a profile if it is ad-hoc or app store
  2. Why did this happen?Pretty sure this is an appstore profile.
Lithu T.V
  • 19,955
  • 12
  • 56
  • 101

4 Answers4

6

Just had the same issue

All you need to do is to delete your provisioning profile and create another one on Apple Developer site.

Queries:

  • 1) The only info we have about it is the Development or Distribution label on the profile itself
  • 2) I can't say it for sure, but maybe Xcode 9 signing doesn't recognize old profiles the same way it once did.
Rubens
  • 95
  • 4
4

If all else fails try using the Application Loader. I almost just default to the Application Loader nowadays with how ridiculously buggy the Xcode upload process is version after version.

Aaron
  • 6,466
  • 7
  • 37
  • 75
  • Thank, try to upload adhoc build using XCode but cannot success and got the error "Profile is not an iOS App Store profile". Now I have to use Application Loader. – haisergeant Jan 08 '18 at 03:28
  • After uploading successfully, I got email from Apple states that "Invalid Swift Support - The SwiftSupport folder is missing.". So weird. – haisergeant Jan 09 '18 at 01:03
3

I think you are selected Ad Hoc option to get .ipa file. Select App Store option to get the .ipa file, then use Application loader to submit .ipa file.

In my case i'm getting email like this...

Missing beta entitlement - Your app does not include the beta-reports-active entitlement. If you intend to distribute this build via TestFlight for beta testing, please re-build this app with an App Store Distribution provisioning profile. Do not use ad-hoc profiles.

After you’ve corrected the issues, you can use Xcode or Application Loader to upload a new binary to iTunes Connect.

Regards,
The App Store team

Then i changed the option from Ad Hoc to App Store... enter image description here

lyankar
  • 33
  • 4
0

In my case I always trying to avoid revoke Apple cert, because I share it with different developers from my company.

So I follow this answer which suggest to downgrade Xcode -> I check version 9.0.1 and unfortunately I have still same error message.

But I've installed additionally 8.3.3 - it works correctly with uploading to Apple store.

Update: I move back into Xcode 9.1installed directly from App Store, because I have problem with run ionic cordova build

So at this moment I am using two Xcode versions:

  • 9.1 - for testing and creating builds - directly in Application
  • 8.3.3 - for uploading build to iTunnes Connect - beside run from different folder

I hope this is temporary situation.

[Update]

After some time I realized that my Provisioning Profile start with XC which is not accepted by Xcode 9+. After refresh all my Provisioning Profiles (avoiding XC in name) - I can finally use Xcode 9+.

Maybe this can be also useful for those who straggle this problem.

dannydedog
  • 459
  • 1
  • 6
  • 15