Post

Replies

Boosts

Views

Activity

iTMSTransporter errors with "Bad Status received from server: 400"
I could use an extra set of eyes on this - I'm totally stuck. Any ideas or thoughts on things to check would be much appreciated. This problem started on 2025-02-06. It's a Unity project under active development, but I don't see where that can create a problem when using Transporter. We have been uploading fine for months. Now we are seeing errors like this: <RLT-005> INFO: Upload Failed: (id: 650d9057-eb69-4d32-a765-e53894c332e3 file: myapp.ipa part: 24) ([1/3] will retry): org.apache.http.NoHttpResponseException: The target server failed to respond <RLT-005> INFO: Starting upload for reservation: (650d9057-eb69-4d32-a765-e53894c332e3) file: (myapp.ipa/24) attempt: 2 size: 5242880 <main> ERROR: myapp.ipa (8) - Bad Status received from server: 400 <main> ERROR: Could not upload 1 file(s): <main> ERROR: Could not upload file: myapp.ipa 28 parts failed: [10, 24, 5, 14, 7, 2, 16, 19, 25, 1, 21, 9, 3, 6, 8, 15, 12, 27, 18, 26, 11, 20, 17, 4, 23, 28, 13, 22] <main> ERROR: Please retry your upload later. That "400" server error has me thinking it could be something on Apple's side. But I've also seen this error: INFO: Verifying checksums against the previous upload attempt. <main> ERROR: A file(s) has been modified between the initial upload and restart of the upload. Please retry your upload. So I don't know what to make of it. Nothing had changed in how we use Transporter. Things I've tried: I have tried the Transporter command using all three "-t" options: Aspera, Signiant, HTTP. Same errors. I have tried using a new app password. I have tried upgrading the OS version to Sequoia 15.3. Xcode 16.0 with iOS 18 stuff I have tried upgrading Transporter to 3.4.1. I am running a Mac mini - M1, 2020. I am working on trying with a different host on a different internet connection. Maybe some network security device is interfering somehow. I am able to manually use Xcode to archive the project and upload it to TestFlight, so the problem appears to be isolated to Transporter or the servers it talks to. The only unexpected warning I see when manually archiving and uploading is something about a HelpShiftX.framework dSYM not being included. Could that be a cause of the Transporter issue?
1
0
173
1w