Application Loader: "Cannot proceed with delivery: an existing transporter instance is currently uploading this package"

ItunesApp Store-Connect

Itunes Problem Overview


I have been unable to overcome this error in Application Loader. I've quit, restarted, tried different computers - it's like the server is hung up on an op that I never initiated and it won't time out. Has anyone seen it before and beaten it?

Itunes Solutions


Solution 1 - Itunes

Basically, you need to clear out the transport tokens. This can happen if you were to close out of Xcode while in the middle of submitting an app to iTunes Connect.

The token files now appear in the > Library/Caches/com.apple.amp.itmstransporter/UploadTokens/ subfolder of the given user's home directory. Which, honestly, is a better place for them anyway.

Delete any .token files in this directory.

-- If you are unable to find the .token files, this is because they are hidden in Finder. To hide/show hidden files in Finder, use the following Terminal command (TRUE = UNHIDE, FALSE = HIDE):

defaults write com.apple.finder AppleShowAllFiles TRUE;killall Finder

Solution 2 - Itunes

You need to clear out the transport tokens.

Open Terminal on your Mac, and paste:

rm /Users/<username>/Library/Caches/com.apple.amp.itmstransporter/UploadTokens/*.token

That should clear the stuck token. After this, try uploading the build again.

Solution 3 - Itunes

It might be because Xcode crashed as you were uploading your app. Either, all you need to do is delete the token files:

Open Terminal on your Mac, and paste:

rm ~/.itmstransporter/UploadTokens/*.token

That should clear it. If it still doesn't work (at this point you should try re-uploading your app), run that command on Terminal again, or manually go to...

/Users/<username>/.itmstransporter/UploadTokens/

...and delete all the .token files.

Hope that helps!

Solution 4 - Itunes

token was in here

/Users/(user_name)/Library/Caches/com.apple.amp.itmstransporter/UploadTokens/

Solution 5 - Itunes

Appreciated @WrightsCS 's answer It helps me to overcome Application Loader issue.

I would like to highlight one more thing here.

I proceed as per @WrightsCS answer and it resolved Application loader error:

>Can not proceed with delivery: an existing transporter instance is currently uploading this package

But I found one more issue after removing all tokens from >/Users//.itmstransporter/UploadTokens/

I went to iTunesConnect and clicked on "My Apps", what I saw a message that "Can not connect... please contact Apple".

Here I don't know why it suddenly stops working!

I submitted the same build which was there on iTunesConnect for submission but it has shown as processing.

After submission of that build, iTunesConnect works fine! Also, I am able to see last uploaded build in a list for submission.

Solution 6 - Itunes

In my case (I am using OSX Catalina), I was not able to find the folder:

Library/Caches/com.apple.amp.itmstransporter/UploadTokens/

Under my user home directory (even when showing hidden files and folders)

but it seems my problem was a bit different and I just closed xCode completely (every xCode window opened) and reopened it again then I archived my project and uploaded it without any issues

maybe this could help someone else fix this issue

Solution 7 - Itunes

You need to clear out the upload tokens that are "stuck". To do this, open the tokens file found in /users//.itmstransporter/UploadTokens/. You should see one line of text at the top that refers to your current upload token. Simply delete this line and save the file. You should now be able to submit your app again.

Cheers

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionSG1View Question on Stackoverflow
Solution 1 - ItunesWrightsCSView Answer on Stackoverflow
Solution 2 - ItunesPau SenabreView Answer on Stackoverflow
Solution 3 - ItunesJack SolomonView Answer on Stackoverflow
Solution 4 - ItunesImpactZeroView Answer on Stackoverflow
Solution 5 - ItunesKampaiView Answer on Stackoverflow
Solution 6 - ItunesNoOneKnowsView Answer on Stackoverflow
Solution 7 - ItunesAli HamzaView Answer on Stackoverflow