New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Transporter Error Output]: An exception has occurred: Broken pipe (Write failed) #16749
Comments
It seems like you have not included the output of |
Yes sorry fastlane-bot see #16748 😬 |
Same issue here - I upgraded to 2.150.1 after I'd been running with one of the 2.150.0 rc builds and now I'm consistently getting a transporter broken pipe when uploading the IPA since I updated yesterday. I had initially thought it might just be an intermittent issue on apple's end per #16462 but that doesn't seem to be the case this time. |
I'm seeing the same issue, but was seeing it first on 2.149.1 so I updated to 2.150.1 to see if that would help, but it didn't. I believe this is more like an iTunes server issue but will try to push a TestFlight build from Xcode just to be sure. Will post back findings. |
I got the same error with fastlane version 2.150.0...help... ================================== fastlane env =============================== Stack
System Locale
==================================== error log ========================================= [09:30:09]: Loading './fastlane/metadata/review_information/email_address.txt'... |
Was able to upload via Xcode without issue. |
Finally,I upload successfully via 'Transporter App' |
Same issue here with Fastlane version 2.148.1, I've been seeing this kind of issue since Fasltane's version 2.149.0, then I did a downgrade to v 2.148.1 but is still happening. I don't know if this is an Apple's API server error but it's weird because using Xcode there is no problem. I'd be grateful if someone can help. |
Same issue, I tried with fastlane 2.150.1 and 2.149.1. |
I used the Signiant delivery protocol mentioned here on a similar issue: #13572 (comment) and I managed to get a build uploaded using 2.145.0 |
Same issue here with 2.150.2, it has worked perfectly up to July 2nd but now it just fails. [12:46:00]: Making sure the latest version on App Store Connect matches '10.1.94'... [12:52:37]: [iTMSTransporter] [2020-07-04 12:52:36 UTC] DBG-X: parameter Success = true [12:52:37]: [iTMSTransporter] [2020-07-04 12:52:36 UTC] DBG-X: parameter StreamingSettings = {LogStreamingEnabled=true, MultipartUploadsEnabled=true, AssetDescriptionStreamingEnabled=false} [12:52:37]: [iTMSTransporter] [2020-07-04 12:52:36 UTC] INFO: Transporter's command line arguments are: -m upload -u hidden value -p hidden value -f /tmp/1467362535.itmsp -t DAV -k 100000 -itc_provider L82P3RMM4V [12:52:37]: [iTMSTransporter] [12:52:37]: [iTMSTransporter] [12:52:37]: [iTMSTransporter] [12:52:37]: [iTMSTransporter] Package Summary: [12:52:37]: [iTMSTransporter] [12:52:37]: [iTMSTransporter] 1 package(s) were not uploaded because they had problems: [12:52:37]: [iTMSTransporter] /tmp/1467362535.itmsp - Error Messages: [12:52:37]: [iTMSTransporter] An error occurred while uploading the package: 1467362535.itmsp. [12:52:37]: [iTMSTransporter] An exception has occurred: Connection reset [12:52:37]: [iTMSTransporter] An error occurred while uploading the package: 1467362535.itmsp [12:52:37]: [iTMSTransporter] [2020-07-04 12:52:36 UTC] DBG-X: Returning 1 [12:52:37]: iTunes Transporter output above ^ [12:52:37]: An error occurred while uploading the package: 1467362535.itmsp. An exception has occurred: Connection reset An error occurred while uploading the package: 1467362535.itmsp. An exception has occurred: Connection reset An error occurred while uploading the package: 1467362535.itmsp Return status of iTunes Transporter was 1: An error occurred while uploading the package: 1467362535.itmsp. \nAn exception has occurred: Connection reset \nAn error occurred while uploading the package: 1467362535.itmsp. \nAn exception has occurred: Connection reset \nAn error occurred while uploading the package: 1467362535.itmsp The call to the iTMSTransporter completed with a non-zero exit status: 1. This indicates a failure. |
Same issue for us, previous fastlane versions dont work as well. |
Signiant delivery protocol worked for us! (edit)
|
Maybe it's the DAV delivery protocol settings that cause it to fail.
Apple seems to recommend not setting a delivery protocol. |
Thank you for this! We're able to use this as a workaround for now since this has been holding up our release pipeline for a couple days. |
The Signiant protocol is blocked by a lot of corporate firewalls, so this workaround won't be an option for some people. Hopefully there will be a fix for this soon. |
Agree. We're using Bitrise, and it worked out OK. Hopefully an official fix is in the works. |
@scottlemke how did you use Signiant protocol in Bitrise? |
Create an environment variable called |
Signiant didn't work for us either
|
Same with |
@janpio For me this issue occurs for |
Set that variable to one white space, it works well in our environment.
|
Thank you @taisukeh, it works! |
I can confirm that -t Signiant in Bitrise is solving my problem as well |
This worked for us perfectly, after multiple unsuccessful tries to deploy. Signiant doesn't work for is, it can't establish a connection. I guess it is blocked in our firewall as @JimHowell20 has already pointed out. |
👋 The fix for this will be released in |
✅ fastlane environment ✅Stack
System Locale
fastlane files:`./fastlane/Fastfile`# This file contains the fastlane.tools configuration
# You can find the documentation at https://docs.fastlane.tools
#
# For a list of all available actions, check out
#
# https://docs.fastlane.tools/actions
#
# For a list of all available plugins, check out
#
# https://docs.fastlane.tools/plugins/available-plugins
#
# Uncomment the line if you want fastlane to automatically update itself
before_all do
update_fastlane
end
default_platform(:ios)
platform :ios do
desc "Push a new beta build to TestFlight"
lane :beta do
match(type: "appstore")
# increment_version_number(bump_type: "minor")
increment_build_number(xcodeproj: "tkt_react.xcodeproj")
build_app(workspace: "tkt_react.xcworkspace", scheme: "tkt_react")
upload_to_testflight(
groups: ['Team']
)
end
end `./fastlane/Appfile`app_identifier("com.tikkit.tkt-react") # The bundle identifier of your app
apple_id("atlas@tikkit.io") # Your Apple email address
itc_team_id("117926984") # App Store Connect Team ID
team_id("ZP8G2NEB87") # Developer Portal Team ID
# For more information about the Appfile, see:
# https://docs.fastlane.tools/advanced/#appfile fastlane gems
Loaded fastlane plugins:No plugins Loaded Loaded gems
generated on: 2020-07-14 Hello! Sadly reporting broken pipe / write failed today on Fastlane With no environment variable set With With Any thoughts greatly appreciated! |
@iiAtlas Hey! Can you try not setting anything? It should be smart enough to pick its own now |
Hey @joshdholtz thanks for the speedy reply. Sorry about that, the first output above (broken pipe) resulted with no environment variable set. I've edited the above to make that more clear! |
@iiAtlas Thanks for clarifying! Can you also try ENV["DELIVER_ITMSTRANSPORTER_ADDITIONAL_UPLOAD_PARAMETERS"] = "-t Aspera"? I don't know if that will help at all but this is a bit confusing 🤷♂️ |
Sorry for the delay @joshdholtz -- that one is a no go!! I'm also not pulling up any system issues when visiting https://www.apple.com/support/systemstatus/ or https://developer.apple.com/system-status/. Not sure if that is a clue or just further confusion... And to be clear, this is a working Fastlane environment for the past 8 months or so! Thanks for the help. |
@iiAtlas Hmmmm 🤔 I've tried all of the different options on my end and things seem to be working fine for me 😔 Are you on a different network or a behind a firewall of some sort today? |
@joshdholtz I am on a different network than my usual but nothing that would have immediately caused concern! I'll head to another spot and see if I have better results... If it does prove to be network related then I am sorry for wasting your time!!! |
@iiAtlas Don't worry about my time 😇 This is what I'm here for! |
Total success! 🤦 Now to dig in to whats stopping this from working at my home base.... thanks @joshdholtz and sorry for dragging up the thread! The mirrored error message mislead me.... |
…e#16749 (fastlane#16774) * Set default ITMSTransporter transport flag to blank fastlane#16749 * Check upload options ENV if nil or empty Co-authored-by: Josh Holtz <josh@rokkincat.com>
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with |
This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem 👍 |
🔑
New Issue Checklist
Issue Description
Hi there! We've been following along with all of the recent updates, and everything was up and running great with 2.150.0 and 2.150.1. Then sometime on Friday, we started seeing these connection reset / broken pipe issues, which are still ongoing. It's unclear to me if it's an App Store issue, a fastlane issue, or maybe a unique combination :).
Any advice is appreciated — thanks in advance!
Command executed
upload_to_app_store(
ipa: './PlanGrid.ipa',
force: true,
skip_screenshots: true,
skip_app_version_update: false,
run_precheck_before_submit: false
)
Complete output when running fastlane, including the stack trace and command used
Environment
I filed #16748 becuase our env command is failing. I've included a bunch of info below. Please let me know if you need more!
Gemfile.lock
The text was updated successfully, but these errors were encountered: