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

每一次提交，都会在iTunesconnect留下一个构建版本。如果中途上传失败或者上传未成功的话，就会一直是“正在处理”状态。

所以，一般10分钟之后，还没有显示可用的构建版本。那么，你就修改版本号重新上传即可。

"Cannot proceed with delivery: an existing transporter instance is currently uploading this package", In the upload error log I can see that it first gives an warning "Failed to obtain exclusive lock on token file. Please ensure the following file is not locked by another process: C:\Windows\System32\config\systemprofile.itmstransporter\UploadTokens\_vendor_identifier.itmsp.token".

原因：token同名，所以锁定了

解决：修改版本号

I think I've solved my problem, I guess the problem was that I was using same folder name for all the packages, I've observed that the .token file is created with the package folder name as a prefix. So when I made the package folder name unique per package, the transporter created multiple .token files for each of the transport, so no locking issue occurred this time. Earlier I thought the package folder name I was using is a special keyword and should be used as it is, which was a wrong assumption.

翻译：

我想我已经解决了我的问题,我猜这个问题是,我使用相同的文件夹名称的包时,我观察到。创建令牌文件包文件夹名称作为前缀。所以当我包文件夹名独特的每包,多个创建的运输车。令牌文件的传输,所以这次没有锁定的问题发生。之前我以为包文件夹名称我使用是一个特殊的关键字,应该使用,这是一个错误的假设。

http://stackoverflow.com/questions/24884261/executing-multiple-instances-of-itmstransporter