There are lots of excellent improvements in the build area, especially the handling of the many provisioning profiles! 
Had hopes for this one - I guess it’s not top priority, just wondering if a bug is filed already. I’m on “latest everything”.
Screenshot in attachment.
There is a standalone version of Application Loader that has the tools needed to send the files to Apple. You must install it separately if you want to use this feature. Click on the blue text to take to you where you can install it. The message should have explained the problem.
Rob
Well, since I’m on latest everything and clicking the link just opens the already installed Application Loader 3.0, it still leaves me wondering what I’m supposed to do to make it work.
It’s also not obvious that you would want to use any other Application Loader version than that which matches the XCode version you’re using. I went hunting for a later version of AL anyway, but Apple has hidden it further. There used to be a link at the bottom of the My Apps page in iTunes Connect, but now it seems any landing page that is about Application Loader that has a link to the latest version is unfindable on the Web. The closest I’ve gotten is to manually modify the direct link here to end with 3.1, which actually downloads a .dmg.
To help others, to get 3.0 log in to iTunes Connect, then Resources and Help > Apps > Scroll to bottom, click View Tools. On this page is what seems the only download link for it.
I could try 3.1 on a whim, but since that last page says the latest version is 3.0, I’m hesitant.
I guess this trouble turns it into a complaint about lagging documentation, which is Apple’s fault and not yours. So what remains is the assumption that you should install 3.0 again on a system that already has it, and that this will install any missing tools. Is that correct?
The Corona console says
okt. 08 08:45:25.788: iOS build succeeded
Using Xcode utilities from /Applications/Xcode.app/Contents/Developer
Building: Validating application with iTunes Connect
Building: Uploading application to iTunes Connect
okt. 08 08:45:41.880: PACKAGING ERROR: upload failed: Transporter not found at path: /usr/local/itms/bin/iTMSTransporter. You should reinstall the application.
I encountered this exact issue yesterday. I then realized that I have three versions of Application Loader installed:
3.0 - which was installed as a separate download from Apple circa Xcode 6
3.1 - which is bundle installed with Xcode 6.4 (which I’m still using to support another development framework we’re using)
3.2 - which is bundle installed with Xcode 7.0.1
I ended up just dragging the .ipa into AL 3.2 and it successfully transmitted to iTunesConnect. But yes, the error message is confusing and yes, I’m unable to solve the problem so that it all works turnkey as desired.
The version of AL that ships with Xcode does not have the tools we are trying to use to automate the upload to the store for you. This comes with the standalone version which can be installed from the Apple OS-X App Store. I don’t believe there is an issue using the Standalone version.
I’ve submitted apps using Xcode 7 and the standalone Application loader. Of course you could choose to not have Corona automatically upload it for you and just output an ipa file and upload it yourself.
Rob
FYI - the latest officially available standalone version of Application Loader is 3.1 available here: https://itunespartner.apple.com/en/apps/tools (you will need to log into your iTunes Connection account.) Please note that the link is incorrectly described as AL 3.0 but the file (.dmg) that is downloaded is actually version 3.1.
After installing AL 3.1 standalone, I was able to successfully use the Upload to App Store option in the Build for iOS dialog.
I just did a build and received this error messages:
ERROR: upload failed: Transporter not found at path: /usr/local/itms/bin/iTMSTransporter. You should reinstall the application.
This may be an Xcode issue which is most easily worked around by opening Application Loader and managing your app manually.
I just downloaded Application Loader from iTunes Connect and attached an .ipa file to it and uploaded to the App Store manually using Application Loader. Now it says it is Uploading package to the iTunes Store so I guess it is taking it.
Thanks
Lori
Manually uploading works. Though it would be good to solve your issue so you can upload from Corona SDK directly.
Rob
The updater doesn’t update Application Loader when you update XCode if any version of AL is previously installed.
If you uninstall AL and install XCode, it will be set up so that it finds the transporter path.
Edit: Wanting Corona to upload to App Store seems counter to wanting to use the latest version of AL (3.3) which comes with XCode, though. (Tested on latest daily build, 2015.2775). The link to the standalone AL 3.1 is still incorrect in the dialog that pops up. Clicking the Application Loader link in the popup still just opens Application Loader (3.3 in my case).
Edit 2: Uninstalling AL 3.1 and (re)installing XCode 7.1.1 sets up the paths correctly as per original post error. But then you get AL 3.3, which Corona doesn’t recognize as usable for Upload to App Store, warning again. But by installing 3.1 again separately, Corona reports Upload to App Store as successful!
Does Anyone know what this error message means?
ERROR: upload failed: Transporter not found at path: /usr/local/itms/bin/iTMSTransporter. You should reinstall the application.
This may be an Xcode issue which is most easily worked around by opening Application Loader and managing your app manually.
I can’t upload using Corona until I know what this message means so I can fix the problem.
Thanks
You can manually run Application Loader and upload your app. The message has to do with Corona wanting to run a file that gets installed as part of the stand-alone Application Loader install. Henrik above suggested uninstalling application loader and uninstalling then reinstalling Xcode to get the right files installed.
Also you can try to hand install Application Loader: https://itunespartner.apple.com/en/apps/tools
Rob
Application Loader has its issues. The command line interface of some versions works, some don’t and it’s definitely not the case that the latest is always the best.
Many people can arrive at a set up which lets them use the “Send to App Store” option in the Corona Simulator but sometimes it just doesn’t seem possible to align the ducks correctly to make this work and you’re better off just running it manually. The bug has been reported to Apple but who knows when it might be fixed.
There is a standalone version of Application Loader that has the tools needed to send the files to Apple. You must install it separately if you want to use this feature. Click on the blue text to take to you where you can install it. The message should have explained the problem.
Rob
Well, since I’m on latest everything and clicking the link just opens the already installed Application Loader 3.0, it still leaves me wondering what I’m supposed to do to make it work.
It’s also not obvious that you would want to use any other Application Loader version than that which matches the XCode version you’re using. I went hunting for a later version of AL anyway, but Apple has hidden it further. There used to be a link at the bottom of the My Apps page in iTunes Connect, but now it seems any landing page that is about Application Loader that has a link to the latest version is unfindable on the Web. The closest I’ve gotten is to manually modify the direct link here to end with 3.1, which actually downloads a .dmg.
To help others, to get 3.0 log in to iTunes Connect, then Resources and Help > Apps > Scroll to bottom, click View Tools. On this page is what seems the only download link for it.
I could try 3.1 on a whim, but since that last page says the latest version is 3.0, I’m hesitant.
I guess this trouble turns it into a complaint about lagging documentation, which is Apple’s fault and not yours. So what remains is the assumption that you should install 3.0 again on a system that already has it, and that this will install any missing tools. Is that correct?
The Corona console says
okt. 08 08:45:25.788: iOS build succeeded
Using Xcode utilities from /Applications/Xcode.app/Contents/Developer
Building: Validating application with iTunes Connect
Building: Uploading application to iTunes Connect
okt. 08 08:45:41.880: PACKAGING ERROR: upload failed: Transporter not found at path: /usr/local/itms/bin/iTMSTransporter. You should reinstall the application.
I encountered this exact issue yesterday. I then realized that I have three versions of Application Loader installed:
3.0 - which was installed as a separate download from Apple circa Xcode 6
3.1 - which is bundle installed with Xcode 6.4 (which I’m still using to support another development framework we’re using)
3.2 - which is bundle installed with Xcode 7.0.1
I ended up just dragging the .ipa into AL 3.2 and it successfully transmitted to iTunesConnect. But yes, the error message is confusing and yes, I’m unable to solve the problem so that it all works turnkey as desired.
The version of AL that ships with Xcode does not have the tools we are trying to use to automate the upload to the store for you. This comes with the standalone version which can be installed from the Apple OS-X App Store. I don’t believe there is an issue using the Standalone version.
I’ve submitted apps using Xcode 7 and the standalone Application loader. Of course you could choose to not have Corona automatically upload it for you and just output an ipa file and upload it yourself.
Rob
FYI - the latest officially available standalone version of Application Loader is 3.1 available here: https://itunespartner.apple.com/en/apps/tools (you will need to log into your iTunes Connection account.) Please note that the link is incorrectly described as AL 3.0 but the file (.dmg) that is downloaded is actually version 3.1.
After installing AL 3.1 standalone, I was able to successfully use the Upload to App Store option in the Build for iOS dialog.
I just did a build and received this error messages:
ERROR: upload failed: Transporter not found at path: /usr/local/itms/bin/iTMSTransporter. You should reinstall the application.
This may be an Xcode issue which is most easily worked around by opening Application Loader and managing your app manually.
I just downloaded Application Loader from iTunes Connect and attached an .ipa file to it and uploaded to the App Store manually using Application Loader. Now it says it is Uploading package to the iTunes Store so I guess it is taking it.
Thanks
Lori
Manually uploading works. Though it would be good to solve your issue so you can upload from Corona SDK directly.
Rob
The updater doesn’t update Application Loader when you update XCode if any version of AL is previously installed.
If you uninstall AL and install XCode, it will be set up so that it finds the transporter path.
Edit: Wanting Corona to upload to App Store seems counter to wanting to use the latest version of AL (3.3) which comes with XCode, though. (Tested on latest daily build, 2015.2775). The link to the standalone AL 3.1 is still incorrect in the dialog that pops up. Clicking the Application Loader link in the popup still just opens Application Loader (3.3 in my case).
Edit 2: Uninstalling AL 3.1 and (re)installing XCode 7.1.1 sets up the paths correctly as per original post error. But then you get AL 3.3, which Corona doesn’t recognize as usable for Upload to App Store, warning again. But by installing 3.1 again separately, Corona reports Upload to App Store as successful!