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
regression - fastlane deliver error #11958
Comments
Same here. |
Same issue for us |
Same here |
Same here |
1 similar comment
Same here |
Adding my two cents. Using jenkins with groovy, adding this solves the issue:
Interestingly enough, application loader app failed as well (same ipa) but then retried by itself and worked. |
It might be related to passwords (not my tweet) https://twitter.com/depoisfalamos/status/969240512665411584 |
Adding the environment variable worked for me as well. the issue only started occurring a couple hours ago. Not to be confused with last week's iTC failures suggesting my binaries included the wrong arm slice, but without changing anything uploads started working again. Unbelievable that Apple can make so many backend changes without testing how it will affect the people who's livelihoods rely on their services working as they say it will. |
The suggested solution worked once for us, but subsequent builds failed to upload with this error:
|
Same here! |
Bump. |
@Ruenzuo I got the same error while uploading my build through Xcode earlier today. This seems to be an error from Apple side. |
The env variable helps. for me it works 50% upload attempts. |
I had this fail about 3 times and it just succeeded on my latest attempt. Whether this means Apple has fixed the issue or not I'm not sure but it may mean that the env var suggestion isn't necessary (I didn't add it but I just got lucky and got a build through.) |
Still not working |
Bump. I was able to get a build through after adding the environment variable to my build environment (CircleCI):
As @szweier mentioned above, I cannot definitively say that the environment variable is what fixed the problem, but for now, it is working for me 👍 |
Thanks everyone, for next time, please include the word I'm investigating if there is something we should change with fastlane, or if this is just a temporary Apple server error. Thanks everyone for letting us know |
Just an update. |
I was just able to submit another app without the environment variable with no issues. And by using a different lane for the app I originally had a problem with this morning that also didn't have the environment variable, upload just succeeded as well. Who know's if this is a server side issue or not at this point. |
Alright, just prepared #11965, and will push a release ASAP, it will probably take about 20 minutes. Thanks everyone, for the time being, you can use the workaround using the environment variable export DELIVER_ITMSTRANSPORTER_ADDITIONAL_UPLOAD_PARAMETERS="-t DAV" |
I was able to submit 1 of 4 apps with the environment variable. Will keep trying... |
* Add workaround for iTC transporter outage Fixes #11958 * Add space
New release is live, please update and let us know if the issue is resolved for you 🚀 |
Thank you everyone! |
@KrauseFx updating resolved the issue for me 🙂 thanks! |
@KrauseFx i can also confirm. the new release is working and you don't need the environment variable |
Glad to hear, thanks everyone 🚀 Let's go back to shipping cool stuff |
I've still the same problem. But if I add the environment variable:
it works I'm using fastlane 2.85.0 |
* Add workaround for iTC transporter outage Fixes fastlane#11958 * Add space
Hi,
I am facing fastlane deliver error since this afternoon. Just 4 hours back when I submitted the app it worked all fine. But now its failing. I updated fastlane to the latest version (2.83.0) but the error persists.
[13:33:22]: Going to upload updated app to iTunes Connect
ERROR: Could not start delivery: all transports failed diagnostics[13:33:22]: �[32mThis might take a few minutes. Please don't interrupt the script.�[0m
[13:35:46]: �[31m[Transporter Error Output]: Could not start delivery: all transports failed diagnostics
�[0m
[13:35:46]: �[31mTransporter transfer failed.�[0m
[13:35:46]:
[13:35:46]: �[31mCould not start delivery: all transports failed diagnostics
�[0m
[13:35:46]: �[33m[iTMSTransporter] [2018-03-01 13:35:46 CET] DEBUG: Transfer warning: Scheduling automatic restart in 1 minute
�[0m
[13:35:46]: �[33m[iTMSTransporter] at com.signiant.interactivetransfer.engine.TransferEngine$2.run(TransferEngine.java:593)
�[0m
[13:35:46]: �[33m[iTMSTransporter]
�[0m
[13:35:46]: �[33m[iTMSTransporter] [2018-03-01 13:35:46 CET] DEBUG: Received failed transfer notification; aborting
�[0m
[13:35:46]: �[33m[iTMSTransporter] [2018-03-01 13:35:46 CET] INFO: Scheduling automatic restart in 1 minute
�[0m
[13:35:46]: �[33m[iTMSTransporter] [2018-03-01 13:35:46 CET]
�[0m
[13:35:46]: �[33m[iTMSTransporter]
�[0m
[13:35:46]: �[33m[iTMSTransporter]
�[0m
[13:35:46]: �[33m[iTMSTransporter]
�[0m
[13:35:46]: �[33m[iTMSTransporter] Package Summary:
�[0m
[13:35:46]: �[33m[iTMSTransporter]
�[0m
[13:35:46]: �[33m[iTMSTransporter] 1 package(s) were not uploaded because they had problems:
�[0m
[13:35:46]: �[33m[iTMSTransporter] /tmp/1013791145.itmsp - Error Messages:
�[0m
[13:35:46]: �[33m[iTMSTransporter] Could not start delivery: all transports failed diagnostics
�[0m
[13:35:46]: �[33m[iTMSTransporter] [2018-03-01 13:35:46 CET] DBG-X: Returning 1
�[0m
[13:35:46]: iTunes Transporter output above ^
[13:35:46]: �[31mCould not start delivery: all transports failed diagnostics
Return status of iTunes Transporter was 1: Could not start delivery: all transports failed diagnostics
The call to the iTMSTransporter completed with a non-zero exit status: 1. This indicates a failure.�[0m
The text was updated successfully, but these errors were encountered: