fastlane: Binary upload invalid / [!] {"data"=>nil, "messages"=>{"warn"=>nil, "error"=>["ITC.response.error.OPERATION_FAILED"], "info"=>nil}, "statusCode"=>"ERROR"}
New Issue Checklist
- Updated fastlane to the latest version
- I have read the Contribution Guidelines
Issue Description
Complete output when running fastlane, including the stack trace and command used
fastlane ios beta --verbose
INSERT OUTPUT HERE
WARN [2016-10-05 17:37:14.91]: [Transporter Warning Output]: WARNING ITMS-90686: "The binary you uploaded was invalid."
INFO [2016-10-05 17:37:14.97]: iTunes Transporter successfully finished its job
DEBUG [2016-10-05 17:37:14.97]: [Transporter]: DBG-X: Returning 0
WARN [2016-10-05 17:37:15.06]: WARNING ITMS-90686: "The binary you uploaded was invalid."
INFO [2016-10-05 17:37:15.06]: ------------------------------------------------------------------------------------------------------
INFO [2016-10-05 17:37:15.06]: Successfully uploaded package to iTunes Connect. It might take a few minutes until it's visible online.
INFO [2016-10-05 17:37:15.06]: ------------------------------------------------------------------------------------------------------
INFO [2016-10-05 17:37:15.06]: Successfully uploaded the new binary to iTunes Connect
INFO [2016-10-05 17:37:15.06]: If you want to skip waiting for the processing to be finished, use the `skip_waiting_for_build_processing` option
INFO [2016-10-05 17:37:15.06]: Waiting for iTunes Connect to process the new build
WARN [2016-10-05 17:37:50.59]: Variable Dump:
INFO [2016-10-05 17:37:50.59]: {:DEFAULT_PLATFORM=>:ios, :PLATFORM_NAME=>:ios, :LANE_NAME=>"ios beta", :CERT_FILE_PATH=>"/Users/wkwyatt/Desktop/Narwhal/GMP/gmp-app/client_ionic_app/platforms/ios/ALXA7RWN88.cer", :CERT_CERTIFICATE_ID=>"ALXA7RWN88", :SIGH_PROFILE_PATH=>"/Users/wkwyatt/Desktop/Narwhal/GMP/gmp-app/client_ionic_app/platforms/ios/AppStore_com.coke.gmp.mobileprovision", :SIGH_PROFILE_PATHS=>["/Users/wkwyatt/Desktop/Narwhal/GMP/gmp-app/client_ionic_app/platforms/ios/AppStore_com.coke.gmp.mobileprovision"], :SIGH_UDID=>"b0c41025-d392-4c13-8465-b3b35b59b292", :SIGH_PROFILE_TYPE=>"app-store", :IPA_OUTPUT_PATH=>"/Users/wkwyatt/Desktop/Narwhal/GMP/gmp-app/client_ionic_app/platforms/ios/GMP.ipa", :DSYM_OUTPUT_PATH=>"/Users/wkwyatt/Desktop/Narwhal/GMP/gmp-app/client_ionic_app/platforms/ios/GMP.app.dSYM.zip", :XCODEBUILD_ARCHIVE=>"/Users/wkwyatt/Library/Developer/Xcode/Archives/2016-10-05/GMP 2016-10-05 17.35.30.xcarchive"}
ERROR [2016-10-05 17:37:50.59]: {"data"=>nil, "messages"=>{"warn"=>nil, "error"=>["ITC.response.error.OPERATION_FAILED"], "info"=>nil}, "statusCode"=>"ERROR"}
INFO [2016-10-05 17:37:50.63]: Successfully generated documentation at path '/Users/wkwyatt/Desktop/Narwhal/GMP/gmp-app/client_ionic_app/platforms/ios/fastlane/README.md'
+------+-------------------------------------+-------------+
| fastlane summary |
+------+-------------------------------------+-------------+
| Step | Action | Time (in s) |
+------+-------------------------------------+-------------+
| 1 | Verifying required fastlane version | 0 |
| 2 | default_platform | 0 |
| 3 | cert | 7 |
| 4 | sigh | 4 |
| 5 | gym | 61 |
| 6 | pilot | 83 |
+------+-------------------------------------+-------------+
ERROR [2016-10-05 17:37:50.71]: fastlane finished with errors
Looking for related GitHub issues on fastlane/fastlane...
Search query: {"data"=>nil, "messages"=>{"warn"=>nil, "error"=>["ITC.response.error.OPERATION_FAILED"], "info"=>nil}, "statusCode"=>"ERROR"}
URL: https://api.github.com/search/issues?q=%7B%22data%22=%3Enil,%20%22messages%22=%3E%7B%22warn%22=%3Enil,%20%22error%22=%3E[%22ITC.response.error.OPERATION_FAILED%22],%20%22info%22=%3Enil%7D,%20%22statusCode%22=%3E%22ERROR%22%7D+repo:fastlane/fastlane
Found no similar issues. To create a new issue, please visit:
https://github.com/fastlane/fastlane/issues/new
#######################################################################
# fastlane 1.105.0 is available. You are on 1.104.0.
# It is recommended to use the latest version.
# Update using 'sudo gem update fastlane'.
#######################################################################
# Run `sudo gem cleanup` from time to time to speed up fastlane
#######################################################################
1.105.0 Xcode 8 and macOS Sierra
* Improve documentation of all _fastlane_ actions
* New [actions docs](https://docs.fastlane.tools/actions)
* Improved support for macOS Sierra
* Improved support for Xcode 8
* Improve output of `fastlane_version` action (#6393)
* Add listing of plugins and their actions in Actions.md
* Switch to new Fastlane::ROOT method to fetch gem resources
* Update `xcpretty` dependency to 0.2.3 (#6323)
* Show š„ when a fastlane step fails
* Ignore SIGH_PROFILE_PATH when using newer api (#6347)
* Add `rake update_dependencies` to automatically update internal dependencies (#6326)
* Update internal dependencies
Update using 'sudo gem update fastlane'
/Users/wkwyatt/.rvm/gems/ruby-2.2.3@global/gems/spaceship-0.34.2/lib/spaceship/client.rb:453:in `parse_response': [!] {"data"=>nil, "messages"=>{"warn"=>nil, "error"=>["ITC.response.error.OPERATION_FAILED"], "info"=>nil}, "statusCode"=>"ERROR"} (Spaceship::Client::UnexpectedResponse)
from /Users/wkwyatt/.rvm/gems/ruby-2.2.3@global/gems/spaceship-0.34.2/lib/spaceship/tunes/tunes_client.rb:527:in `build_trains'
from /Users/wkwyatt/.rvm/gems/ruby-2.2.3@global/gems/spaceship-0.34.2/lib/spaceship/tunes/build_train.rb:51:in `all'
from /Users/wkwyatt/.rvm/gems/ruby-2.2.3@global/gems/spaceship-0.34.2/lib/spaceship/tunes/application.rb:205:in `build_trains'
from /Users/wkwyatt/.rvm/gems/ruby-2.2.3@global/gems/spaceship-0.34.2/lib/spaceship/tunes/application.rb:243:in `all_processing_builds'
from /Users/wkwyatt/.rvm/gems/ruby-2.2.3@global/gems/pilot-1.10.1/lib/pilot/build_manager.rb:127:in `block in wait_for_processing_build'
from /Users/wkwyatt/.rvm/gems/ruby-2.2.3@global/gems/pilot-1.10.1/lib/pilot/build_manager.rb:116:in `loop'
from /Users/wkwyatt/.rvm/gems/ruby-2.2.3@global/gems/pilot-1.10.1/lib/pilot/build_manager.rb:116:in `wait_for_processing_build'
from /Users/wkwyatt/.rvm/gems/ruby-2.2.3@global/gems/pilot-1.10.1/lib/pilot/build_manager.rb:34:in `upload'
from /Users/wkwyatt/.rvm/gems/ruby-2.2.3/gems/fastlane-1.104.0/lib/fastlane/actions/pilot.rb:18:in `run'
from /Users/wkwyatt/.rvm/gems/ruby-2.2.3/gems/fastlane-1.104.0/lib/fastlane/runner.rb:202:in `block (2 levels) in execute_action'
from /Users/wkwyatt/.rvm/gems/ruby-2.2.3/gems/fastlane-1.104.0/lib/fastlane/actions/actions_helper.rb:35:in `execute_action'
from /Users/wkwyatt/.rvm/gems/ruby-2.2.3/gems/fastlane-1.104.0/lib/fastlane/runner.rb:187:in `block in execute_action'
from /Users/wkwyatt/.rvm/gems/ruby-2.2.3/gems/fastlane-1.104.0/lib/fastlane/runner.rb:186:in `chdir'
from /Users/wkwyatt/.rvm/gems/ruby-2.2.3/gems/fastlane-1.104.0/lib/fastlane/runner.rb:186:in `execute_action'
from /Users/wkwyatt/.rvm/gems/ruby-2.2.3/gems/fastlane-1.104.0/lib/fastlane/runner.rb:112:in `trigger_action_by_name'
from /Users/wkwyatt/.rvm/gems/ruby-2.2.3/gems/fastlane-1.104.0/lib/fastlane/fast_file.rb:140:in `method_missing'
from Fastfile:38:in `block (2 levels) in parsing_binding'
from /Users/wkwyatt/.rvm/gems/ruby-2.2.3/gems/fastlane-1.104.0/lib/fastlane/lane.rb:33:in `call'
from /Users/wkwyatt/.rvm/gems/ruby-2.2.3/gems/fastlane-1.104.0/lib/fastlane/lane.rb:33:in `call'
from /Users/wkwyatt/.rvm/gems/ruby-2.2.3/gems/fastlane-1.104.0/lib/fastlane/runner.rb:49:in `block in execute'
from /Users/wkwyatt/.rvm/gems/ruby-2.2.3/gems/fastlane-1.104.0/lib/fastlane/runner.rb:45:in `chdir'
from /Users/wkwyatt/.rvm/gems/ruby-2.2.3/gems/fastlane-1.104.0/lib/fastlane/runner.rb:45:in `execute'
from /Users/wkwyatt/.rvm/gems/ruby-2.2.3/gems/fastlane-1.104.0/lib/fastlane/lane_manager.rb:46:in `cruise_lane'
from /Users/wkwyatt/.rvm/gems/ruby-2.2.3/gems/fastlane-1.104.0/lib/fastlane/command_line_handler.rb:30:in `handle'
from /Users/wkwyatt/.rvm/gems/ruby-2.2.3/gems/fastlane-1.104.0/lib/fastlane/commands_generator.rb:49:in `block (2 levels) in run'
from /Users/wkwyatt/.rvm/gems/ruby-2.2.3/gems/commander-4.4.0/lib/commander/command.rb:178:in `call'
from /Users/wkwyatt/.rvm/gems/ruby-2.2.3/gems/commander-4.4.0/lib/commander/command.rb:178:in `call'
from /Users/wkwyatt/.rvm/gems/ruby-2.2.3/gems/commander-4.4.0/lib/commander/command.rb:153:in `run'
from /Users/wkwyatt/.rvm/gems/ruby-2.2.3/gems/commander-4.4.0/lib/commander/runner.rb:444:in `run_active_command'
from /Users/wkwyatt/.rvm/gems/ruby-2.2.3@global/gems/fastlane_core-0.52.1/lib/fastlane_core/ui/fastlane_runner.rb:36:in `run!'
from /Users/wkwyatt/.rvm/gems/ruby-2.2.3/gems/commander-4.4.0/lib/commander/delegates.rb:15:in `run!'
from /Users/wkwyatt/.rvm/gems/ruby-2.2.3/gems/fastlane-1.104.0/lib/fastlane/commands_generator.rb:246:in `run'
from /Users/wkwyatt/.rvm/gems/ruby-2.2.3/gems/fastlane-1.104.0/lib/fastlane/commands_generator.rb:20:in `start'
from /Users/wkwyatt/.rvm/gems/ruby-2.2.3/gems/fastlane-1.104.0/lib/fastlane/cli_tools_distributor.rb:58:in `take_off'
from /Users/wkwyatt/.rvm/gems/ruby-2.2.3/gems/fastlane-1.104.0/bin/fastlane:5:in `<top (required)>'
from /Users/wkwyatt/.rvm/gems/ruby-2.2.3/bin/fastlane:23:in `load'
from /Users/wkwyatt/.rvm/gems/ruby-2.2.3/bin/fastlane:23:in `<main>'
from /Users/wkwyatt/.rvm/gems/ruby-2.2.3/bin/ruby_executable_hooks:15:in `eval'
from /Users/wkwyatt/.rvm/gems/ruby-2.2.3/bin/ruby_executable_hooks:15:in `<main>'
Configuration Files
Please copy the complete content of your Fastfile and any other configuration files you use below:
Fastfile:
# INSERT CONTENT HERE
# Customise this file, documentation can be found here:
# https://github.com/fastlane/fastlane/tree/master/docs
# All available actions: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Actions.md
# can also be listed using the `fastlane actions` command
# Change the syntax highlighting to Ruby
# All lines starting with a # are ignored when running `fastlane`
# If you want to automatically update fastlane if a new version is available:
# update_fastlane
# This is the minimum version number required.
# Update this, if you use features of a newer version
fastlane_version "1.81.0"
default_platform :ios
platform :ios do
before_all do
# increment_build_number()
# ENV["SLACK_URL"] = "https://hooks.slack.com/services/..."
end
desc "Runs all the tests"
lane :test do
scan
end
desc "Submit a new Beta Build to Apple TestFlight"
desc "This will also make sure the profile is up to date"
lane :beta do
# match(type: "appstore") # more information: https://codesigning.guide
cert
sigh
gym(scheme: "GMP") # Build your app - more options available
pilot
# testflight
# sh "your_script.sh"
# You can also use other beta testing services here (run `fastlane actions`)
end
desc "Deploy a new version to the App Store"
lane :appstore do
# match(type: "appstore")
# snapshot
gym(scheme: "GMP") # Build your app - more options available
deliver(force: true)
# frameit
end
# You can define as many lanes as you want
after_all do |lane|
# This block is called, only if the executed lane was successful
# slack(
# message: "Successfully deployed new App Update."
# )
end
error do |lane, exception|
# slack(
# message: exception.message,
# success: false
# )
end
end
# More information about multiple platforms in fastlane: https://github.com/fastlane/fastlane/blob/master/docs/Platforms.md
# All available actions: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Actions.md
# fastlane reports which actions are used
# No personal data is recorded. Learn more at https://github.com/fastlane/enhancer
Environment
fastlane version (run fastlane -v):
1.104.0
Do you use bundler to execute fastlane (i.e. bundle exec fastlane)?
no
Do you use a Ruby environment manager (e.g. chruby, rbenv, rvm)?
no
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Reactions: 15
- Comments: 84 (18 by maintainers)
Commits related to this issue
- Automaticaly retry failed requests on an internal server error for iTunes Connect Fixes https://github.com/fastlane/fastlane/issues/6419#issuecomment-275291403 — committed to fastlane/fastlane by KrauseFx 7 years ago
- Automaticaly retry failed requests on an internal server error for iTunes Connect (#8006) * Automaticaly retry failed requests on an internal server error for iTunes Connect Fixes https://github.c... — committed to fastlane/fastlane by KrauseFx 7 years ago
- Automaticaly retry failed requests on an internal server error for iTunes Connect Fixes https://github.com/fastlane/fastlane/issues/6419#issuecomment-275321850 — committed to fastlane/fastlane by KrauseFx 7 years ago
- Automaticaly retry failed requests on an internal server error for iTunesConnect (#8017) * Automaticaly retry failed requests on an internal server error for iTunes Connect Fixes https://github.co... — committed to fastlane/fastlane by KrauseFx 7 years ago
Iām bumping this, because itās still an issue. I canāt really see a pattern, it just looks like iTC sometimes responds with an error.
It would be really great if
pilotcould retry the request a few times before aborting the whole operation.@KrauseFx I tested the patch and it worked for 2 distributions in a row, will continue to test but it looks like it is working as advertised š thanks!
We are also experiencing this irregularly with our nightly deploys.
Sometimes we get the error described here, sometimes we get āError receiving the newly uploaded binary, please check iTunes Connectā. And sometimes all works well.
This makes automatic distributing to external testflight users via fastlane/pilot almost useless for us at the moment.
Wouldn“t it be possible to address such issues with some internal (configurable) retry mechanism in pilot? Although this would be an ugly workaround for Apple“s instability, it would make the fastlane tools much more reliable and usable.
Thereās an outage right now fyi. https://developer.apple.com/system-status/
I have a PR ready, you can already test: https://github.com/fastlane/fastlane/pull/7762 some more unit tests are needed, but this should be working already š
@jonstjohn Thanks for sharing, thatās the same kind of error though:
Iāve made great progress on this š Thanks for all your help
Hey everyone, thanks for reporting this issue. Itās definitely something we want to improve, however itās really hard. Not only is the server out of our control, but also itās hard to reproduce the issue, to try out if a certain fix works. Iāll give my best to add some kind of re-try logic for this use-case.
Can confirm that this is still happening as I have only red builds over the last 4 days, but am still getting the TestFlight updates (it builds, but then they always drop off at the
Waiting for iTunes Connect to finish processing the new buildpart).Iām again receiving the error āITC.response.error.OPERATION_FAILEDā My fastlane build waited 20 minutes the processing and then I received the ITC error and fastlane failed, but the test flight build is on test flight as usual.
I just disabled the pilot build validation (PILOT_SKIP_WAITING_FOR_BUILD_PROCESSING) and submitted another build and all is good.
Any news about it?
Iām also having this issue. Some points align with what others have said, some not.
With our issue:
gymandpiloton the command line, I get an error explaining the the build was already uploaded, yet I still canāt see it in iTCThese points would suggest that something is wrong with iTC, particularly with builds not being visible anymore and the build apparently still being on iTC.
Iāve now made a new build, changing the build number and have uploaded it successfully with Application Loader. Still waiting for it to process. Hopefully it finishes soon š.
After a quick check on Twitter, to go along with the many other links people are posting, Iāve found that lots of other people are having this issue too. With missing builds and all:
Just search Twitter for
iTunes Connect.Ok Guys I should have found the solution. At least right now I just had a clean successful build. Thank to this thread https://forums.developer.apple.com/thread/64988 and what āmatthartā written i figured out the solution.
Basically the issue is that your Project Capabilities switch state doesnāt reflect the Provisioning Portal AppID Services.
@dusek Thanks for letting me know. There has been some performance degradation on the iTC API in the past few days. Let me know if you see this again! Thanks š