fastlane: [pilot] "Error receiving the newly uploaded binary" on the very first upload

New Issue Checklist

Updated fastlane to the latest version
I have read the Contribution Guidelines

Issue Description

Having a new app, created in iTunes Connect web interface. When I run the fastlane script on a deploy lane for the first time - it fails. Meanwhile, the binary uploaded fine. The very same script with no changes but app version being incremented succeeded, when run at second time.

I guess the problem line is

break if builds.count == 0

Maybe there must be some extra checks for that case.

Complete output when running fastlane, including the stack trace and command used

[15:30:19]: -------------------
[15:30:19]: --- Step: pilot ---
[15:30:19]: -------------------
[15:30:19]: Login to iTunes Connect (user@mail.com)
[15:30:23]: Login successful
[15:30:23]: Ready to upload new build to TestFlight (App: 123456789)...
[15:30:24]: Going to upload updated app to iTunes Connect
[15:30:24]: This might take a few minutes, please don't interrupt the script
[15:31:55]: iTunes Transporter successfully finished its job
[15:31:55]: ------------------------------------------------------------------------------------------------------
[15:31:55]: Successfully uploaded package to iTunes Connect. It might take a few minutes until it's visible online.
[15:31:55]: ------------------------------------------------------------------------------------------------------
[15:31:56]: Successfully uploaded the new binary to iTunes Connect
[15:31:56]: If you want to skip waiting for the processing to be finished, use the `skip_waiting_for_build_processing` option
[15:31:56]: Waiting for iTunes Connect to process the new build
[15:32:27]: Variable Dump:
[15:32:27]: {:DEFAULT_PLATFORM=>:ios, :PLATFORM_NAME=>:ios, :LANE_NAME=>"ios auto", :SIGH_PROFILE_TYPE=>"app-store", :VERSION_NUMBER=>"1.0.117", :BUILD_NUMBER=>"1.0.117", :PRODUCE_APPLE_ID=>"", :IPA_OUTPUT_PATH=>"/Users/travis/build/Company/Repo/Project/Project", :DSYM_OUTPUT_PATH=>"/Users/travis/build/Company/Repo/Project/Project.app.dSYM.zip", :XCODEBUILD_ARCHIVE=>"/Users/travis/Library/Developer/Xcode/Archives/2016-06-13/Project 2016-06-13 15.22.47.xcarchive", :HOCKEY_DOWNLOAD_LINK=>"https://upload.hockeyapp.net/apps/123456789", :HOCKEY_BUILD_INFORMATION=>{"title"=>"Project", "bundle_identifier"=>"com.app.project", "public_identifier"=>"xxxxx", "platform"=>"iOS", "release_type"=>0, "custom_release_type"=>nil, "created_at"=>"2016-05-11T22:12:24Z", "updated_at"=>"2016-06-13T15:30:18Z", "featured"=>false, "id"=>xxxxxx, "config_url"=>"https://upload.hockeyapp.net/manage/apps/xxxx/app_versions/58", "public_url"=>"https://upload.hockeyapp.net/apps/xxxxxxxx", "minimum_os_version"=>"9.0", "device_family"=>"iPhone/iPod/iPad", "status"=>2, "visibility"=>"private", "integrated_at"=>"2016-05-11T22:28:50Z", "owner"=>"Owner", "owner_token"=>"token", "company"=>"Company"}}
[15:32:27]: Error receiving the newly uploaded binary, please check iTunes Connect

Configuration Files

Please copy the complete content of your Fastfile and any other configuration files you use below:

Fastfile:

...

lane :deploy do
    match(type: "development", force_for_new_devices: true)
    build(beta:false)
    pilot(skip_submission:true, app_identifier: proj_id, verbose: true)
    download_dsyms                  
    upload_symbols_to_crashlytics
  end

Environment

fastlane version (run fastlane -v): 1.95.0 Do you use bundler to execute fastlane (i.e. bundle exec fastlane)? bundle Do you use a Ruby environment manager (e.g. chruby, rbenv, rvm)? rvm

About this issue

Original URL
State: closed
Created 8 years ago
Reactions: 23
Comments: 79 (26 by maintainers)

Most upvoted comments

I experienced this too, but it was when I uploaded a new version of an existing app for the first time.

ashfurrow on Jun 17, 2016

Okay, we’re reproducing the issue on our end, will look into possible solutions and will report back shortly! Thanks for your patience, all!

mpirri on Jun 30, 2016

Thanks for the fix! Next time we push to iTunesConnect / Testflight, I will let you know how it goes.

Edit: Fixed confirmed, successful upload to iTunesConnect!

We see a lot of new, repeated output lines, but I think that’s to be expected:

[Step 1/5] [12:11:25]: New application; waiting for build train to appear on iTunes Connect

And

[Step 1/5] [12:11:59]: Waiting for iTunes Connect to finish processing the new build (ver)

Thanks again!

Kendaren on Nov 3, 2016

@MaximusMcCann Good feedback - we think of PILOT_WAIT_FOR_NEW_BUILD_TRAINS_ON_ITUNES_CONNECT as a “hidden” feature flag that we are using to validate a new behavior before making it the default (and only) option. We will probably release a new version of pilot shortly that sets this behavior by default at which point this environment variable will go away.

mpirri on Oct 28, 2016

@jlubeck Okay, let me look into that one a bit further. I still suspect that the line ERROR [2016-10-28 13:27:40.06]: The file, c65c990af6831864010a0b1b8f09739c.ipa, did not complete its upload. implies a different error, but I’ll see what I can learn.

mpirri on Nov 1, 2016

mpirri’s PR: “If anyone wants to try out this PR, you just need to set the environment variable PILOT_WAIT_FOR_NEW_BUILD_TRAINS_ON_ITUNESCONNECT=1 before executing fastlane/pilot”

tomachi on Aug 28, 2016

Also, I’ve got following email from iTC team:

<...>
Invalid Swift Support - The SwiftSupport folder is missing. Rebuild your app using the current public (GM) version of Xcode and resubmit it.

Once these issues have been corrected, you can then redeliver the corrected binary.

Regards,

The App Store team

nesterenkodm on Jul 20, 2016

Happened to me as well. Same scenario.

ssuchanowski on Jun 17, 2016

Thanks for the report!

vpolouchkine on Jun 15, 2016