fastlane: iTMSTransporter Authorization Required error

New Issue Checklist

Issue Description

When using pilot or deliver I get Authorization Required errors. This seems to be an issue for some accounts/apps only (not all I use) even though I was able to successfully execute lanes for these accounts/apps before with the same parameters.

I have noticed that once I got this error for a particular account/app then each time I try to execute pilot/deliver/the same lanes for this account/app it will end with this error on upload. Not sure how long this will last - I will try to check this later on.

This error is strange because if I use the same ipa file and upload it via Application Loader it works with no issue…

Pilot Output
[11:18:18]: -------------------
[11:18:18]: --- Step: pilot ---
[11:18:18]: -------------------
[11:18:18]: Login to App Store Connect (##Redacted##)
[11:18:21]: Login successful
[11:18:21]: Ready to upload new build to TestFlight (App: ##Redacted##)...
[11:18:22]: Going to upload updated app to App Store Connect
[11:18:22]: This might take a few minutes. Please don't interrupt the script.
[11:19:21]: [Transporter Error Output]: An error occurred while processing the http request for the webDAV upload.
[11:19:21]: [Transporter Error Output]: An exception has occurred: Authorization Required
[11:19:24]: Transporter transfer failed.
[11:19:24]:
[11:19:24]: An error occurred while processing the http request for the webDAV upload.
An exception has occurred: Authorization Required
[11:19:24]: [iTMSTransporter] [2018-11-19 11:19:24 CEST] <main> DBG-X: Apple's web service operation return value:

11:19:24: [iTMSTransporter] [2018-11-19 11:19:24 CEST] <main> DBG-X: parameter EnableJWTForAllCalls = false

11:19:24: [iTMSTransporter] [2018-11-19 11:19:24 CEST] <main> DBG-X: parameter SessionExpiration = 2018-11-22T09:19:21.681Z

11:19:24: [iTMSTransporter] [2018-11-19 11:19:24 CEST] <main> DBG-X: parameter Success = true

11:19:24: [iTMSTransporter] [2018-11-19 11:19:24 CEST] <main> DBG-X: parameter StreamingSettings = {LogStreamingEnabled=true, MultipartUploadsEnabled=true, AssetDescriptionStreamingEnabled=false}

11:19:24: [iTMSTransporter] Package Summary:

11:19:24: [iTMSTransporter] 1 package(s) were not uploaded because they had problems:

11:19:24: [iTMSTransporter] /var/folders/q3/pv4n6xx50y189qbvp34h__vc0000gn/T/d20181119-16194-qvgie9/{redacted_ap_id}.itmsp - Error Messages:

11:19:24: [iTMSTransporter] An error occurred while processing the http request for the webDAV upload.

11:19:24: [iTMSTransporter] An exception has occurred: Authorization Required

11:19:24: [iTMSTransporter] [2018-11-19 11:19:24 CEST] <main> DBG-X: Returning 1

11:19:24: iTunes Transporter output above ^ 11:19:24: An error occurred while processing the http request for the webDAV upload. An exception has occurred: Authorization Required Return status of iTunes Transporter was 1: An error occurred while processing th\nAn exception has occurred: Authorization Required The call to the iTMSTransporter completed with a non-zero exit status: 1. This indicates a failure. 11:19:24: Error uploading ipa file, for more information see above

Deliver Output
[✔] Uploading metadata to App Store Connect
[11:39:34]: Successfully uploaded set of metadata to App Store Connect
[11:39:36]: Starting with the upload of screenshots...
[11:39:36]: Successfully uploaded screenshots to App Store Connect
[11:39:38]: Price Tier unchanged (tier 0)
[11:39:39]: Uploading app icon...
[11:40:04]: Uploading binary to App Store Connect
[11:40:06]: Going to upload updated app to App Store Connect
[11:40:06]: This might take a few minutes. Please don't interrupt the script.
[11:41:49]: [Transporter Error Output]: An error occurred while processing the http request for the webDAV upload.
[11:41:49]: [Transporter Error Output]: An exception has occurred: Authorization Required
[11:41:51]: Transporter transfer failed.
[11:41:51]:
[11:41:51]: An error occurred while processing the http request for the webDAV upload.
An exception has occurred: Authorization Required
[11:41:52]: [iTMSTransporter] [2018-11-19 11:41:51 CET] <main> DBG-X: Apple's web service operation return value:

11:41:52: [iTMSTransporter] [2018-11-19 11:41:51 CET] <main> DBG-X: parameter EnableJWTForAllCalls = false

11:41:52: [iTMSTransporter] [2018-11-19 11:41:51 CET] <main> DBG-X: parameter SessionExpiration = 2018-11-23T10:41:49.257Z

11:41:52: [iTMSTransporter] [2018-11-19 11:41:51 CET] <main> DBG-X: parameter Success = true

11:41:52: [iTMSTransporter] [2018-11-19 11:41:51 CET] <main> DBG-X: parameter StreamingSettings = {LogStreamingEnabled=true, MultipartUploadsEnabled=true, AssetDescriptionStreamingEnabled=false}

11:41:52: [iTMSTransporter] Package Summary:

11:41:52: [iTMSTransporter] 1 package(s) were not uploaded because they had problems:

11:41:52: [iTMSTransporter] /tmp/{redacted_app_id}.itmsp - Error Messages:

11:41:52: [iTMSTransporter] An error occurred while processing the http request for the webDAV upload.

11:41:52: [iTMSTransporter] An exception has occurred: Authorization Required

11:41:52: [iTMSTransporter] [2018-11-19 11:41:51 CET] <main> DBG-X: Returning 1

11:41:52: iTunes Transporter output above ^ 11:41:52: An error occurred while processing the http request for the webDAV upload. An exception has occurred: Authorization Required Return status of iTunes Transporter was 1: An error occurred while processing th\nAn exception has occurred: Authorization Required The call to the iTMSTransporter completed with a non-zero exit status: 1. This indicates a failure.

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Reactions: 8
  • Comments: 23 (14 by maintainers)

Most upvoted comments

I ran into the same issue since a day or 2 ago. I was on 2.116.0. Later, updated to 2.116.1. In both case, the upload step results in same error message:

[11:48:32]: [iTMSTransporter] 		An exception has occurred: Authorization Required

Base on @androidseb suggestion, I added to my fast file before calling upload_to_testflight

ENV["DELIVER_ITMSTRANSPORTER_ADDITIONAL_UPLOAD_PARAMETERS"] = " "

This stops the iTMSTransporter error

So, while keeping FL version 2.115, I was able to fix the problem by editing the fastlane/.env.default file.

DELIVER_ITMSTRANSPORTER_ADDITIONAL_UPLOAD_PARAMETERS=" "

^ Once doing this, the webdav upload error stopped happening. This basically reverts the upload command behavior to what was happening before this MR was merged in version 2.106, breaking the upload for us: https://github.com/fastlane/fastlane/pull/13404

This is good enough for us since it’s just one entry in a config file and it avoids having to modify FL executable files.

I hope this helps other people 😃

Still having this issue, I tried troubleshooting version by version to see where the problem is. I tried performing the upload updating my Gemfile every time: 2.108 -> problem happens 2.107 -> problem happens 2.106 -> problem happens 2.105 -> error installing gem, so didn’t check 2.104 -> problem GONE!

I looked at the release changelog for version 2.106 here: https://github.com/fastlane/fastlane/releases/tag/2.106.0

I noticed one of the changes is:

[pilot] fixes issue with -t DAV upload parameter not being set in Pilot upload commands (#13404) via Robert MacEachern

This is the change in question: https://github.com/fastlane/fastlane/pull/13404

Next time I encounter this upload problem, I will try reverting the changes of that pull request and see if it solves my problem… In the meantime, maybe this will help troubleshoot…

We have the same issue (including the same output of Application Loader) after upgrading from 2.102 to 2.109. Reverted fastlane back to 2.102 and we’re able to submit apps again.

I have the same issue. I was using 2.108. Seeing mjovkovic’s message, I tried to upgrade to 2.110 with no luck. I reverted back to 2.102 and it worked for me as well! The weird thing is that we have several branded apps (identical binaries except icon, name and signature) and for the same version of the binary, some apps of the App Store are not affected by this issue and were successfully uploaded. For those having this issue, over 10 attempts systematically failed, but as soon as I switched to 2.102 it worked. I hope this helps investigate the issue further…