Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Xcode 7.1 "iTunes store operation failed you are not authorized to use this service"

Trying to submit iOS and Apple Watch OS2 extension update from ios 9.0 to 9.1. I recently updated Xcode to version 7.1 and now I'm hitting this problem without changing anything else.

iTunes store operation failed you are not authorized to use this service

What I've tried:

  1. Removed developer account from Xcode -> added developer account back into Xcode -> Still hit the error.
  2. I tried Xcode -> Preferences -> Apple ID -> Download All to get my latest provisioning profiles up to date. Still get the error.
  3. Deleted all old archives, cleaned project, archive again. Still get the error.
  4. Increased build number and version number in both the project and in itunes connect. Still get the error.
  5. Deleted derived data in the Library -> Developer folder and I still get the error.
  6. Cleaned the project -> Archived the project again -> Unchecked "enable bitcode" and I still receive the error.

Code Signing Settings:

  • Watch Target -> Provisioning profile automatic code signing iOS Developer
  • Watch Target Extension -> Provisioning profile automatic code signing iOS Developer
  • iOS Target -> Provisioning profile automatic code signing iOS Developer

Still hit the error message with the provisioning profile settings.

  • Reinstalled Xcode 7.1 -> Still hit the error message.

I've also confirmed that all my developer and distribution provisioning profiles are valid and downloaded.

Observations:

One thing I've noticed is that when I archive the app and look in the Window -> Organizer I notice my iOS apps on the left side for my archives. This app I'm trying to submit has no name next to it. However, if I delete all old archives for this app the app name shows up again next to the app icon. Maybe a bug with Xcode but I have no clue.

Another thing I've noticed is I've been able to successfully submit iOS archives that have no WatchKit extension using Xcode 7.1. I'm not sure if the WatchKit extension could be the problem but it is a possibility.

Also when the archive is ready to be uploaded to iTunes Connect I notice a couple of things. First, the iOS App defaults to the active provisioning profile: "MyApp" Distribution profile. However, both the WatchKit app and app extensions automatically default to the XC* wildcard provisioning profile. I'm not sure if this whole problem could just be related to a provisioning profile error but it is possible.

iOS Target -> Build Phases -> Embed Watch Content is set as:

$(CONTENTS_FOLDER_PATH)/Watch

Application Loader Submission Attempt:

Tried and failed with the following error message:

ERROR ITMS-90171 "Invalid Bundle Structure - The Binary file 'MyApp.app/Watch/MyAppWatch.app/_WatchKitStub/WK' is not permitted. Your app can't contain stand alone executables or libraries other then the CFBundleExecutable of supported bundles. Refer to the Bundle Programming Guide..."

Again, I used this exact same project structure to submit the ios app and watchkit OS2 extension on Xcode 7.0 ios 9.0.x no problem. I think the error message is inaccurate unless I'm misconfiguring something but I imagine I would've hit the error back on Xcode 7.0

Any help on how to solve this would be awesome. I've found no help googling and reading other SO posts and I've been stuck on this for far too long. Thanks!

like image 926
zic10 Avatar asked Oct 24 '15 03:10

zic10


2 Answers

I met the same issue today and I think it is a bug of Xcode 7.1

Finally I managed to submit my app via Application Loader. There were warnings but it did work.

Here are the basic steps:

  1. Archive
  2. Export
  3. Xcode menu --> Xcode --> Open Developer Tool --> Application Loader
  4. Double click "Deliver Your App" and choose the file exported in step #2
  5. click next and follow the instructions until the end
like image 103
Tyler Liu Avatar answered Oct 23 '22 23:10

Tyler Liu


I found the solution by unchecking the Include bitcode option.

Uncheck include Bitcode

like image 41
Nishant Avatar answered Oct 23 '22 21:10

Nishant