Error in Xcode 12 when trying to upload app binary to App Store Connect

Question

On Mac OS 10.15.7, in Xcode 12.1, when I try to upload my app binary to App Store Connect, I am getting:

"App Store Connect Operation Error: Please update iTMSTransporter to a newer version. (4107)"

I've tried restarting my computer, deleting .itmstransporter, and various other things to no avail.

In the meantime, I've downloaded the Transporter app from the Mac App Store and have been able to submit from there by exporting the binary rather than uploading it to the App Store, but I'd like to regain the functionality in Xcode.

Does anyone have a clue on what may be causing this?

Answer 1

I face the same issues and solved it after execute ./iTMSTransporter -updateChannel earlyAccess on command line.

/Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/Versions/A/itms/bin/iTMSTransporter -updateChannel earlyAccess

or

/Applications/Transporter.app/Contents/itms/bin/iTMSTransporter -updateChannel earlyAccess

Answer 2

I finally was able to solve this. Peeking around my system I found 3 versions of iTMSTransporter. Printing the version of each using ./iTMSTransporter -version gives the following results:

• /Applications/Transporter.app/Contents/itms/bin/ has version 2.0.0

• /Applications/Xcode.app/Contents/SharedFrameworks/ContentDeliveryServices.framework/Versions/A/itms/bin/ has version 2.1.0

• /usr/local/itms/bin/ has version version 1.9.3

So it looks that old version in /usr/local/itms was used by Xcode. After deleting /usr/local/itms I was able to upload my binary within Xcode 12.2 and using the xcodebuild command line tool.

I also deleted ~/Library/Caches/com.apple.amp.itmstransporter but I do not expect that this was the real issue.

UPDATE: This also solved my issue today in Xcode 12.3 where Distribute App and xcodebuild both got stuck in a

authenticating with the app store

Answer 3

I faced it with XCode 13.0, the solution is just to update your XCode to the new released. Also, u can just ignore this warning.