Darwin Build Environment Help Center

Upload failure due to deprecated Transporter usage

append delete hicham

Windows version:
Windows 11

Builder version:
3.83.1

SDK version:
3.83.1

Context:
I am trying to upload a valid signed IPA to App Store Connect. The IPA was generated successfully from Unity/Xcode and can be exported correctly. The app uses CocoaPods and Firebase SDKs (Crashlytics, Analytics, etc.).

The upload itself fails before transfer starts with the following Apple error:

Deprecated Transporter usage. You are required to use the -assetFile command instead of the -f command with your .ipa or .pkg files. Additionally, to continue uploading apps using the Aspera and Signiant delivery methods, you are required to use Transporter 4.2 or later. (1046)

It seems the tool still uses the old deprecated `-f` Transporter argument internally.

I tested:

* Darwin Build Environment
* Fastlane
* other Windows App Store Connect upload tools

The IPA itself appears valid and signed correctly, but all uploaders relying on the old Transporter backend now fail with the same Apple message.

I also verified that removing re-signing does not change the issue.

Reply RSS

Replies

append delete #1. Pierre-Marie Baty

Hello

The tool does not use Apple's iTMSTransporter. Instead it reimplements Apple's iTMSTransporter WebDAV protocol in C using LibreSSL. It was done a few years ago, but Apple introduced changes in the protocol since then and deprecated the use case which was reverse engineered to build this implementation.

The upload tool needs an update. You can consider the upload feature of this toolchain broken until the next upgrade.

:: @Pierre-Marie Baty added on 08 May ’26 · 10:44

*edit* FWIW :

https://help.apple.com/itc/transporteruserguide/

Since you use Windows 11, if you're knowledgeable and comfortable enough with command line tools, you can use Apple's own iTMSTransporter to upload your app. I read they provide their own Java execution environment on Windows now.

If you do, I'll be interested in your feedback, to know if it's become a worthy alternative to my upload tool.

append delete #2. Pierre-Marie Baty

I made further research on this, and the news are bad.

*Apple has tightened the screws and seem to no longer want to allow the possibility of uploads to the App Store of apps that have not been built with Xcode.*

To enforce this, they now force all uploads made through their submission APIs (WebDAV, Signiant, Aspera, either with iTMSTransporter or whatever reimplementation such as this toolchain's transporter.exe), to include a specific binary AppStoreInfo.plist file that only Xcode generates.

The format of this file is, of course, documented nowhere.

In other words, even with Apple's iTMSTransporter command-line tool that *supposedly* enables you to upload .ipa files from Windows, you won't go far because to do so you'll need a companion .plist file that you can only obtain from Xcode. Clapping hands in irony here.

At this point, and considering the slowly decaying popularity of this toolchain, I honestly do not know if I will invest more time and effort in this uphill battle. I've done my best for 15 years to give people the possibility to build and upload their Apple apps on the ecosystem they want, the challenge has been tough and kept getting tougher every few years, and I don't know if it's still worth it considering less and less people use it and more and more people prefer privacy-questionable "cloud build" alternatives.

I'll take the night to ponder.

Sorry all. Really.

:: @Pierre-Marie Baty added on 08 May ’26 · 16:15

*edit* it won't wait til tomorrow in fact. I realize that with my new dayjob that I took in february I no longer have the material time to continue the race.

I call it quits. I'll make an announcement.

append delete #3. Pierre-Marie Baty

Reply

(Leave this as-is, it’s a trap!)

There is no need to “register”, just enter the same name + password of your choice every time.

Pro tip: Use markup to add links, quotes and more.

Moderators: Pierre-Marie Baty