问题
Transporter not found at path: /usr/local/itms/bin/iTMSTransporter.
You should reinstall the application.
So I checked the path /Applications/Xcode.app/Contents/Applications/Application Loader.app/Contents/MacOS/itms/bin and iTMSTransporter exists there (where it is installed with xcode). The path given to me in the error is where transporter is installed if you install it manually. How do I make it so that when I try and submit my app xcode organizer uses the path were iTMSTransporter is installed through xcode? I'm baffled why it is doing this in the first place.
回答1:
I had the same problem and made a symlink from the location XCode expected the iTMSTransporter to the location in the Applications folder you mentioned:
ln -s /Applications/Xcode.app/Contents/Applications/Application\ Loader.app/Contents/itms /usr/local/itms
However, when uploading my binary I get the error:
[ERROR ITMS-90209: "Invalid Segment Alignment. The app binary at 'MyApp.app/Frameworks/libswiftCore.dylib' does not have proper segment alignment. Try rebuilding the app with the latest Xcode version."
Digging some deeper into Console.app, I found the following error message:
DBG-X: The error code is: 1102
INFO: Done performing authentication.
INFO: The following info messages were received from Apple's web service ...
INFO-X: INFO ITMS-90111: "Your app is built with a beta version of Xcode or iOS SDK. Only apps distributed for beta testing may be built with beta software. To submit an app for distribution on the App Store, you will need to build the app with release versions of Xcode and iOS SDK."
DBG-X: Returning 1
But I haven't figured out a way to tell XCode that uploading for beta testing is exactly what I'm trying to do.
回答2:
Basically what the above answer stated but the symlink command was wrong for me. I used the following command to fix it:
ln -s /Applications/Xcode.app/Contents/Applications/Application\ Loader.app/Contents/itms/ /usr/local/itms
来源：https://stackoverflow.com/questions/28461768/xcode-organizer-trying-to-access-transporter-at-wrong-directory-path