App Store Connect transporter transfer failed about fastlane

[marcoburato-ecutek]

For anyone experiencing this issue on Azure DevOps, I solved this by changing the Release Pipeline agent specification from macOS-latest, which currently is still an alias for macOS-11, to macOS-12.

The macOS-12 spec uses Xcode 14 instead of Xcode 13. In turn, fastlane uses altool (instead of iTMSTransporter) by default for Xcode 14.

altool did upload successfully.

[Marygimm]

Getting also today

ERROR [2022-11-21 18:32:57.04]: Transporter transfer failed.
WARN [2022-11-21 18:32:57.04]: The software asset has already been successfully delivered.

ERROR [2022-11-21 18:32:57.04]: Upload is not in processing state, please try again. state: class Build {

WARN [2022-11-21 18:32:58.65]: The software asset has already been successfully delivered.

WARN [2022-11-21 18:32:58.65]: [iTMSTransporter]             data: null

WARN [2022-11-21 18:32:58.65]: [iTMSTransporter]         }

WARN [2022-11-21 18:32:58.65]: [iTMSTransporter]         buildAssetSpi: class BuildRelationshipsBuildAssetDescription {

WARN [2022-11-21 18:32:58.65]: [iTMSTransporter]             links: class AppAvailabilityRelationshipsAppLinks {

WARN [2022-11-21 18:32:58.65]: [iTMSTransporter]                 self: https://contentdelivery.itunes.apple.com/MZContentDeliveryService/iris/v1/builds/ae1136f1-c30a-4fa4-a093-9ae0d915b278/relationships/buildAssetSpi

WARN [2022-11-21 18:32:58.65]: [iTMSTransporter]                 related: https://contentdelivery.itunes.apple.com/MZContentDeliveryService/iris/v1/builds/ae1136f1-c30a-4fa4-a093-9ae0d915b278/buildAssetSpi

WARN [2022-11-21 18:32:58.65]: [iTMSTransporter]             }

WARN [2022-11-21 18:32:58.65]: [iTMSTransporter]             data: null

WARN [2022-11-21 18:32:58.65]: [iTMSTransporter]         }

WARN [2022-11-21 18:32:58.65]: [iTMSTransporter]     }

WARN [2022-11-21 18:32:58.65]: [iTMSTransporter]     links: class ResourceLinks {

WARN [2022-11-21 18:32:58.65]: [iTMSTransporter]         self: https://contentdelivery.itunes.apple.com/MZContentDeliveryService/iris/v1/builds/ae1136f1-c30a-4fa4-a093-9ae0d915b278

WARN [2022-11-21 18:32:58.65]: [iTMSTransporter]     }

WARN [2022-11-21 18:32:58.65]: [iTMSTransporter] }

WARN [2022-11-21 18:32:58.65]: [iTMSTransporter] [2022-11-21 18:32:57 UTC] <main> DBG-X: Returning 1

INFO [2022-11-21 18:32:58.65]: iTunes Transporter output above ^
ERROR [2022-11-21 18:32:58.65]: Upload is not in processing state, please try again. state: class Build {
Return status of iTunes Transporter was 1: Upload is not in processing state, please try again. state: class Build {
The call to the iTMSTransporter completed with a non-zero exit status: 1. This indicates a failure.
WARN [2022-11-21 18:32:58.68]: Lane Context:
INFO [2022-11-21 18:32:58.69]: {:PLATFORM_NAME=>nil, :LANE_NAME=>"main", :SIGH_PROFILE_TYPE=>"app-store", :MATCH_PROVISIONING_PROFILE_MAPPING=>{"cgd.business.app.main"=>"match AppStore cgd.business.app.main", "cgd.business.app.dev"=>"match AppStore cgd.business.app.dev", "cgd.business.app.test"=>"match AppStore cgd.business.app.test", "cgd.business.app.uat"=>"match AppStore cgd.business.app.uat"}, :IPA_OUTPUT_PATH=>"/Users/runner/work/cgd-mobile-ios/cgd-mobile-ios/CGD.ipa", :XCODEBUILD_ARCHIVE=>"/Users/runner/Library/Developer/Xcode/Archives/2022-11-21/CGD 2022-11-21 18.13.47.xcarchive", :DSYM_OUTPUT_PATH=>"/Users/runner/work/cgd-mobile-ios/cgd-mobile-ios/CGD.app.dSYM.zip"}
ERROR [2022-11-21 18:32:58.69]: Error uploading ipa file:

[LuisFelipe635]

I'm facing the same issue right now

[shaddeen]

providing both team_id and itc_provider resolved the issue for me.

team_id: you can grab here if you're logged into your dev account (under data.associatedAccounts[n].contentProvider.contentProviderId)

itc_provider: your team ID for your apple account, you can find in developer.apple.com portal

(Xcode 13.3)

[marcoburato-ecutek]

I have the same problem.

From what I can see, iTMSTransporter is failing, but the output (iTunes Transporter output above ^) is limited to 15 lines, so we can't see that went wrong. The same happens invoking fastlane with --verbose. I suggest the iTMSTransporter output should not be limited in verbose mode.

[frankfuu]

For anyone experiencing this issue on Azure DevOps, I solved this by changing the Release Pipeline agent specification from macOS-latest, which currently is still an alias for macOS-11, to macOS-12.

The macOS-12 spec uses Xcode 14 instead of Xcode 13. In turn, fastlane uses altool (instead of iTMSTransporter) by default for Xcode 14.

altool did upload successfully.

Thanks for sharing. Changing to macOS-12 worked for me.

[nuldato]

It seems like Apple servers were down ?

Today, after a simple retry the upload succeeds for me.

[jbatra-umeey]

@nuldato did you face the same error earlier which I have posted ?

[jbatra-umeey]

@nuldato I think you are right. There must have been some server outrage. I just deployed it again and its working fine

[richardkshergold]

I'm getting this error today (trying to upload a build from Ionic AppFlow)

[Ruchi-VDBApp]

I'm also facing same issue currently,

[MoemenMostafa]

We are facing the same issue still since 2 days

[TulasiPerigisetti7]

We also have the same issue since 2 days. Can someone please help to resolve the issue.

[richardkshergold]

For anyone using AppFlow (like us) the latest build stack does not use iTMSTransporter so if you use that you do not get the issue

[TulasiPerigisetti7]

We are not using AppFlow :(

[Cayke]

I was having the same issue. Fixed after updating my macOS

[TulasiPerigisetti7]

Can you please let me know to which version is macOS updated ?

[Cayke]

Can you please let me know to which version is macOS updated ?

I updated to the latest macOS version and after that updated XCode to the latest available on app store.
I dont know why but after that my upload scripts are working again.

[hongdangodori]

I have the same issue. Does it really work well if I just update the Mac?

[rasentry]

I have the same issue. Fastlane version 2.211.0

[DmitriyDark]

Same issue. Fastlane 2.211.0
Xcode 13
MacOS 12.6.1

[janduldhardt]

Same issue happens since mid November. Usually restarting the pipeline helps but takes sometimes a couple of tries.

[TulasiPerigisetti7]

providing both team_id and itc_provider resolved the issue for me.

team_id: you can grab here if you're logged into your dev account (under data.associatedAccounts[n].contentProvider.contentProviderId)

itc_provider: your team ID for your apple account, you can find in developer.apple.com portal

(Xcode 13.3)

Can you please let me know where I must provide these values

[rwangau]

I have the same problem and highly suspect it's an Apple issue.
And did notice that as soon as you manually upload a build with the same version, the fastlane will work fine again.

[shaileshpendams]

We are not using AppFlow :(

TulasiPerigisetti7 any luck..!

[TulasiPerigisetti7]

We are not using AppFlow :(

TulasiPerigisetti7 any luck..!

Setting the env variable ITMSTRANSPORTER_FORCE_ITMS_PACKAGE_UPLOAD=true worked for me

[charmipatalia]

I am also having same issue. Can anyone have proper solution?
MacOS : 12.5.1
xCode : 14.0.1
fastlane version : 2.211.0

[DmitriyDark]

Addition env ITMSTRANSPORTER_FORCE_ITMS_PACKAGE_UPLOAD=true dont work for me.
But in my case use another Xcode version work fine.
App was builded and signed with Xcode 13, but before upload i switch Xcode to 14.1 and then ipa uploading run without issues.
Used fastlane 2.211.0

[AnuragTiwari1]

I am also seeing this, strangely one build succeeded but after sometime started facing this. I checked Apple Developer system status it is green. any solution for this

[rwangau]

Upgraded the macOS to Ventura and XCode 14.1, then the upload works fine without issues.

[Lisba]

@Marygimm did you find a solution to your specific error message?

[Marygimm]

No, it actually worked in the day before...

[ooikengsiang]

For anyone experiencing this issue on Azure DevOps, I solved this by changing the Release Pipeline agent specification from macOS-latest, which currently is still an alias for macOS-11, to macOS-12.

The macOS-12 spec uses Xcode 14 instead of Xcode 13. In turn, fastlane uses altool (instead of iTMSTransporter) by default for Xcode 14.

altool did upload successfully.

Azure Pipeline with macOS-latest doesn't work as well, need to specify set to macOS-12

[tastydev]

I had the same Issue today and it was gone after uploading a build manually with XCode. After the manual xcode upload the fastlane iTunes Transporter upload worked again.

[niallwatchorn]

This was happening to me too, I updated to the latest version and it was fixed.

[lahirupintospt]

Got the same issue this week on [macos-12 & Xcode_13.3.1.app]
Fixed it by updating the xcode to Xcode_14.1.app

[asalvo]

Started seeing this last week and we build every night. Eventually we got an upload to succeed after multiple reties last week. Then faced the same problem this week again. We have 8 build agents running on VMs and the problem affects them all, which is not too surprising as they are all configured the same. We also have a couple of different apps/bundles we upload and this has affected 3 of 3 so far.

OSX: 12.0.1
XCode: 13.1
Fastlane: 2.211.0

[mdgeist]

Started seeing this last week and we build every night. Eventually we got an upload to succeed after multiple reties last week. Then faced the same problem this week again. We have 8 build agents running on VMs and the problem affects them all, which is not too surprising as they are all configured the same. We also have a couple of different apps/bundles we upload and this has affected 3 of 3 so far.

OSX: 12.0.1 XCode: 13.1 Fastlane: 2.211.0

In older versions of Xcode the upload mechanism was done through iTMSTransporter, a tool that lives inside of your Xcode install. I'm wondering if that is being removed/deprecated in favor of the new transfer tool called altool has caused issues. Xcode 14.1+ uses altool to upload to App Store Connect.