[spaceship, pilot] Getting "410 gone"

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description

Managed to upload ipa to testflight but getting 410 when waiting for the build to be processed. Noticed that pilot builds also fails.
Command executed

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

 $ fastlane pilot builds
[✔] 🚀
[14:20:45]: fastlane detected a Gemfile in the current directory
[14:20:45]: however it seems like you don't use `bundle exec`
[14:20:45]: to launch fastlane faster, please use
[14:20:45]:
[14:20:45]: $ bundle exec fastlane pilot builds
[14:20:45]:
[14:20:45]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
[14:20:46]: Login to App Store Connect<EMAIL_ADDRESS>[14:20:49]: Login successful
Looking for related GitHub issues on fastlane/fastlane...
/Users/stefano/.rvm/gems/ruby-2.4.1/gems/fastlane-2.119.0/spaceship/lib/spaceship/test_flight/client.rb:321:in `handle_response': [!]  (Spaceship::UnexpectedResponse)

Error 410 Gone

HTTP ERROR 410
Problem accessing /v2/providers/118458784/apps/1383073333/platforms/ios/trains. Reason:
    Gone

from /Users/stefano/.rvm/gems/ruby-2.4.1/gems/fastlane-2.119.0/spaceship/lib/spaceship/test_flight/client.rb:31:in `get_build_trains'
from /Users/stefano/.rvm/gems/ruby-2.4.1/gems/fastlane-2.119.0/spaceship/lib/spaceship/test_flight/build_trains.rb:16:in `all'
from /Users/stefano/.rvm/gems/ruby-2.4.1/gems/fastlane-2.119.0/spaceship/lib/spaceship/test_flight/build.rb:110:in `all'
from /Users/stefano/.rvm/gems/ruby-2.4.1/gems/fastlane-2.119.0/spaceship/lib/spaceship/test_flight/build.rb:121:in `all_processing_builds'
from /Users/stefano/.rvm/gems/ruby-2.4.1/gems/fastlane-2.119.0/spaceship/lib/spaceship/tunes/application.rb:321:in `all_processing_builds'
from /Users/stefano/.rvm/gems/ruby-2.4.1/gems/fastlane-2.119.0/pilot/lib/pilot/build_manager.rb:111:in `list'
from /Users/stefano/.rvm/gems/ruby-2.4.1/gems/fastlane-2.119.0/pilot/lib/pilot/commands_generator.rb:90:in `block (2 levels) in run'
from /Users/stefano/.rvm/gems/ruby-2.4.1/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in `call'
from /Users/stefano/.rvm/gems/ruby-2.4.1/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in `run'
from /Users/stefano/.rvm/gems/ruby-2.4.1/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in `run_active_command'
from /Users/stefano/.rvm/gems/ruby-2.4.1/gems/fastlane-2.119.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in `run!'
from /Users/stefano/.rvm/gems/ruby-2.4.1/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in `run!'
from /Users/stefano/.rvm/gems/ruby-2.4.1/gems/fastlane-2.119.0/pilot/lib/pilot/commands_generator.rb:166:in `run'
from /Users/stefano/.rvm/gems/ruby-2.4.1/gems/fastlane-2.119.0/pilot/lib/pilot/commands_generator.rb:18:in `start'
from /Users/stefano/.rvm/gems/ruby-2.4.1/gems/fastlane-2.119.0/fastlane/lib/fastlane/cli_tools_distributor.rb:111:in `take_off'
from /Users/stefano/.rvm/gems/ruby-2.4.1/gems/fastlane-2.119.0/bin/fastlane:23:in `<top (required)>'
from /Users/stefano/.rvm/gems/ruby-2.4.1/bin/fastlane:23:in `load'
from /Users/stefano/.rvm/gems/ruby-2.4.1/bin/fastlane:23:in `'

For reference: This was also reported (and highly upvoted) at https://github.com/fastlane/fastlane/issues/14476#issuecomment-479638532

This is definitely an issue with AppStore Connect. I got the same error after uploading a build to TestFlight, and now there are two builds processing, which had NEVER happened to me before.

I am receiving this issue as well.  On top of the getting the latest build number is not working either.

I am receiving this issue as well. On top of the getting the latest build number is not working either.

Are you getting:
You have to specify a new version number, as there are multiple to choose from

Yes even though I only have 1 version number and I deployed last night with no issues

Suffering from the same issue. Wondering if it's a Connect issue...

Still getting 410 but builds started to be processed

Heyyy! Are people still receiving these errors or is App Store Connect back to normal?

@joshdholtz hey, still getting it. Error for fastlane pilot builds:
bundler: failed to load command: fastlane (/usr/local/lib/ruby/gems/2.5.0/bin/fastlane)
Spaceship::UnexpectedResponse: [!]

<meta http-equiv="Content-Type" content="text/html;charset=utf-8"/>
<title>Error 410 Gone</title>

HTTP ERROR 410

Problem accessing /v2/providers/xxxx/apps/xxxxx/platforms/ios/trains. Reason:

    Gone

Seems to be an issue with App Store Connect.

Still getting the error with Fastlane although manual release to tesflight via App Store Connect works.

Problem accessing /v2/providers/xxxx/apps/xxxxx/platforms/ios/trains. Reason:

    Gone

RIP this route ☠ Will look into to see what we can replace it with 🙃

Did they really remove an API endpoint without notice?

@ishegg Yuuuupppp! This is not the first time and its bound to happen again. A lot of fastlane still relies on the old private APIs. We will be working on adapting what we can to the new App Store Connect APIs but we can only use the ones that the App Store Connect dashboard uses since those are the ones are valid with the session tokens that we use 😇 Will let you know when I got this put back together 💪

/v2/providers/xxxx/apps/xxxx/groups - API used for retrieving the TestFlight groups, seems also broken for us:
\n\n<meta http-equiv="Content-Type" content="text/html;charset=utf-8"/>\n<title>Error 410 Gone</title>\n\n
HTTP ERROR 410
\n
Problem accessing /v2/providers/xxxx/apps/xxxx/groups. Reason:\n
    Gone

\n\n

Anyone facing the same issue?

@joabalea Noooooooooo 😱 This........... might be a challenge 😬😬😬😬😬😬😬😬 I will do what I can to get this working as fast as I can for all of you!

@joshdholtz thanks for your hard work. Any way we can help? I tried inspecting the traffic on AppStore Connect but I can't find anything helpful.

Keep posting any new broken endpoints 🙃 I have a few pilot setups that I will test myself so I should hit stuff but for now any new broken ones would be 💯 I will probably need some of you to test a branch (once I make one) with my fixes in it to see if they work for when whenever I get that far 💪

Apple still seems to be using those endpoints 🤔
tf.tidbits.min.5f90db1f60.js:1905
}), t.rPrefix = "/testflight/v2/providers/:providerId/apps/:adamID/", t.apiPrefix = "/iris", t.cache = {}, t.topics = {}, t.normalize = a["default"], t.initResources(), t

They might still be referencing it but no necessarily using it 🤔

@joshdholtz
facing the same issue - latest TestFlight build number returning inappropriate value
Let me know if you need any help.

I'm also facing this issue

I appreciated everyone offering any help ❤ I think the biggest thing here would just be patience 😇 This is a pretty breaking change that Apple made so I'm going to be touching a lot of bits of code to here 🤞

Update 1
Got fastlane pilot builds "working" again. The code is not great but it works which is the first step. This should now help me put together the rest of pilot 🤞
➜  test-ios git:(dude-release-hey) ✗ fl pilot builds
[✔] 🚀
[21:55:06]: Login to App Store Connect
[21:55:08]: Login successful
+-----------+---------+----------+
|    FastlaneTest Josh Builds    |
+-----------+---------+----------+
| Version # | Build # | Installs |
+-----------+---------+----------+
| 1.0.0     | 189     | 0        |
| 1.0.0     | 188     | 0        |
| 1.0.0     | 187     | 0        |
| 1.0.0     | 185     | 0        |
| 1.0.0     | 184     | 0        |
| 1.0.0     | 183     | 0        |
| 1.0.0     | 182     | 0        |
| 1.0.0     | 181     | 0        |
| 1.0.0     | 180     | 0        |
| 1.0.0     | 174     | 0        |
+-----------+---------+----------+

BTW... nobody installs my apps 😇 Those 0s are correct 😢

I'm super close but I need to get some 💤s now 😔 Hopefully I can butotn some things up here in the morning 🤞

I'm here to help out, if there is anything I can do, let me know

I have same problem with fastlane pilot builds
When i try to get active build throughout fastlane pilot i get following error
bundle exec fastlane pilot builds --verbose
[✔] 🚀
Successfully loaded Appfile at path '<project-root>/fastlane/Appfile'
- app_identifier: '<app-identifier>'
- apple_id: '<my-apple-id>'
- team_name: '<team-name>'
- team_id: <team-id>'
-------
INFO [2019-04-04 13:20:27.88]: Login to App Store Connect (----------)
Reading keychain entry, because either user or password were empty
Loading session from '----------'
Looking for App Store Connect Team with ID ------
INFO [2019-04-04 13:20:31.02]: Login successful
DEBUG [2019-04-04 13:20:31.02]: App identifier (----)

Looking for related GitHub issues on fastlane/fastlane...
Search query:

<meta http-equiv="Content-Type" content="text/html;charset=utf-8"/>
<title>Error 410 Gone</title>

HTTP ERROR 410

Problem accessing /v2/providers/<my-team-id>/apps/<my-app-id>/platforms/ios/trains. Reason:

    Gone

URL: https://api.github.com/search/issues?q=%3Chtml%3E%0A%3Chead%3E%0A%3Cmeta%20http-equiv%3D%22Content-Type%22%20content%3D%22text%2Fhtml%3Bcharset%3Dutf-8%22%2F%3E%0A%3Ctitle%3EError%20410%20Gone%3C%2Ftitle%3E%0A%3C%2Fhead%3E%0A%3Cbody%3E%3Ch2%3EHTTP%20ERROR%20410%3C%2Fh2%3E%0A%3Cp%3EProblem%20accessing%20%2Fv2%2Fproviders%2F1104328%2Fapps%2F880549869%2Fplatforms%2Fios%2Ftrains.%20Reason%3A%0A%3Cpre%3E%20%20%20%20Gone%3C%2Fpre%3E%3C%2Fp%3E%0A%3C%2Fbody%3E%0A%3C%2Fhtml%3E%0A+repo:fastlane/fastlane
ERROR [2019-04-04 13:20:33.35]: Error finding relevant GitHub issues: undefined method `map' for nil:NilClass
bundler: failed to load command: fastlane (------)
Spaceship::UnexpectedResponse: [!]

<meta http-equiv="Content-Type" content="text/html;charset=utf-8"/>
<title>Error 410 Gone</title>

HTTP ERROR 410

Problem accessing /v2/providers/<my-team-id>/apps/<my-app-id>/platforms/ios/trains. Reason:

    Gone

...
...

Looks that ale credentials are set up correclty. I can upload ipa file for test flight using same credentials, but can not list acitve builds.
Right now this problem is not critical for our workflow, but will be nice to have this working again. Works withou any problems day or two ago.

I really appreciate the quick action that's being taken to resolve this. To be clear: the actual deployment process still works (the pushed build will be processed and becomes active). Once that's finished, I manually kick of the rest of the steps in a separate lane for now, and everything works there as well (like getting the build number). So it's not a huge issue, just a minor inconvenience.

@joshdholtz
facing the same issue - latest TestFlight build number returning inappropriate value
Let me know if you need any help.

@ramnac Is this related to the same issue? The action latest_testflight_build_number keeps returning version 0 even when we have builds in TestFlight in the store.

@joshdholtz
facing the same issue - latest TestFlight build number returning inappropriate value
Let me know if you need any help.

@ramnac Is this related to the same issue? The action latest_testflight_build_number keeps returning version 0 even when we have builds in TestFlight in the store.

Yes @adamirowe, the error is exactly the same

@adamirowe That is probably exactly why 🙄 I'm currently working on retrofitting the Spaceship::TestFlight::Build methods and FastlaneCore::BuildWatcher to work with the new APIs that we have to use. Hoping to have this PR up for some testing in a few hours that should solve most things 🤞
Bad thing here is this was a highly used API within fastlane so more things might popup 😬

@joshdholtz Thanks for all your hard work on this.

Not a problem! Pre-thanks for everyone who will be yolo testing branch 🙃

Experiencing the same issue using Spaceshipt while trying to deploy to Heroku:
remote:        Spaceship::UnexpectedResponse:
remote:
remote:        <meta http-equiv="Content-Type" content="text/html;charset=utf-8"/>
remote:        <title>Error 410 Gone</title>
remote:
remote:
HTTP ERROR 410

remote:
Problem accessing /v2/providers/.../apps/.../groups. Reason:
remote:
    Gone

remote:
remote:

I'm not familiar with what pilot or spaceship is, but we are hitting this while running these commands in our Fastfile:
  build_app(scheme: "MyAppNameHere", configuration: "Release", xcargs: "-allowProvisioningUpdates" )
  upload_to_testflight

(@lancedolan pilot is the code "part" that is run when using upload_to_testflight, and spaceship is one more level down that is used by pilot to communicate with Apple's services in the background 🚀 )

Update 2
We can wait for a build again 🎊 (code again is really ugly but we got it up). Apple ended up adding a new App Store Connect API endpoint called buildDeliveries that is a holding spot for builds while they are processing. After a while the build will then appear in builds for a bit and been seen as processing. After a little bit there it will then be shown in builds as VALID 🙄
INFO [2019-04-04 13:46:00.08]: ------------------------------------------------------------------------------------------------------------------
INFO [2019-04-04 13:46:00.08]: --- Successfully uploaded package to App Store Connect. It might take a few minutes until it's visible online. ---
INFO [2019-04-04 13:46:00.08]: ------------------------------------------------------------------------------------------------------------------
INFO [2019-04-04 13:46:00.23]: Successfully uploaded the new binary to App Store Connect
INFO [2019-04-04 13:46:00.23]: If you want to skip waiting for the processing to be finished, use the `skip_waiting_for_build_processing` option
DEBUG [2019-04-04 13:46:00.23]: App Platform (ios)
INFO [2019-04-04 13:46:18.29]: Waiting for App Store Connect to finish processing the new build (1.1 - 204)
INFO [2019-04-04 13:46:58.60]: Waiting for App Store Connect to finish processing the new build (1.1 - 204)
INFO [2019-04-04 13:47:47.79]: Waiting for App Store Connect to finish processing the new build (1.1 - 204)
INFO [2019-04-04 13:48:29.25]: Waiting for App Store Connect to finish processing the new build (1.1 - 204)
INFO [2019-04-04 13:49:11.32]: Waiting for App Store Connect to finish processing the new build (1.1 - 204)
INFO [2019-04-04 13:49:52.10]: Waiting for App Store Connect to finish processing the new build (1.1 - 204)
INFO [2019-04-04 13:50:36.66]: Waiting for App Store Connect to finish processing the new build (1.1 - 204)
INFO [2019-04-04 13:51:17.73]: Waiting for App Store Connect to finish processing the new build (1.1 - 204)
INFO [2019-04-04 13:52:00.72]: Waiting for App Store Connect to finish processing the new build (1.1 - 204)
INFO [2019-04-04 13:52:44.22]: Waiting for App Store Connect to finish processing the new build (1.1 - 204)
INFO [2019-04-04 13:53:27.60]: Waiting for App Store Connect to finish processing the new build (1.1 - 204)
INFO [2019-04-04 13:54:08.66]: Waiting for App Store Connect to finish processing the new build (1.1 - 204)
INFO [2019-04-04 13:54:50.18]: Successfully finished processing the build 1.1 - 204
INFO [2019-04-04 13:54:51.34]: Successfully set the beta_app_feedback_email and/or beta_app_description
INFO [2019-04-04 13:54:53.49]: Successfully set the changelog for build

The final fix is now to fix the /v2/providers/.../apps/.../groups. And THEN clean up some code 💪

@joshdholtz I believe #14476 is related. Any ideas on a fix for that?

@joshdholtz I believe #14476 is related. latest_testflight_build_number fails and always returns 1. Any ideas on a fix for that?

Yes, it's related to that. The latest_testflight_build_number action won't fail as it's inside a begin/rescue and will return the default initial_build_number value (that is 1)

@brandons I think my fixes should do it but if not it should be a similar fix 🙃 I will add that to my list of things to look into as well

@brandons I think my fixes should do it but if not it should be a similar fix 🙃 I will add that to my list of things to look into as well

@joshdholtz I pulled down the branch being worked on and gave it a test drive. I don't get prompted about providing version number anymore but still falling back to the initial_build_number  number looks like. Progress though! :)
[15:51:36]: --- Step: latest_testflight_build_number ---
[15:51:36]: --------------------------------------------
/Users/.../code/fastlane/spaceship/lib/spaceship/connect_api/client.rb:21: warning: circular argument reference - cursor
[15:51:36]: Login to App Store Connect (...)
[15:51:38]: Login successful
[15:51:56]: Fetching the latest build number for version 1.10.0
[15:51:56]: Latest upload for version 1.10.0 is build: 1
[15:51:56]: Result: 1

Why does Apple not give core fastlane devs an update of what is coming ?? Considering how use it is and how often this happens.

Seeing the same issue as @zeulb

We're seeing the same issue here, all builds returning no valid build, so defaulting to 0.

Thanks @joshdholtz!
FYI: we failed on this endpoint only when we tried to kickoff our TestFlight build, starts with creating tester: Spaceship::TestFlight::Tester.create_app_level_tester
<meta http-equiv="Content-Type" content="text/html;charset=utf-8"/><title>Error 410 Gone</title>
HTTP ERROR 410

Problem accessing /v2/providers/xxxx/apps/yyyy/testers. Reason:
    Gone

Our fastlane deliver is still 👍

Any quick tutorials on how to pull this branch and test it in our CI?  I'm not a ruby dev but am facing this exact issue and want to help test the fix.  Using fastlane to build and distribute our Android and iOS builds with Travis.
Thanks for your hard work!

fwiw I'm getting it as well ...

Error 410 Gone

HTTP ERROR 410
Problem accessing /v2/providers/redacted/apps/redacted/platforms/ios/trains. Reason:
    Gone

I found https://github.com/fastlane/fastlane/blob/master/Testing.md#test-your-local-fastlane-code-base-with-your-setup which
Added @joshdholtz's https://github.com/fastlane/fastlane/tree/joshdholtz-pilot-fixes-removed-build-trains branch as a git submodule to my project, changed my Gemfile and ran it on Travis and it all worked perfectly!  Now I just need to make a ticket to remove that when the PR gets merged and I can update fastlane ;)
Thanks @joshdholtz for your work!

P.S. if it has not been mentioned before, regular TestFlight is currently broken as well...
https://forums.developer.apple.com/message/355676

No rush @joshdholtz. We found a way to fix our pipeline meanwhile.

@brandons I think my fixes should do it but if not it should be a similar fix 🙃 I will add that to my list of things to look into as well

@joshdholtz I pulled down the branch being worked on too, as @willdeberry already said, it is still falling back to the initial_build_number. Hopefully there's gonna be a fix for this one soon, I really want to stop worrying about redundant build numbers. Thanks for your work, glad things are moving fast with fastlane as always. Big 👍 !

Great to see the 26 + me participants here. I had JUST got it working fully and then the literal next night it just broke on me. Thank you for the speedy fix! Awesome developers in here

Hi ya'll. @jbruce2112 @paulkite and I came across this issue too, but we tag our releases with the build number.  It has worked pretty well for us and even speeds up our build since we don't need to talk to Apple.
We will probably stick with this solution as well since we create our release tag before uploading to Apple, so if the tagging succeeds, but the upload fails, we would want a higher build number next go around.
We alternately explored saving release numbers in a separate github repo. That solution worked well too, but wasn't as simple as using tags

As a temporary workaround and to help test, I believe you can test the patched branch and run it in CI by changing your Gemfile to:
gem 'fastlane', git: 'https://github.com/fastlane/fastlane.git', branch: 'joshdholtz-pilot-fixes-removed-build-trains'

As a temporary workaround and to help test, I believe you can test the patched branch and run it in CI by changing your Gemfile to:
gem 'fastlane', git: 'https://github.com/fastlane/fastlane.git', branch: 'joshdholtz-pilot-fixes-removed-build-trains'

Whoah! Mind Blown...that's SO much easier than what I did...
https://bundler.io/v1.12/git.html

also getting 410 gone when using pilot add to add testers to an existing build.
23:51:22]:

Error 410 Gone

HTTP ERROR 410
Problem accessing /v2/providers/117111851/apps/952811109/testers. Reason:
    Gone

[!] Some operations failed:

I've tried fastlane update_fastlane and I'm still getting the error. How do I update fastlane to the latest version which works?

I am also facing the same as above in my spaceship

<meta http-equiv="Content-Type" content="text/html;charset=utf-8"/>
<title>Error 410 Gone</title>

HTTP ERROR 410

Problem accessing /v2/providers/119021831/apps/1362469768/platforms/ios/trains. Reason:

    Gone

/.rvm/gems/ruby-2.5.1/gems/fastlane-2.101.1/spaceship/lib/spaceship/test_flight/build_trains.rb:16:in `all'
/.rvm/gems/ruby-2.5.1/gems/fastlane-2.101.1/spaceship/lib/spaceship/test_flight/client.rb:31:in `get_build_trains'
/.rvm/gems/ruby-2.5.1/gems/fastlane-2.101.1/spaceship/lib/spaceship/test_flight/client.rb:326:in `handle_response': [!]  (Spaceship::UnexpectedResponse)

@ahushh use bundle update fastlane to update the fastlane version

Hey people try adding this plugin to use altool because altool works for me. Here is how to add altool

@nihp it works. Thank you!

@bobgodwinx From your above answer I have a clarification
Does the atool will upload the build in testflight? Does it requires to run fastlane init.
Note: I have all the setup for upload to testflight. Shall I need to remove the fastfiles and all?

FWIW I'm happy to test things as well, I'm experiencing the latest_testflight_build_number always returning 0 issue. Thanks for all your hard work @joshdholtz 👍🏻👍🏻.

Hey everyone! I will be finish this up tomorrow 💪 Getting married next week and had a migraine yesterday so life is a bit cray 🙃 But I’m dedicating tomorrow to finishing this up so we can have most of the things working for next week 🤞
Sent with GitHawk

We did it!!! Thanks again for all the patience ❤ Put this in your Gemfile to switch to my branch and run with bundle install or bundle update
gem "fastlane", :git => "https://github.com/fastlane/fastlane.git", :branch => "joshdholtz-pilot-fixes-removed-build-trains"

My next big task is to fix allllllllllll of the tests 😱 But once that tests are fix we can work on getting this merged 💪 And then get a jump start on replacing other APIs that might break soon 😬
My test output
INFO [2019-04-07 16:35:50.61]: ------------------------------------------------------------------------------------------------------------------
INFO [2019-04-07 16:35:50.61]: --- Successfully uploaded package to App Store Connect. It might take a few minutes until it's visible online. ---
INFO [2019-04-07 16:35:50.61]: ------------------------------------------------------------------------------------------------------------------
INFO [2019-04-07 16:35:50.62]: Successfully uploaded the new binary to App Store Connect
INFO [2019-04-07 16:35:50.62]: If you want to skip waiting for the processing to be finished, use the `skip_waiting_for_build_processing` option
DEBUG [2019-04-07 16:35:50.62]: App Platform (ios)
INFO [2019-04-07 16:36:04.30]: Build doesn't show up in the build list anymore, waiting for it to appear again (check your email for processing issues if this continues)
INFO [2019-04-07 16:36:34.86]: Waiting for App Store Connect to finish processing the new build (1.1 - 206)
INFO [2019-04-07 16:37:05.20]: Waiting for App Store Connect to finish processing the new build (1.1 - 206)
INFO [2019-04-07 16:37:37.02]: Waiting for App Store Connect to finish processing the new build (1.1 - 206)
INFO [2019-04-07 16:38:07.28]: Waiting for App Store Connect to finish processing the new build (1.1 - 206)
INFO [2019-04-07 16:38:38.20]: Waiting for App Store Connect to finish processing the new build (1.1 - 206)
INFO [2019-04-07 16:39:08.92]: Waiting for App Store Connect to finish processing the new build (1.1 - 206)
INFO [2019-04-07 16:39:39.20]: Waiting for App Store Connect to finish processing the new build (1.1 - 206)
INFO [2019-04-07 16:40:25.71]: Waiting for App Store Connect to finish processing the new build (1.1 - 206)
INFO [2019-04-07 16:41:07.93]: Waiting for App Store Connect to finish processing the new build (1.1 - 206)
INFO [2019-04-07 16:41:51.28]: Waiting for App Store Connect to finish processing the new build (1.1 - 206)
INFO [2019-04-07 16:42:32.63]: Waiting for App Store Connect to finish processing the new build (1.1 - 206)
INFO [2019-04-07 16:43:12.94]: Waiting for App Store Connect to finish processing the new build (1.1 - 206)
INFO [2019-04-07 16:43:55.04]: Successfully finished processing the build 1.1 - 206
INFO [2019-04-07 16:43:58.06]: Successfully set the beta_app_feedback_email and/or beta_app_description
INFO [2019-04-07 16:44:03.46]: Successfully set the changelog for build
INFO [2019-04-07 16:44:05.47]: Distributing new build to testers: 1.1 - 206
INFO [2019-04-07 16:44:09.59]: Successfully distributed build to External testers

@joshdholtz I am still getting the initial version number when I run
bundle exec fastlane run latest_testflight_build_number
with latest your branch.
Anything I can do to help figure out whats happening there?

Ahhh, I will tackle that one next before working on tests 😇 That's more fun anyway 😉

I updated my Gemfile to point to your branch:
source "https://rubygems.org"
gem 'fastlane', git: 'https://github.com/fastlane/fastlane.git', branch: 'joshdholtz-pilot-fixes-removed-build-trains'

Ran bundle update with relevant output Using fastlane 2.119.0 from https://github.com/fastlane/fastlane.git (at joshdholtz-pilot-fixes-removed-build-trains@e191207)
And then ran my lane. Everything goes smooth until I get to the upload_to_testflight step.
This is the output:
[13:29:23]: ----------------------------------
[13:29:23]: --- Step: upload_to_testflight ---
[13:29:23]: ----------------------------------
[13:29:23]: Login to App Store Connect<EMAIL_ADDRESS>[13:29:28]: Login successful
[13:29:29]: Ready to upload new build to TestFlight (App:<PHONE_NUMBER>)...
[13:29:52]: iTunes Transporter successfully finished its job
[13:29:52]: Going to upload updated app to App Store Connect
[13:29:52]: This might take a few minutes. Please don't interrupt the script.
[13:38:45]: iTunes Transporter successfully finished its job
[13:38:45]: ------------------------------------------------------------------------------------------------------------------
[13:38:45]: --- Successfully uploaded package to App Store Connect. It might take a few minutes until it's visible online. ---
[13:38:45]: ------------------------------------------------------------------------------------------------------------------
[13:38:45]: Successfully uploaded the new binary to App Store Connect
[13:38:45]: If you want to skip waiting for the processing to be finished, use the `skip_waiting_for_build_processing` option
+------------------------------------+---------------------------------------------------------------------------------+
|                                                     Lane Context                                                     |
+------------------------------------+---------------------------------------------------------------------------------+
| DEFAULT_PLATFORM                   | ios                                                                             |
| PLATFORM_NAME                      | ios                                                                             |
| LANE_NAME                          | ios patch                                                                       |
| GIT_REPO_WAS_CLEAN_ON_START        | true                                                                            |
| BUILD_NUMBER                       | 1                                                                               |
| VERSION_NUMBER                     | 0.3.17                                                                          |
| SIGH_PROFILE_TYPE                  | app-store                                                                       |
| MATCH_PROVISIONING_PROFILE_MAPPING | {"cab.u.driver"=>"match AppStore cab.u.driver"}                                 |
| IPA_OUTPUT_PATH                    | /Users/mario/Projects/ucab-driver/ucabDriver.ipa                                |
| DSYM_OUTPUT_PATH                   | /Users/mario/Projects/ucab-driver/ucabDriver.app.dSYM.zip                       |
| XCODEBUILD_ARCHIVE                 | /Users/mario/Library/Developer/Xcode/Archives/2019-04-08/ucabDriver 2019-04-08  |
|                                    | 13.11.45.xcarchive                                                              |
+------------------------------------+---------------------------------------------------------------------------------+
[13:38:47]:

<meta http-equiv="Content-Type" content="text/html;charset=utf-8"/>
<title>Error 410 Gone</title>

HTTP ERROR 410

Problem accessing /v2/providers/119243127/apps/1441649349/platforms/ios/trains. Reason:

    Gone

+------+--------------------------+-------------+
|               fastlane summary                |
+------+--------------------------+-------------+
| Step | Action                   | Time (in s) |
+------+--------------------------+-------------+
| 1    | default_platform         | 0           |
| 2    | ensure_git_status_clean  | 0           |
| 3    | increment_build_number   | 2           |
| 4    | increment_version_number | 1           |
| 5    | get_version_number       | 0           |
| 6    | commit_version_bump      | 0           |
| 7    | get_version_number       | 0           |
| 8    | add_git_tag              | 0           |
| 9    | push_to_git_remote       | 5           |
| 10   | match                    | 39          |
| 11   | build_app                | 847         |
| 12   | crashlytics              | 215         |
| 💥   | upload_to_testflight     | 563         |
+------+--------------------------+-------------+

[13:38:47]: fastlane finished with errors

Looking for related GitHub issues on fastlane/fastlane...

/Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/spaceship/lib/spaceship/test_flight/client.rb:321:in `handle_response': [!]  (Spaceship::UnexpectedResponse)

<meta http-equiv="Content-Type" content="text/html;charset=utf-8"/>
<title>Error 410 Gone</title>

HTTP ERROR 410

Problem accessing /v2/providers/119243127/apps/1441649349/platforms/ios/trains. Reason:

    Gone

	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/spaceship/lib/spaceship/test_flight/client.rb:31:in `get_build_trains'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/spaceship/lib/spaceship/test_flight/build_trains.rb:16:in `all'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/spaceship/lib/spaceship/test_flight/build.rb:110:in `all'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/spaceship/lib/spaceship/test_flight/build.rb:121:in `all_processing_builds'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/fastlane_core/lib/fastlane_core/build_watcher.rb:38:in `watching_build'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/fastlane_core/lib/fastlane_core/build_watcher.rb:12:in `wait_for_build_processing_to_be_complete'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/pilot/lib/pilot/build_manager.rb:61:in `wait_for_build_processing_to_be_complete'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/pilot/lib/pilot/build_manager.rb:53:in `upload'

Still getting 410 Gone error. Any ideas?

Using fastlane 2.119.0 from https://github.com/fastlane/fastlane.git (at joshdholtz-pilot-fixes-removed-build-trains@e191207)
Bundle updated!
But getting same issue with 410 Gone
`INFO [2019-04-07 23:59:39.32]: Successfully generated documentation at path '/Users/Xcloud/.fastlane/README.md'
+------+---------------------------------+-------------+
|                   fastlane summary                   |
+------+---------------------------------+-------------+
| Step | Action                          | Time (in s) |
+------+---------------------------------+-------------+
| 1    | default_platform                | 0           |
| 2    | upgrade_super_old_xcode_project | 0           |
| 3    | automatic_code_signing          | 0           |
| 4    | increment_build_number          | 1           |
| 5    | build_app                       | 50          |
| 💥   | upload_to_testflight            | 66          |
+------+---------------------------------+-------------+
DEBUG [2019-04-07 23:59:39.33]: All plugins are up to date
ERROR [2019-04-07 23:59:39.33]: fastlane finished with errors
Looking for related GitHub issues on fastlane/fastlane...
Search query:

Error 410 Gone

HTTP ERROR 410
Problem accessing /v2/providers/118735554/apps/1423089930/platforms/ios/trains/1.4.2/builds. Reason:
    Gone

URL: https://api.github.com/search/issues?q=

<meta http-equiv%3D"Content-Type" content%3D"text%2Fhtml%3Bcharset%3Dutf-8"%2F>
<title>Error 410 Gone<%2Ftitle>
<%2Fhead>

HTTP ERROR 410<%2Fh2>

Problem accessing %2Fv2%2Fproviders%2F118735554%2Fapps%2F1423089930%2Fplatforms%2Fios%2Ftrains%2F1.4.2%2Fbuilds. Reason%3A

    Gone<%2Fpre><%2Fp>
<%2Fbody>
<%2Fhtml>
+repo:fastlane/fastlane
ERROR [2019-04-07 23:59:39.76]: Error finding relevant GitHub issues: undefined method `map' for nil:NilClass
Did you mean?  tap
DEBUG [2019-04-07 23:59:39.76]: All plugins are up to date
bundler: failed to load command: fastlane (/Library/Ruby/Gems/2.3.0/bin/fastlane)
Spaceship::UnexpectedResponse: [!]

Error 410 Gone

HTTP ERROR 410
Problem accessing /v2/providers/118735554/apps/1423089930/platforms/ios/trains/1.4.2/builds. Reason:
    Gone

/Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/spaceship/lib/spaceship/test_flight/client.rb:321:in handle_response'   /Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/spaceship/lib/spaceship/test_flight/client.rb:38:in block in get_builds_for_train'
/Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/spaceship/lib/spaceship/client.rb:619:in with_retry'   /Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/spaceship/lib/spaceship/test_flight/client.rb:36:in get_builds_for_train'
/Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/spaceship/lib/spaceship/test_flight/build.rb:115:in builds_for_train'   /Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/fastlane_core/lib/fastlane_core/build_watcher.rb:45:in matching_build'
/Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/fastlane_core/lib/fastlane_core/build_watcher.rb:23:in block in wait_for_build_processing_to_be_complete'   /Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/fastlane_core/lib/fastlane_core/build_watcher.rb:22:in loop'
/Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/fastlane_core/lib/fastlane_core/build_watcher.rb:22:in wait_for_build_processing_to_be_complete'   /Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/pilot/lib/pilot/build_manager.rb:61:in wait_for_build_processing_to_be_complete'
/Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/pilot/lib/pilot/build_manager.rb:53:in upload'   /Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/fastlane/lib/fastlane/actions/upload_to_testflight.rb:16:in run'
/Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/fastlane/lib/fastlane/runner.rb:253:in block (2 levels) in execute_action'   /Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/fastlane/lib/fastlane/actions/actions_helper.rb:50:in execute_action'
/Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/fastlane/lib/fastlane/runner.rb:232:in block in execute_action'   /Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/fastlane/lib/fastlane/runner.rb:227:in chdir'
/Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/fastlane/lib/fastlane/runner.rb:227:in execute_action'   /Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/fastlane/lib/fastlane/runner.rb:157:in trigger_action_by_name'
/Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/fastlane/lib/fastlane/fast_file.rb:154:in method_missing'   Fastfile:40:in block (2 levels) in parsing_binding'
/Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/fastlane/lib/fastlane/lane.rb:33:in call'   /Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/fastlane/lib/fastlane/runner.rb:49:in block in execute'
/Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/fastlane/lib/fastlane/runner.rb:45:in chdir'   /Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/fastlane/lib/fastlane/runner.rb:45:in execute'
/Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/fastlane/lib/fastlane/lane_manager.rb:56:in cruise_lane'   /Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/fastlane/lib/fastlane/command_line_handler.rb:36:in handle'
/Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/fastlane/lib/fastlane/commands_generator.rb:108:in block (2 levels) in run'   /Library/Ruby/Gems/2.3.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in call'
/Library/Ruby/Gems/2.3.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in run'   /Library/Ruby/Gems/2.3.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in run_active_command'
/Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in run!'   /Library/Ruby/Gems/2.3.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in run!'
/Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/fastlane/lib/fastlane/commands_generator.rb:333:in run'   /Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/fastlane/lib/fastlane/commands_generator.rb:41:in start'
/Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/fastlane/lib/fastlane/cli_tools_distributor.rb:119:in take_off'   /Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/bin/fastlane:23:in <top (required)>'
/Library/Ruby/Gems/2.3.0/bin/fastlane:22:in load'   /Library/Ruby/Gems/2.3.0/bin/fastlane:22:in <top (required)>'`

Yes, I'm still getting 410 Gone while trying to upload tf build via upload_to_testflight action. The fastlane is installed with bundler from joshdholtz-pilot-fixes-removed-build-trains@e191207. If you need logs, please, let me know.

Getting 410 Gone here also, have a script built on spaceship to transfer dSYM files from iTunes to Firebase automatically which is currently broken.
/Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/spaceship/lib/spaceship/test_flight/client.rb:321:in `handle_response':  (Spaceship::UnexpectedResponse)

<meta http-equiv="Content-Type" content="text/html;charset=utf-8"/>
<title>Error 410 Gone</title>

HTTP ERROR 410

Problem accessing /v2/providers/272511/apps/610311708/platforms/ios/trains/6.3.9/builds. Reason:

    Gone

	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/spaceship/lib/spaceship/test_flight/client.rb:38:in `block in get_builds_for_train'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/spaceship/lib/spaceship/client.rb:619:in `with_retry'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/spaceship/lib/spaceship/test_flight/client.rb:36:in `get_builds_for_train'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/spaceship/lib/spaceship/test_flight/build.rb:115:in `builds_for_train'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.119.0/spaceship/lib/spaceship/tunes/application.rb:315:in `all_builds_for_train'
	from ./itunes-to-crashlytics.rb:28:in `block in '
	from ./itunes-to-crashlytics.rb:25:in `collect'
	from ./itunes-to-crashlytics.rb:25:in `'

Thanks @joshdholtz for all your hard work. Appreciate!
Still the latest_testflight_build_number issue exists.
Just as a workaround (Took me a lot of time though), i have created a method which can solve the problem (Temporarily) - later this can be merged to the core spaceship.
Add this method to your fastfile. Call this method by passing three parameters.
version:
appleId:
appIdentifier:
You will get the appropriate build number. Uses the AppStoreconnect API
private_lane :latestTestflightBuildNumber do |options|
require "spaceship"
UI.message("Login to App Store Connect (#{options[:appleId]})")
Spaceship::Tunes.login(user = options[:appleId])
Spaceship::Tunes.select_team
UI.message("Login successful")
spaceshipClient = Spaceship::ConnectAPI::Base.client
params = spaceshipClient.build_params(filter: { bundleId: options[:appIdentifier]})
appsResponse = spaceshipClient.request(:get, "apps") do |req|
req.options.params_encoder = Faraday::NestedParamsEncoder
req.params = params
end
UI.user_error!("The bundle identifier - #{options[:appIdentifier]} does not exist in the AppStoreConnect!!!") if appsResponse.body["data"].count==0
UI.user_error!("Looks like there is some problem with the input provided. Please check the app identifier!!!") if appsResponse.body["data"].count>1
appIdFromAppsResponse=appsResponse.body["data"][0]["id"]
preReleaseVersionsResponse = spaceshipClient.request(:get, "apps/#{appIdFromAppsResponse}/preReleaseVersions")
preReleaseFilteredResponse = preReleaseVersionsResponse.body["data"].select { |k| k["attributes"]["version"] == options[:version] }
begin
preReleaseVersionId = preReleaseFilteredResponse[0]["id"]
nonExpiredBuildsResponse = spaceshipClient.get_builds(filter: { expired: true, processingState: "PROCESSING,VALID", preReleaseVersion: "#{preReleaseVersionId}" },limit: 200, includes: "preReleaseVersion")
latestTestflightBuildNumber = (nonExpiredBuildsResponse.max_by{|k| k["attributes"]["version"].to_i }["attributes"]["version"]).to_i
rescue
latestTestflightBuildNumber = "0".to_i
end
end

@mario462 @cubedivone @mwoollard Can you update to the latest commit and try again?! This should do it 🤞 Just pushed some stuff
@ramnac I will have a commit for the latest_testflight_build_number but thanks for posting that in the meantime ❤

NOW pilot/upload_to_testflight, latest_testflight_build_number, and download_dsyms should be back to normal ❤ Put this in your Gemfile to switch to my branch and run with bundle install or bundle update. The latest commit is https://github.com/fastlane/fastlane/pull/14523/commits/e476888f4c537e81885275471890b073a8493b72
gem "fastlane", :git => "https://github.com/fastlane/fastlane.git", :branch => "joshdholtz-pilot-fixes-removed-build-trains"

Let me know if there is anything else that you run into that is busted. In the meantime I'll be fixing all those tests 🔨

@joshdholtz looks good now, thanks a lot!
[15:54:51]: Successfully uploaded package to App Store Connect. It might take a few minutes until it's visible online.
[15:54:51]: --------------------------------------------------------------------
[15:54:51]: Successfully uploaded the new binary to App Store Connect
[15:54:51]: If you want to skip waiting for the processing to be finished, use the `skip_waiting_for_build_processing` option
[15:54:57]: Waiting for App Store Connect to finish processing the new build (1.1.0 - 160)```

Nice work

I just wanted to take 5 minutes to thanks @joshdholtz for the incredible work.
The work desserve last week is an awesome work and help a lot our communauty.
Kudos to you.
 Amazing work @joshdholtz, and very thoughtful to keep everyone informed with the statuses along the way.
Have a great wedding! 🕺

Another big thank you to @joshdholtz for resolving this !

@joshdholtz I'm having a failure here 🤔
NoMethodError: [!] undefined method `empty?' for nil:NilClass
  /Users/vagrant/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/bundler/gems/fastlane-e476888f4c53/pilot/lib/pilot/build_manager.rb:19:in `upload'
  /Users/vagrant/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/bundler/gems/fastlane-e476888f4c53/fastlane/lib/fastlane/actions/upload_to_testflight.rb:16:in `run'
  /Users/vagrant/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/bundler/gems/fastlane-e476888f4c53/fastlane/lib/fastlane/runner.rb:253:in `block (2 levels) in execute_action'
  /Users/vagrant/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/bundler/gems/fastlane-e476888f4c53/fastlane/lib/fastlane/actions/actions_helper.rb:50:in `execute_action'
  /Users/vagrant/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/bundler/gems/fastlane-e476888f4c53/fastlane/lib/fastlane/runner.rb:232:in `block in execute_action'
  /Users/vagrant/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/bundler/gems/fastlane-e476888f4c53/fastlane/lib/fastlane/runner.rb:227:in `chdir'
  /Users/vagrant/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/bundler/gems/fastlane-e476888f4c53/fastlane/lib/fastlane/runner.rb:227:in `execute_action'
  /Users/vagrant/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/bundler/gems/fastlane-e476888f4c53/fastlane/lib/fastlane/runner.rb:157:in `trigger_action_by_name'
  /Users/vagrant/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/bundler/gems/fastlane-e476888f4c53/fastlane/lib/fastlane/fast_file.rb:154:in `method_missing'
  Fastfile:89:in `block (2 levels) in parsing_binding'
  /Users/vagrant/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/bundler/gems/fastlane-e476888f4c53/fastlane/lib/fastlane/lane.rb:33:in `call'
  /Users/vagrant/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/bundler/gems/fastlane-e476888f4c53/fastlane/lib/fastlane/runner.rb:204:in `try_switch_to_lane'
  /Users/vagrant/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/bundler/gems/fastlane-e476888f4c53/fastlane/lib/fastlane/runner.rb:146:in `trigger_action_by_name'
  /Users/vagrant/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/bundler/gems/fastlane-e476888f4c53/fastlane/lib/fastlane/fast_file.rb:154:in `method_missing'
  Fastfile:17:in `block (2 levels) in parsing_binding'
  /Users/vagrant/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/bundler/gems/fastlane-e476888f4c53/fastlane/lib/fastlane/lane.rb:33:in `call'
  /Users/vagrant/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/bundler/gems/fastlane-e476888f4c53/fastlane/lib/fastlane/runner.rb:49:in `block in execute'
  /Users/vagrant/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/bundler/gems/fastlane-e476888f4c53/fastlane/lib/fastlane/runner.rb:45:in `chdir'
  /Users/vagrant/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/bundler/gems/fastlane-e476888f4c53/fastlane/lib/fastlane/runner.rb:45:in `execute'
  /Users/vagrant/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/bundler/gems/fastlane-e476888f4c53/fastlane/lib/fastlane/lane_manager.rb:56:in `cruise_lane'
  /Users/vagrant/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/bundler/gems/fastlane-e476888f4c53/fastlane/lib/fastlane/command_line_handler.rb:36:in `handle'
  /Users/vagrant/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/bundler/gems/fastlane-e476888f4c53/fastlane/lib/fastlane/commands_generator.rb:108:in `block (2 levels) in run'
  /Users/vagrant/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in `call'
  /Users/vagrant/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in `run'
  /Users/vagrant/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in `run_active_command'
  /Users/vagrant/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/bundler/gems/fastlane-e476888f4c53/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in `run!'
  /Users/vagrant/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in `run!'
  /Users/vagrant/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/bundler/gems/fastlane-e476888f4c53/fastlane/lib/fastlane/commands_generator.rb:333:in `run'
  /Users/vagrant/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/bundler/gems/fastlane-e476888f4c53/fastlane/lib/fastlane/commands_generator.rb:41:in `start'
  /Users/vagrant/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/bundler/gems/fastlane-e476888f4c53/fastlane/lib/fastlane/cli_tools_distributor.rb:119:in `take_off'
  /Users/vagrant/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/bundler/gems/fastlane-e476888f4c53/bin/fastlane:23:in `<top (required)>'
  /Users/vagrant/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/bin/fastlane:23:in `load'
  /Users/vagrant/.rbenv/versions/2.5.3/lib/ruby/gems/2.5.0/bin/fastlane:23:in `<top (required)>'

@PatrickNLT are you adding distribute_external to the pilot? That's the same error I had, and I think it's because that parameter is deprecated.

@PatrickNLT Pushed another fix for that! If you want to try running bundle update again you should be 💯

Fixed. Thank you so much @joshdholtz !

It takes not the latest one version for example my latest 1.2.1 but it takes first one 1.1.3
INFO [2019-04-08 06:54:00.74]: ------------------------------------
INFO [2019-04-08 06:54:00.74]: --- Step: increment_build_number ---
INFO [2019-04-08 06:54:00.74]: ------------------------------------
Current version of project is:
    1.2.1
DEBUG [2019-04-08 06:58:57.93]: App Platform (ios)
INFO [2019-04-08 06:59:22.79]: Successfully finished processing the build 1.1.3 - 66
WARN [2019-04-08 06:59:22.79]: Uploaded app 1.2.1 - 66, but received build 1.1.3 - 66. If you want to wait for uploaded build to be finished processing, use the `wait_for_uploaded_build` option

Also i can't see what to test changelog, beta app description in place.

@cubedivone Thanks for the report! Will look into right away

@joshdholtz I am now not getting 1 anymore, but am still getting the wrong number back.
When I run latest_testflight_build_number I get back:
[07:49:41]: --------------------------------------------
[07:49:41]: --- Step: latest_testflight_build_number ---
[07:49:41]: --------------------------------------------
[07:49:41]: Login to App Store Connect (XXXXXXXXX)
[07:49:42]: Login successful
[07:49:42]: Fetching the latest build number for version 1.0
[07:49:43]: Latest upload for version 1.0 is build: 2
[07:49:43]: Result: 2

And from my setup I would expect 134. Anything I can do to help you debug?

@cubedivone I'm not able to replicate the same thing you were 😔 Asking because I can't see your setup but are you sure you incremented the build before you did you upload with pilot/uploaded_to_testflight?
@tberman Is that version correct of 1.0? Or should it really be checking a different version?

@joshdholtz I experienced a similar issue this morning.
  | [08:52:52]: --- Step: get_build_number ---
  | [08:52:52]: ------------------------------
  | [08:52:52]: $ cd /usr/local/var/buildkite-agent/builds/macpro-xeon-standard-1016-shared-1/florianbuerger/flighty && agvtool what-version -terse
  | [08:52:53]: ▸ 92

and later
--------------------------------------------------------------------
--
  | [08:59:44]: Successfully uploaded package to App Store Connect. It might take a few minutes until it's visible online.
  | [08:59:44]: --------------------------------------------------------------------
  | [08:59:44]: Successfully uploaded the new binary to App Store Connect
  | [08:59:44]: If you want to skip waiting for the processing to be finished, use the `skip_waiting_for_build_processing` option
  | [09:00:11]: Started watching build 0.9 - 91 but expected 0.9 - 92
  | [09:00:25]: Successfully finished processing the build 0.9 - 91
  | [09:00:25]: Uploaded app 0.9 - 92, but received build 0.9 - 91. If you want to wait for uploaded build to be finished processing, use the `wait_for_uploaded_build` option
  | [09:00:27]: Successfully set the changelog for build
  | [09:00:29]: Distributing new build to testers: 0.9 - 91

it did update release notes but for the previous release (91). I was on e191207002b2263ff06feb5288d969384c9a448a. I just updated to the latest commit and will report in a bit if the issue is fixed.
Let me know if I can help any better.

I'm still having issues, although now is a different one, same as @PatrickNLT.
It seems that even though I'm running bundle exec fastlane, it tries to execute fastlane as a global command, which cannot be found, since I have fastlane installed via bundler, not globally.
bundler: failed to load command: fastlane (/Library/Ruby/Gems/2.3.0/bin/fastlane)
NoMethodError: [!] undefined method `empty?' for nil:NilClass
  /Users/mario/.bundle/ruby/2.3.0/fastlane-e476888f4c53/pilot/lib/pilot/build_manager.rb:19:in `upload'
  /Users/mario/.bundle/ruby/2.3.0/fastlane-e476888f4c53/fastlane/lib/fastlane/actions/upload_to_testflight.rb:16:in `run'
  /Users/mario/.bundle/ruby/2.3.0/fastlane-e476888f4c53/fastlane/lib/fastlane/runner.rb:253:in `block (2 levels) in execute_action'
  /Users/mario/.bundle/ruby/2.3.0/fastlane-e476888f4c53/fastlane/lib/fastlane/actions/actions_helper.rb:50:in `execute_action'
  /Users/mario/.bundle/ruby/2.3.0/fastlane-e476888f4c53/fastlane/lib/fastlane/runner.rb:232:in `block in execute_action'
  /Users/mario/.bundle/ruby/2.3.0/fastlane-e476888f4c53/fastlane/lib/fastlane/runner.rb:227:in `chdir'
  /Users/mario/.bundle/ruby/2.3.0/fastlane-e476888f4c53/fastlane/lib/fastlane/runner.rb:227:in `execute_action'
  /Users/mario/.bundle/ruby/2.3.0/fastlane-e476888f4c53/fastlane/lib/fastlane/runner.rb:157:in `trigger_action_by_name'
  /Users/mario/.bundle/ruby/2.3.0/fastlane-e476888f4c53/fastlane/lib/fastlane/fast_file.rb:154:in `method_missing'
  Fastfile:55:in `common_actions'
  Fastfile:21:in `block (2 levels) in parsing_binding'
  /Users/mario/.bundle/ruby/2.3.0/fastlane-e476888f4c53/fastlane/lib/fastlane/lane.rb:33:in `call'
  /Users/mario/.bundle/ruby/2.3.0/fastlane-e476888f4c53/fastlane/lib/fastlane/runner.rb:49:in `block in execute'
  /Users/mario/.bundle/ruby/2.3.0/fastlane-e476888f4c53/fastlane/lib/fastlane/runner.rb:45:in `chdir'
  /Users/mario/.bundle/ruby/2.3.0/fastlane-e476888f4c53/fastlane/lib/fastlane/runner.rb:45:in `execute'
  /Users/mario/.bundle/ruby/2.3.0/fastlane-e476888f4c53/fastlane/lib/fastlane/lane_manager.rb:56:in `cruise_lane'
  /Users/mario/.bundle/ruby/2.3.0/fastlane-e476888f4c53/fastlane/lib/fastlane/command_line_handler.rb:36:in `handle'
  /Users/mario/.bundle/ruby/2.3.0/fastlane-e476888f4c53/fastlane/lib/fastlane/commands_generator.rb:108:in `block (2 levels) in run'
  /Library/Ruby/Gems/2.3.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in `call'
  /Library/Ruby/Gems/2.3.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in `run'
  /Library/Ruby/Gems/2.3.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in `run_active_command'
  /Users/mario/.bundle/ruby/2.3.0/fastlane-e476888f4c53/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in `run!'
  /Library/Ruby/Gems/2.3.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in `run!'
  /Users/mario/.bundle/ruby/2.3.0/fastlane-e476888f4c53/fastlane/lib/fastlane/commands_generator.rb:333:in `run'
  /Users/mario/.bundle/ruby/2.3.0/fastlane-e476888f4c53/fastlane/lib/fastlane/commands_generator.rb:41:in `start'
  /Users/mario/.bundle/ruby/2.3.0/fastlane-e476888f4c53/fastlane/lib/fastlane/cli_tools_distributor.rb:119:in `take_off'
  /Users/mario/.bundle/ruby/2.3.0/fastlane-e476888f4c53/bin/fastlane:23:in `<top (required)>'
  /Library/Ruby/Gems/2.3.0/bin/fastlane:22:in `load'
  /Library/Ruby/Gems/2.3.0/bin/fastlane:22:in `<top (required)>'

@tberman Is that version correct of 1.0? Or should it really be checking a different version?

Version is correct, did some more digging and its because CI has been uploading builds w/ the number of 2 and that have been failing due to duplicate build number while this bug has been ongoing, so the sort by uploadedDate isn't necessarily going to give you what you want.

Same issue on commit f0dbe188ade918b4a77cfbf5a427369e762bfcb6.
$ cd /usr/local/var/buildkite-agent/builds/macpro-xeon-standard-1016-shared-1/florianbuerger/flighty && agvtool what-version -terse
  | [17:21:54]: ▸ 92

Now it fails with The build is not in state for internal testing. - Build is not in internal testing state.
Started watching build 0.8.1 - 88 but expected 0.8.1 - 92
  | [17:29:06]: Successfully finished processing the build 0.8.1 - 88
  | [17:29:06]: Uploaded app 0.8.1 - 92, but received build 0.8.1 - 88. If you want to wait for uploaded build to be finished processing, use the `wait_for_uploaded_build` option
  | [17:29:07]: Successfully set the changelog for build
  | [17:29:12]: Distributing new build to testers: 0.8.1 - 88
  | [17:29:14]: The build is not in state for internal testing. - Build is not in internal testing state.

Different marketing version the from the snippet I posted earlier is correct, it is a different version of the same app. Newest version that was just uploaded is 0.8.1 - 92.
On the previous commit the upload command did not fail though.

@cubedivone @florianbuerger @tberman Do you all have wait_for_uploaded_build: true in your setups? I was testing with wait_for_uploaded_build: false which goes a different route using FastlaneCore::BuildWatcher

No, the relevant part of the Fastfile is
	upload_to_testflight(
		changelog: external_changelog,
		app_identifier: app_identifier,
		distribute_external: true,
		groups: ['Group A', 'Group B']
	)

I just saw that the build log report Using deprecated option: '--distribute_external' (This no longer does anything by itself. Use :groups to distribute externally) which wasn't included before.

I lied... I had wait_for_uploaded_build: true 🙄🙄🙄🙄🙄🙄🙄🙄🙄🙄🙄🙄
BRB, coding

@florianbuerger Can you try setting wait_for_uploaded_build: true and see if things work for you? Trying to figure out why https://github.com/fastlane/fastlane/blob/joshdholtz-pilot-fixes-removed-build-trains/fastlane_core/lib/fastlane_core/build_watcher.rb#L10-L20 is a thing that exists right now and if we still need it 🙃

If I remember correctly the flag had a different name at some point? Not sure.
Let me try that on our internal build. Will report back in a few minutes.

@florianbuerger Thank you! I'm actually going to remove that logic completely since its not needed anymore with the new API and deprecate the wait_for_uploaded_build build option

@joshdholtz I just uploaded using
    upload_to_testflight(
      app_identifier: "REDACTED",
      username: "REDACTED",
      changelog: changelog,
    )

and it worked just fine whereas before it had been failing.  So you fixed it for me, nice work!  :-). And node that I am not specifying wait_for_uploaded_build and I believe that defaults to false.

@joshdholtz yes im using wait_for_uploaded_build bcs it will not apply changelog, if something was changed let me know
   increment_build_number(
        xcodeproj: "",
        build_number: latest_testflight_build_number + 1
    )
    build_app(workspace: "", scheme: "", clean: "true", xcargs: "-UseNewBuildSystem=NO", export_method: "app-store", export_options: {provisioningProfiles: {"" => "", "" => ""}})
    upload_to_testflight(username: "", team_id: "", skip_waiting_for_build_processing: "false", beta_app_description: "changeme", changelog: "changeme", wait_for_uploaded_build: "true"

@joshdholtz Processing seems to be super slow today but adding the wait_for_uploaded_build: true options seems to have helped 💖
[18:01:42]: Successfully uploaded the new binary to App Store Connect
--
  | [18:01:42]: If you want to skip waiting for the processing to be finished, use the `skip_waiting_for_build_processing` option
  | [18:01:43]: Waiting for App Store Connect to finish processing the new build (0.9 - 93)
  // … more waiting …
  | [18:25:59]: Waiting for App Store Connect to finish processing the new build (0.9 - 93)

Build 0.9 - 93 is the correct version number. Fastfile looks like this now:
upload_to_testflight(
	changelog: testflight_notes,
	app_identifier: beta_app_identifier,
	wait_for_uploaded_build: true
)

I will report back if it lane fails for some reason but it seems you are on to something here 😉

Wait, @cubedivone and @joshdholtz - in order for changelogs to be uploaded to ITC by fast lane and used by TestFlight, do we need:
skip_waiting_for_build_processing: false
wait_for_uploaded_build: true

As in both those fields must be set?
The documentation seems to indicate that notes / changelog will be used and uploaded provided that skip_waiting_for_build_processing is false but doesn't mention anything about also needing to set wait_for_upload_build to be true.  See https://docs.fastlane.tools/actions/upload_to_testflight/#upload_to_testflight
Maybe that's why my test notes haven't been showing up reliably in TestFlight recently?

@cubedivone @florianbuerger @tberman @joelgetaction
Okay! Just removed the wait_for_uploaded_build option as its not longer needed and was confusing. Thing should work for everybody now ❤ Put this in your Gemfile to switch to my branch and run with bundle install or bundle update. Latest commit is https://github.com/fastlane/fastlane/pull/14523/commits/e83b17724412b671b867db25979069ea0c5e5d78
gem "fastlane", :git => "https://github.com/fastlane/fastlane.git", :branch => "joshdholtz-pilot-fixes-removed-build-trains"

@joshdholtz, your changes work when the wait_for_uploaded_build parameter is set to true. Echoing the thanks of others upstream for your work on this. Congrats on the upcoming nuptials!

@cubedivone @florianbuerger @tberman @joelgetaction
Okay! Just removed the wait_for_uploaded_build option as its not longer needed and was confusing. Thing should work for everybody now ❤ Put this in your Gemfile to switch to my branch and run with bundle install or bundle update. Latest commit is e83b177
gem "fastlane", :git => "https://github.com/fastlane/fastlane.git", :branch => "joshdholtz-pilot-fixes-removed-build-trains"

This worked for me. Thank you! ❤

Same for /v2/providers/xxx/apps/xxx/testers

@tberman try using the method which I created. I am not only using the sort uploadeddate as it is kinda not enough to identify the latest build number.
Let me know if you still face any issue.

Sorry for adding another thing here but now there is a typo in the deprecation warning for the wait_for_uploaded_build  flag:
Using deprecated option: '--wait_for_uploaded_build' (No longer needed with the user of App Store Connect API)

Should be “(…)with the user of the App Store Connect API”.

I updated to commit e83b17724412b671b867db25979069ea0c5e5d78, now I get this error when distribution a build (using the same setup as earlier)
The provided entity includes a relationship with an invalid value - Group with id '5bc8e433-8bd1-440d-bf38-24948e425e9c' does not exists

I assume that has something to do with the external tester groups. I checked the URLs for all groups in App Store Connect (I don't know if that are the same ids?), for example https://appstoreconnect.apple.com/WebObjects/iTunesConnect.woa/ra/ng/app/<app_id>/testflight?section=group&subsection=testers&id=dfe276fd-87b2-455d-8814-d418f6304e84 and the ID mentioned in the error message does not exist.

@florianbuerger Currently away from my computer but I’ll look when I get back home for you!
Sent with GitHawk

as mentioned by @snit-tile, still getting 401 gone with create_app_level_tester  after update:
                    Spaceship::TestFlight::Tester.create_app_level_tester(
                        app_id: app.id,
                        first_name: "blah",
                        last_name: "blah",
                        email<EMAIL_ADDRESS>                    )

@snit-tile Ah thanks! I will fix that action tonight as well ☺
Sent with GitHawk

@snit-tile Ah thanks! I will fix that action tonight as well ☺
Sent with GitHawk

FYI, that was just an example. Other actions that were failing for us are:
Spaceship::TestFlight::Group.all, Spaceship::TestFlight::Tester.remove_from_testflight! and Spaceship::TestFlight::Tester.remove_from_app!

@sonjz I've temporarily replaced Spaceship::TestFlight::Tester.create_app_level_tester by the add_tester_to_group! function I posted here. That works as a workaround. It creates the tester and adds it to the group_id.

@florianbuerger Do you have your stacktrace from your error? 🤔
@snit-tile I might have to rework your issues into a whole new PR 😬 A lot of Spaceship::TestFlight is going to get completely deprecated by the new API so we will be transitioning into new models here. But I will try to get that done as soon as possible!

Hey issue #14521 fam! Just wanted to let you all know I'm almost finished up fixing all the tests that I broke during this fix 😇 Tomorrow morning I"ll be doing a pair review on my PR and then looking to ship this out 🤞
This is by no means 100% completely done. There is A TON of improvement I'd like to do with pilot still which involves completely removing the use of the Spaceship::TestFlightmodule in favor of Spaceship::ConnectAPI 🔥 Once this next phase is complete it should end up with a more stable version of pilot since we are hoping to get rid of all the legacy APIs that will be pulled from under our feet with no notice.
So thanks again for the patience and helping me test 🙏 This community rocks 🤘🚀

@joshdholtz No stack trace, sorry. And it didn't happen again for later releases so 🤷♂ I'll open a new issue if it comes back.

@joshdholtz Increment build not working i should set it manual and i still get vrong version in build
INFO [2019-04-09 02:51:25.09]: iTunes Transporter successfully finished its job
DEBUG [2019-04-09 02:51:25.09]: [Transporter]: DBG-X: Returning 0
INFO [2019-04-09 02:51:25.22]: ------------------------------------------------------------------------------------------------------------------
INFO [2019-04-09 02:51:25.22]: --- Successfully uploaded package to App Store Connect. It might take a few minutes until it's visible online. ---
INFO [2019-04-09 02:51:25.22]: ------------------------------------------------------------------------------------------------------------------
INFO [2019-04-09 02:51:25.23]: Successfully uploaded the new binary to App Store Connect
INFO [2019-04-09 02:51:25.23]: If you want to skip waiting for the processing to be finished, use the `skip_waiting_for_build_processing` option
DEBUG [2019-04-09 02:51:25.23]: App Platform (ios)
INFO [2019-04-09 02:51:51.75]: Successfully finished processing the build 1.1.3 - 67
WARN [2019-04-09 02:51:51.75]: Uploaded app 1.2.1 - 67, but received build 1.1.3 - 67.
INFO [2019-04-09 02:51:54.09]: Successfully set the beta_app_feedback_email and/or beta_app_description
WARN [2019-04-09 02:51:54.76]: Lane Context:
INFO [2019-04-09 02:51:54.76]: {:DEFAULT_PLATFORM=>:ios, :PLATFORM_NAME=>:ios, :LANE_NAME=>"ios release", :BUILD_NUMBER=>"67", :IPA_OUTPUT_PATH=>"/Users/Xcloud/", :DSYM_OUTPUT_PATH=>"/Users/Xcloud/", :XCODEBUILD_ARCHIVE=>"/Users/Xcloud/Library/Developer/Xcode/Archives/2019-04-09/"}
ERROR [2019-04-09 02:51:54.76]: Could not set changelog: undefined method `[]' for nil:NilClass

I am getting something similar too:
version = get_version_number(xcodeproj: "MyXcodeProj.xcodeproj", target: target)
build_number = latest_testflight_build_number(version: version, app_identifier: "my.app.identifier")

the build_number keep returning me 1 even if the latest version is 4. For now i fix this by getting the build number directly from the project and not from testflight.

For all those who are facing the latest build number issue - can make use of this method.
Still the latest_testflight_build_number issue exists.
Just as a workaround (Took me a lot of time though), i have created a method which can solve the problem (Temporarily) - later this can be merged to the core spaceship.
Add this method to your fastfile. Call this method by passing three parameters.
version:
appleId:
appIdentifier:
You will get the appropriate build number. Uses the AppStoreconnect API
private_lane :latestTestflightBuildNumber do |options|
    require "spaceship"
    UI.message("Login to App Store Connect (#{options[:appleId]})")
    Spaceship::Tunes.login(user = options[:appleId])
    Spaceship::Tunes.select_team
    UI.message("Login successful")
    spaceshipClient = Spaceship::ConnectAPI::Base.client
    params = spaceshipClient.build_params(filter: { bundleId: options[:appIdentifier]})
    appsResponse = spaceshipClient.request(:get, "apps") do |req|
      req.options.params_encoder = Faraday::NestedParamsEncoder
      req.params = params
    end
    UI.user_error!("The bundle identifier - #{options[:appIdentifier]} does not exist in the AppStoreConnect!!!") if appsResponse.body["data"].count==0
    UI.user_error!("Looks like there is some problem with the input provided. Please check the app identifier!!!") if appsResponse.body["data"].count>1
    appIdFromAppsResponse=appsResponse.body["data"][0]["id"]
    preReleaseVersionsResponse = spaceshipClient.request(:get, "apps/#{appIdFromAppsResponse}/preReleaseVersions")
    preReleaseFilteredResponse = preReleaseVersionsResponse.body["data"].select { |k| k["attributes"]["version"] == options[:version] }
    begin
      preReleaseVersionId = preReleaseFilteredResponse[0]["id"]
      nonExpiredBuildsResponse = spaceshipClient.get_builds(filter: { expired: false, processingState: "PROCESSING,VALID", preReleaseVersion: "#{preReleaseVersionId}" },limit: 200, includes: "preReleaseVersion")
      latestTestflightBuildNumber = (nonExpiredBuildsResponse.max_by{|k| k["attributes"]["version"].to_i }["attributes"]["version"]).to_i
    rescue
      latestTestflightBuildNumber = "0".to_i
    end
  end

Let me know if anyone faces any issue with this.

Error 410 Gone

HTTP ERROR 410
Problem accessing /v2/providers/120038901/apps/1459238986/platforms/ios/trains. Reason:
    Gone

@nihp Does your user have admin or app manager access? That API call has been there a while so that error shouldn't be related to this one though so if you could create a new issue after you make sure you have proper access that would be 💯?
@cubedivone Hmmm 🤔 I'll see what I can do to try and replicate this.  Or are you still running off of the latest official release?

@cubedivone I THINK I FOUND YOUR ERROR! Fixing 💪

Is it possible that this issue affects delivery? I am getting:
WARN [2019-04-09 03:55:24.13]: [iTMSTransporter] 1 package(s) were not uploaded because they had problems:
WARN [2019-04-09 03:55:24.13]: [iTMSTransporter] 	/tmp/1459087723.itmsp - Error Messages:
WARN [2019-04-09 03:55:24.13]: [iTMSTransporter] 		Unable to find an iTunes Connect user for username<EMAIL_ADDRESS>and provider DEV_TEAM_ID. This username may not be enabled for iTunes Connect. Contact your team admin for assistance. (1296)

I have checked this user has admin permissions and error is misleading.

@arnmtk Probably not this one 😬 Can you create a brand new issue with what you are seeing?

@joshdholtz hi, i was using the latest official release. For now i fixed it by using the private_lane posted by @ramnac

Upload_to_testflight work for me. With the modified Gemfile. Did not test latest_testflight_build_number.
Thanks for good work!

For people struggling with latest_testflight_build_number. I used this trouble to switch build number detection from testflight to use git tags. This also enabled me to have consistent build numbers for our alpha, beta and release builds. We tag our builds using 'builds/alpha/1234' or 'builds/beta/4711' or 'builds/beta/0815'.
In my Fastfile I added
sh('git fetch --tags')     ENV['BUILD_NUMBER'] = (sh('git tag | grep builds\/ | sort -t / -k 3 -g | tail -n 1 | cut -d"/" -f3').to_i + 1).to_s
and replaced calls to latest_testflight_build_number with ENV['BUILD_NUMBER']
I also moved my addTagAndPush lane before calling pilot.

Let me know if increment build still not working, or it was changed ?
ERROR [2019-04-09 07:55:12.13]: Error in your Fastfile at line 45
ERROR [2019-04-09 07:55:12.13]:     43:     increment_build_number({
ERROR [2019-04-09 07:55:12.13]:     44:         xcodeproj: "/Users/Xcloud",
ERROR [2019-04-09 07:55:12.13]:  => 45:         build_number: latest_testflight_build_number + 1
ERROR [2019-04-09 07:55:12.13]:     46:     })
ERROR [2019-04-09 07:55:12.13]:     47:     build_app(workspace: "/Users/Xcloud/", scheme: "", clean: "true", xcargs: "-UseNewBuildSystem=NO", export_method: "app-store", export_options: {provisioningProfiles: {"" => "", "" => ""}})

@cubedivone I just pushed another round changes up if you want to run bundle update fastlane one more time 😇 There should also be some more helpful console messages from latest_testflight_build_number that should inform us why its not returning the correct number 🧠

@joshdholtz
I dont know where it takes this version 12.3.1, maybe in the pas it was test build with random version which i rejected long time ago
INFO [2019-04-09 08:25:30.89]: Login successful
INFO [2019-04-09 08:25:31.73]: Fetching the latest build number for version 12.3.1
INFO [2019-04-09 08:25:32.40]: Latest upload for version 12.3.1 is build: 12.3.1
INFO [2019-04-09 08:25:32.40]: ------------------------------------
INFO [2019-04-09 08:25:32.40]: --- Step: increment_build_number ---
INFO [2019-04-09 08:25:32.40]: ------------------------------------
Current version of project is:
    12.3.1

/Users/Xcloud

@cubedivone Hmmm... I would maybe try passing in the version option into latest_testflight_build_number or using live: true? 🧐

When i set manual build number all goes smooth now, but this increment with latest_testflight_build_number not working :(

I don't know if this is at all related, but after I uploaded a build last night using the new branch, I got a strange error that seems like it was looking at an old version number.  latest_testflight_build_number does seem to work for me however, so this may be totally unrelated.
[20:16:36]: ------------------------------------------------------------------------------------------------------------------
[20:16:36]: --- Successfully uploaded package to App Store Connect. It might take a few minutes until it's visible online. ---
[20:16:36]: ------------------------------------------------------------------------------------------------------------------
[20:16:36]: Successfully uploaded the new binary to App Store Connect
[20:16:36]: If you want to skip waiting for the processing to be finished, use the `skip_waiting_for_build_processing` option
[20:18:01]: Successfully finished processing the build 1.2 - 34
[20:18:01]: Uploaded app 1.57.0 - 34, but received build 1.2 - 34.
+------------------------------------+------------------------------------------------------------------+
|                                             Lane Context                                              |
+------------------------------------+------------------------------------------------------------------+
| DEFAULT_PLATFORM                   | ios                                                              |
| PLATFORM_NAME                      | ios                                                              |
| LANE_NAME                          | ios beta                                                         |
| GIT_REPO_WAS_CLEAN_ON_START        | true                                                             |
| SIGH_PROFILE_TYPE                  | app-store                                                        |
| MATCH_PROVISIONING_PROFILE_MAPPING | {"com.voltathletics.native"=>"match AppStore                     |
|                                    | com.voltathletics.native"}                                       |
| VERSION_NUMBER                     | 1.57.0                                                           |
| LATEST_BUILD_NUMBER                | 17                                                               |
| LATEST_TESTFLIGHT_BUILD_NUMBER     | 17                                                               |
| BUILD_NUMBER                       | 34                                                               |
| IPA_OUTPUT_PATH                    | /Users/new/Desktop/webdev/Volt/client_react_native/Volt.ipa      |
| DSYM_OUTPUT_PATH                   | /Users/new/Desktop/webdev/Volt/client_react_native/Volt.app.dSY  |
|                                    | M.zip                                                            |
| XCODEBUILD_ARCHIVE                 | /Users/new/Library/Developer/Xcode/Archives/2019-04-08/Volt      |
|                                    | 2019-04-08 20.09.05.xcarchive                                    |
+------------------------------------+------------------------------------------------------------------+
[20:18:02]: Could not set changelog: undefined method `[]' for nil:NilClass

+------+---------------------------------------+-------------+
|                      fastlane summary                      |
+------+---------------------------------------+-------------+
| Step | Action                                | Time (in s) |
+------+---------------------------------------+-------------+
| 1    | Verifying fastlane version            | 0           |
| 2    | default_platform                      | 0           |
| 3    | ensure_git_status_clean               | 0           |
| 4    | cd ../ && yarn install --force && cd  | 26          |
|      | /Users/new/Desktop/webde              |             |
| 5    | cd ../ios && bundle exec pod install  | 18          |
| 6    | match                                 | 2           |
| 7    | get_version_number                    | 0           |
| 8    | latest_testflight_build_number        | 2           |
| 9    | increment_build_number                | 1           |
| 10   | commit_version_bump                   | 1           |
| 11   | gym                                   | 368         |
| 12   | ensure_git_status_clean               | 0           |
| 13   | get_build_number                      | 2           |
| 14   | get_version_number                    | 0           |
| 💥   | pilot                                 | 171         |
+------+---------------------------------------+-------------+

[20:18:02]: fastlane finished with errors

[!] Could not set changelog: undefined method `[]' for nil:NilClass

@fossage Can you run bundle update fastlane if you are still pointed at my branch? I should have fixed that error this morning and the latest code on my branch should be 💯 for you 😊

Set version with latest_testflight_build_number
INFO [2019-04-09 08:42:33.92]: Login successful
INFO [2019-04-09 08:42:34.83]: Fetching the latest build number for version 1.2.1
INFO [2019-04-09 08:42:35.67]: Latest upload for version 1.2.1 is build: 68
INFO [2019-04-09 08:42:35.68]: ------------------------------------
INFO [2019-04-09 08:42:35.68]: --- Step: increment_build_number ---
INFO [2019-04-09 08:42:35.68]: ------------------------------------
Current version of project is:
    12.3.1

First of all, great work so far @joshdholtz. You're really putting a lot of effort in this issue 💪
For us, it's nearly working. However, it seems that the TestFlight group selection is still broken:
/Users/travis/build/WeTransfer/Coyote/bundle/ruby/2.4.0/bundler/gems/fastlane-109e4ab424c2/spaceship/lib/spaceship/connect_api/client.rb:353:in `handle_response': [!] The provided entity includes a relationship with an invalid value - Group with id 'c773f6da-d72c-487d-8821-6b02eb86c636' does not exists (Spaceship::UnexpectedResponse)
	from /Users/travis/build/WeTransfer/Coyote/bundle/ruby/2.4.0/bundler/gems/fastlane-109e4ab424c2/spaceship/lib/spaceship/connect_api/client.rb:335:in `add_beta_groups_to_build'
	from /Users/travis/build/WeTransfer/Coyote/bundle/ruby/2.4.0/bundler/gems/fastlane-109e4ab424c2/pilot/lib/pilot/build_manager.rb:268:in `distribute_build'
	from /Users/travis/build/WeTransfer/Coyote/bundle/ruby/2.4.0/bundler/gems/fastlane-109e4ab424c2/pilot/lib/pilot/build_manager.rb:99:in `distribute'
	from /Users/travis/build/WeTransfer/Coyote/bundle/ruby/2.4.0/bundler/gems/fastlane-109e4ab424c2/pilot/lib/pilot/build_manager.rb:54:in `upload'
	from /Users/travis/build/WeTransfer/Coyote/bundle/ruby/2.4.0/bundler/gems/fastlane-109e4ab424c2/fastlane/lib/fastlane/actions/upload_to_testflight.rb:16:in `run'
	from /Users/travis/build/WeTransfer/Coyote/bundle/ruby/2.4.0/bundler/gems/fastlane-109e4ab424c2/fastlane/lib/fastlane/runner.rb:253:in `block (2 levels) in execute_action'
	from /Users/travis/build/WeTransfer/Coyote/bundle/ruby/2.4.0/bundler/gems/fastlane-109e4ab424c2/fastlane/lib/fastlane/actions/actions_helper.rb:50:in `execute_action'
	from /Users/travis/build/WeTransfer/Coyote/bundle/ruby/2.4.0/bundler/gems/fastlane-109e4ab424c2/fastlane/lib/fastlane/runner.rb:232:in `block in execute_action'
	from /Users/travis/build/WeTransfer/Coyote/bundle/ruby/2.4.0/bundler/gems/fastlane-109e4ab424c2/fastlane/lib/fastlane/runner.rb:227:in `chdir'
	from /Users/travis/build/WeTransfer/Coyote/bundle/ruby/2.4.0/bundler/gems/fastlane-109e4ab424c2/fastlane/lib/fastlane/runner.rb:227:in `execute_action'
	from /Users/travis/build/WeTransfer/Coyote/bundle/ruby/2.4.0/bundler/gems/fastlane-109e4ab424c2/fastlane/lib/fastlane/runner.rb:157:in `trigger_action_by_name'
	from /Users/travis/build/WeTransfer/Coyote/bundle/ruby/2.4.0/bundler/gems/fastlane-109e4ab424c2/fastlane/lib/fastlane/fast_file.rb:154:in `method_missing'
	from Fastfile:141:in `block in parsing_binding'
	from /Users/travis/build/WeTransfer/Coyote/bundle/ruby/2.4.0/bundler/gems/fastlane-109e4ab424c2/fastlane/lib/fastlane/lane.rb:33:in `call'
	from /Users/travis/build/WeTransfer/Coyote/bundle/ruby/2.4.0/bundler/gems/fastlane-109e4ab424c2/fastlane/lib/fastlane/runner.rb:49:in `block in execute'
	from /Users/travis/build/WeTransfer/Coyote/bundle/ruby/2.4.0/bundler/gems/fastlane-109e4ab424c2/fastlane/lib/fastlane/runner.rb:45:in `chdir'
	from /Users/travis/build/WeTransfer/Coyote/bundle/ruby/2.4.0/bundler/gems/fastlane-109e4ab424c2/fastlane/lib/fastlane/runner.rb:45:in `execute'
	from /Users/travis/build/WeTransfer/Coyote/bundle/ruby/2.4.0/bundler/gems/fastlane-109e4ab424c2/fastlane/lib/fastlane/lane_manager.rb:56:in `cruise_lane'
	from /Users/travis/build/WeTransfer/Coyote/bundle/ruby/2.4.0/bundler/gems/fastlane-109e4ab424c2/fastlane/lib/fastlane/command_line_handler.rb:36:in `handle'
	from /Users/travis/build/WeTransfer/Coyote/bundle/ruby/2.4.0/bundler/gems/fastlane-109e4ab424c2/fastlane/lib/fastlane/commands_generator.rb:108:in `block (2 levels) in run'
	from /Users/travis/build/WeTransfer/Coyote/bundle/ruby/2.4.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in `call'
	from /Users/travis/build/WeTransfer/Coyote/bundle/ruby/2.4.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in `run'
	from /Users/travis/build/WeTransfer/Coyote/bundle/ruby/2.4.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in `run_active_command'
	from /Users/travis/build/WeTransfer/Coyote/bundle/ruby/2.4.0/bundler/gems/fastlane-109e4ab424c2/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in `run!'
	from /Users/travis/build/WeTransfer/Coyote/bundle/ruby/2.4.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in `run!'
	from /Users/travis/build/WeTransfer/Coyote/bundle/ruby/2.4.0/bundler/gems/fastlane-109e4ab424c2/fastlane/lib/fastlane/commands_generator.rb:333:in `run'
	from /Users/travis/build/WeTransfer/Coyote/bundle/ruby/2.4.0/bundler/gems/fastlane-109e4ab424c2/fastlane/lib/fastlane/commands_generator.rb:41:in `start'
	from /Users/travis/build/WeTransfer/Coyote/bundle/ruby/2.4.0/bundler/gems/fastlane-109e4ab424c2/fastlane/lib/fastlane/cli_tools_distributor.rb:119:in `take_off'
	from /Users/travis/build/WeTransfer/Coyote/bundle/ruby/2.4.0/bundler/gems/fastlane-109e4ab424c2/bin/fastlane:23:in `<top (required)>'
	from /Users/travis/build/WeTransfer/Coyote/bundle/ruby/2.4.0/bin/fastlane:23:in `load'
	from /Users/travis/build/WeTransfer/Coyote/bundle/ruby/2.4.0/bin/fastlane:23:in `'
	from /Users/travis/build/WeTransfer/Coyote/bundle/ruby/2.4.0/bin/ruby_executable_hooks:24:in `eval'
	from /Users/travis/build/WeTransfer/Coyote/bundle/ruby/2.4.0/bin/ruby_executable_hooks:24:in `'

We're running the TestFlight command as following:
testflight(
    skip_waiting_for_build_processing: false,
    skip_submission: false,
    groups: ['QA Source', 'iOS Team', 'WeTransfer Testers'],
    changelog: last_release_changelog,
    team_id: "XXXXXX")

Let me know if this helps and if you have any further questions!

@AvdLee This might be a weird question but can you go to https://appstoreconnect.apple.com/iris/v1/betaGroups?filter[app]=<your_app_id> in your browser (logged in to the correct team) and see if you see the c773f6da-d72c-487d-8821-6b02eb86c636 in there?
And if so, can you send its attributes to me like the following?

@AvdLee WAAIIITTT... I think I know!! Fix incoming

@joshdholtz 12.3.1 version in all builds list from app connect, i have found it, somehow latest_testflight_build_number always takes version from the top of the all version list, i dont know how delete it bcs it is rejected version, set version in latest_testflight_build_number does not help :(

@cubedivone Something is very odd with your list of builds 😔 Maybe we do a screenshare sometime??? I don't know how else to debug 🤔
@AvdLee @florianbuerger The latest commit on my branch should have a fix for that group relationship issue you were both experiencing! bundle update fastlane should do it for you 💪

got the same issue:
HTTP ERROR 410
Problem accessing /v2/providers/118727232/apps/1256291798/platforms/ios/trains. Reason:
    Gone

Going to be releasing a version with this tonight 😬😬😬😬😬😬😬😬😬😬😬😬😬😬😬😬

Alright, this is released in 2.120.0 🚀 Hopefully we don't have any more huge issues in there. I will now be working on moving everything from old API in Spaceship::TestFlight over to new API in Spaceship::ConnectAPI. This will be then include some pretty big rewrite of pilot and other tools/actions that use the old API but I want to prevent downtime like this from happening again 🙃

I'm a little late to the broken endpoint reporting party 😅 but Spaceship::TestFlight::Tester.create_app_level_tester (adding testers to TestFlight, needed for fastlane/boarding) doesn't seem to be working anymore. @joshdholtz if I can figure out the App Store Connect API do you want me to send a PR to move this to https://developer.apple.com/documentation/appstoreconnectapi/create_a_beta_tester?

@Josh Holtz<EMAIL_ADDRESS>Now I am using the developer account. It not
have the App Manager or Admin role. Is it mandatory to have the AppManager
or Admin role for uploading the app in testflight?
On Wed, Apr 10, 2019 at 8:50 AM Rajiv Shah<EMAIL_ADDRESS>wrote:

I'm a little late to the broken endpoint reporting party 😅 but
Spaceship::TestFlight::Tester.create_app_level_tester (adding testers to
TestFlight, needed for fastlane/boarding) doesn't seem to be working
anymore. @joshdholtz https://github.com/joshdholtz if I can figure out
the App Store Connect API do you want me to send a PR to move this to
https://developer.apple.com/documentation/appstoreconnectapi/create_a_beta_tester
?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fastlane/fastlane/issues/14521#issuecomment-481517771,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AjR1UuwR_LyR_uiOqmNE04XiyTOntiyfks5vfVh0gaJpZM4cberx
.

@nihp Developer can only upload builds. If you want to distribute it or update build info you need AppManager. For details see Program Roles

Here the uploaded builds are seen in Activity tab and why it not shown in
testflight tab. Why it showing empty screen in testflight?
Note: Before 1 week there is more builds in my testflight tab. But now all
the builds are disappeared.
On Wed, Apr 10, 2019 at 11:55 AM Florian Bürger<EMAIL_ADDRESS>wrote:

@nihp https://github.com/nihp Developer can only upload builds. If you
want to distribute it or update build info you need AppManager. For
details see Program Roles https://developer.apple.com/support/roles/
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fastlane/fastlane/issues/14521#issuecomment-481550876,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AjR1Uk3PZ8op1J7OdnfrT9xEbxP24LAZks5vfYPogaJpZM4cberx
.

@nihp Developer can only upload builds. If you want to distribute it or update build info you need AppManager. For details see Program Roles

This is a bit unrelated (refering to #5386), but I will mention this anyway:
Note that if you have AppManager privileges in AppStoreConnect it might cause the your session has expired, please log in issue in Fastlane pipeline depending on size of your project.

Am still seeing intermittent failures after seeing success on Monday, more often than not will get a failure but sometimes calls succeed. This is with 2.120.0. As mentioned earlier am using 🚀 in a small script to automate transfer dSYM files from iTunes to Crashlytics (this is itself driven by a Python script):
#!/usr/bin/env ruby
#
# Script to query iTunes for builds that may need dSYM sets transferring to
# Fastlane Crashlytics. Script is driven by environment vars which need to
# be setup as follows:
#
# FASTLANE_ITC_USERNAME    The iTunes account username
# FASTLANE_ITC_PASSWORD    The iTunes account password
# FASTLANE_ITC_TEAM_ID     The team ID (needed when account associated with multiple teams)
# ITC_LAST_BUILD           Last build number already handled, filters earlier builds from output
#
# Output is one build per line with format:
#
# <bundle-id>,<build-number>,<dsym download url>
#

require "spaceship"

username = ENV["FASTLANE_ITC_USERNAME"]
password = ENV["FASTLANE_ITC_PASSWORD"]
last_build = ENV["ITC_LAST_BUILD"].to_i

Spaceship::Tunes::login(username, password)
Spaceship::Tunes.select_team

Spaceship::Tunes::Application.all.collect do |app|
    if app.live_version != nil
        train=app.live_version.version
        app.all_builds_for_train(train: train).sort { |a,b| a.build_version <=> b.build_version }.collect do |build|
            build.reload
            if !build.processing?
                puts app.bundle_id + ',' + build.build_version + ',' + build.dsym_url
            end
        end
    end
    if app.edit_version != nil
        app.edit_version.candidate_builds.sort { |a,b| a.build_version <=> b.build_version }.collect do |build|
            if !build.processing && build.details.dsym_url != nil && build.build_version.to_i > last_build
                puts app.bundle_id + ',' + build.build_version + ',' + build.details.dsym_url
            end
        end
    end
end

Sometimes will fail immediately with no builds output, sometimes it will get through a number of them before failing (replaced the full output lines with app,build,link for simplicity):
$ ./itunes-to-crashlytics.rb
app,build,link
app,build,link
app,build,link
/Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/spaceship/lib/spaceship/test_flight/client.rb:321:in `handle_response':  (Spaceship::UnexpectedResponse)

<meta http-equiv="Content-Type" content="text/html;charset=utf-8"/>
<title>Error 410 Gone</title>

HTTP ERROR 410

Problem accessing /v2/providers/272511/apps/687242690/platforms/ios/trains/6.3.18/builds. Reason:

    Gone

	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/spaceship/lib/spaceship/test_flight/client.rb:38:in `block in get_builds_for_train'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/spaceship/lib/spaceship/client.rb:620:in `with_retry'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/spaceship/lib/spaceship/test_flight/client.rb:36:in `get_builds_for_train'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/spaceship/lib/spaceship/test_flight/build.rb:115:in `builds_for_train'
	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/spaceship/lib/spaceship/tunes/application.rb:315:in `all_builds_for_train'
	from ./itunes-to-crashlytics.rb:29:in `block in '
	from ./itunes-to-crashlytics.rb:26:in `collect'
	from ./itunes-to-crashlytics.rb:26:in `'

Any ideas? Thanks!

@DominikBucher12 Okay

I'm still having hard times with latest_testflight_build_number
When I've bumped version number in Xcode the lane fails to find this version (which is obvious), but it's not setting initial number to 1 :
This is my lane part of code:
latest_testflight_build_number(version: version, live: "false", initial_build_number: "1")
And those are logs:
`INFO [2019-04-10 10:53:03.97]: --- Step: latest_testflight_build_number ---
INFO [2019-04-10 10:53:03.97]: --------------------------------------------
INFO [2019-04-10 10:53:03.97]: Login to App Store Connect<EMAIL_ADDRESS>Reading keychain entry, because either user or password were empty
Loading session from<EMAIL_ADDRESS>Looking for App Store Connect Team with ID 000000
INFO [2019-04-10 10:53:06.10]: Login successful
WARN [2019-04-10 10:53:07.62]: Lane Context:
INFO [2019-04-10 10:53:07.62]: {:DEFAULT_PLATFORM=>:ios, :PLATFORM_NAME=>:ios, :LANE_NAME=>"ios build_beta", :CERT_FILE_PATH=>"/Users/user/Sources/project/xxxxxxxxxx.cer", :CERT_CERTIFICATE_ID=>"xxxxxxxxxx", :SIGH_PROFILE_PATH=>"/Users/user/Sources/project/AppStore_xx.xxx.xxxxxxxxxxx.mobileprovision", :SIGH_PROFILE_PATHS=>["/Users/user/Sources/project/AppStore_xx.xxx.xxxxxxxxxxx.mobileprovision"], :SIGH_UDID=>"xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", :SIGH_UUID=>"xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx", :SIGH_NAME=>"APPLICATION Distribution", :SIGH_PROFILE_TYPE=>"app-store", :VERSION_NUMBER=>"1.6"}
ERROR [2019-04-10 10:53:07.62]: Could not find a build number for version 1.6
INFO [2019-04-10 10:53:07.62]: Successfully generated documentation at path '/Users/user/Sources/project/fastlane/README.md'
+------+-----------------------------------+-------------+
|                    fastlane summary                    |
+------+-----------------------------------+-------------+
| Step | Action                            | Time (in s) |
+------+-----------------------------------+-------------+
| 1    | update_fastlane                   | 30          |
| 2    | default_platform                  | 0           |
| 3    | get_certificates                  | 6           |
| 4    | get_provisioning_profile          | 8           |
| 5    | Switch to ios version_number lane | 0           |
| 6    | get_version_number                | 0           |
| 💥   | latest_testflight_build_number    | 3           |
+------+-----------------------------------+-------------+
DEBUG [2019-04-10 10:53:07.62]: All plugins are up to date
ERROR [2019-04-10 10:53:07.62]: fastlane finished with errors
DEBUG [2019-04-10 10:53:07.62]: All plugins are up to date
Traceback (most recent call last):
37: from /Users/user/.rvm/gems/ruby-2.6.1/bin/ruby_executable_hooks:24:in ' 	36: from /Users/user/.rvm/gems/ruby-2.6.1/bin/ruby_executable_hooks:24:in eval'
35: from /Users/user/.rvm/gems/ruby-2.6.1/bin/fastlane:23:in ' 	34: from /Users/user/.rvm/gems/ruby-2.6.1/bin/fastlane:23:in load'
33: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/bin/fastlane:23:in <top (required)>' 	32: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/cli_tools_distributor.rb:119:in take_off'
31: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/commands_generator.rb:41:in start' 	30: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/commands_generator.rb:333:in run'
29: from /Users/user/.rvm/gems/ruby-2.6.1/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in run!' 	28: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in run!'
27: from /Users/user/.rvm/gems/ruby-2.6.1/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in run_active_command' 	26: from /Users/user/.rvm/gems/ruby-2.6.1/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in run'
25: from /Users/user/.rvm/gems/ruby-2.6.1/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in call' 	24: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/commands_generator.rb:108:in block (2 levels) in run'
23: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/command_line_handler.rb:36:in handle' 	22: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/lane_manager.rb:56:in cruise_lane'
21: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/runner.rb:45:in execute' 	20: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/runner.rb:45:in chdir'
19: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/runner.rb:49:in block in execute' 	18: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/lane.rb:33:in call'
17: from Fastfile:66:in block (2 levels) in parsing_binding' 	16: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/fast_file.rb:154:in method_missing'
15: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/runner.rb:146:in trigger_action_by_name' 	14: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/runner.rb:204:in try_switch_to_lane'
13: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/lane.rb:33:in call' 	12: from Fastfile:92:in block (2 levels) in parsing_binding'
11: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/fast_file.rb:154:in method_missing' 	10: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/runner.rb:157:in trigger_action_by_name'
9: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/runner.rb:227:in execute_action' 	 8: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/runner.rb:227:in chdir'
7: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/runner.rb:235:in block in execute_action' 	 6: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/actions/actions_helper.rb:50:in execute_action'
5: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/runner.rb:256:in block (2 levels) in execute_action' 	 4: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/actions/latest_testflight_build_number.rb:11:in run'
3: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/actions/app_store_build_number.rb:11:in run' 	 2: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/actions/app_store_build_number.rb:45:in get_build_number'
1: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane_core/lib/fastlane_core/ui/ui.rb:17:in method_missing' /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane_core/lib/fastlane_core/ui/interface.rb:141:in user_error!': Could not find a build number for version 1.6 (FastlaneCore::Interface::FastlaneError)
37: from /Users/user/.rvm/gems/ruby-2.6.1/bin/ruby_executable_hooks:24:in ' 	36: from /Users/user/.rvm/gems/ruby-2.6.1/bin/ruby_executable_hooks:24:in eval'
35: from /Users/user/.rvm/gems/ruby-2.6.1/bin/fastlane:23:in ' 	34: from /Users/user/.rvm/gems/ruby-2.6.1/bin/fastlane:23:in load'
33: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/bin/fastlane:23:in <top (required)>' 	32: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/cli_tools_distributor.rb:119:in take_off'
31: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/commands_generator.rb:41:in start' 	30: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/commands_generator.rb:333:in run'
29: from /Users/user/.rvm/gems/ruby-2.6.1/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in run!' 	28: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in run!'
27: from /Users/user/.rvm/gems/ruby-2.6.1/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in run_active_command' 	26: from /Users/user/.rvm/gems/ruby-2.6.1/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in run'
25: from /Users/user/.rvm/gems/ruby-2.6.1/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in call' 	24: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/commands_generator.rb:108:in block (2 levels) in run'
23: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/command_line_handler.rb:36:in handle' 	22: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/lane_manager.rb:56:in cruise_lane'
21: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/runner.rb:45:in execute' 	20: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/runner.rb:45:in chdir'
19: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/runner.rb:49:in block in execute' 	18: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/lane.rb:33:in call'
17: from Fastfile:66:in block (2 levels) in parsing_binding' 	16: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/fast_file.rb:154:in method_missing'
15: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/runner.rb:146:in trigger_action_by_name' 	14: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/runner.rb:204:in try_switch_to_lane'
13: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/lane.rb:33:in call' 	12: from Fastfile:92:in block (2 levels) in parsing_binding'
11: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/fast_file.rb:154:in method_missing' 	10: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/runner.rb:157:in trigger_action_by_name'
9: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/runner.rb:227:in execute_action' 	 8: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/runner.rb:227:in chdir'
7: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/runner.rb:235:in block in execute_action' 	 6: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/actions/actions_helper.rb:50:in execute_action'
5: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/runner.rb:256:in block (2 levels) in execute_action' 	 4: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/actions/latest_testflight_build_number.rb:11:in run'
3: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/actions/app_store_build_number.rb:11:in run' 	 2: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane/lib/fastlane/actions/app_store_build_number.rb:45:in get_build_number'
1: from /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane_core/lib/fastlane_core/ui/ui.rb:17:in method_missing' /Users/user/.rvm/gems/ruby-2.6.1/gems/fastlane-2.120.0/fastlane_core/lib/fastlane_core/ui/interface.rb:141:in user_error!': [!] Could not find a build number for version 1.6 (FastlaneCore::Interface::FastlaneError)`

I am also facing the same issue
Error 410 Gone
Problem accessing /v2/providers/119021831/apps/1362469768/platforms/ios/trains.

<meta http-equiv="Content-Type" content="text/html;charset=utf-8"/>
<title>Error 410 Gone</title>

HTTP ERROR 410

Problem accessing /v2/providers/119021831/apps/1362469768/platforms/ios/trains. Reason:

    Gone

.rvm/gems/ruby-2.5.1/gems/fastlane-2.116.1/spaceship/lib/spaceship/test_flight/client.rb:321:in `handle_response': [!]  (Spaceship::UnexpectedResponse)
.rvm/gems/ruby-2.5.1/gems/fastlane-2.116.1/spaceship/lib/spaceship/test_flight/client.rb:31:in `get_build_trains'

@AvdLee WAAIIITTT... I think I know!! Fix incoming

You were right, it's fixed! 🎉 Great work @joshdholtz. Time for you to get a beer and take a moment to relax! 😄

Hi, the fix works well for an existing version, with the new one seems not working (also using the initial_build_number parameter).
Does anyone else have the same problem?
1:57:01 /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/fastlane_core/lib/fastlane_core/ui/interface.rb:141:in user_error!': [!] Could not find a build number for version 1.1.7 (FastlaneCore::Interface::FastlaneError) 11:57:01 	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/fastlane_core/lib/fastlane_core/ui/ui.rb:17:in method_missing'
11:57:01 	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/fastlane/lib/fastlane/actions/app_store_build_number.rb:45:in get_build_number' 11:57:01 	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/fastlane/lib/fastlane/actions/app_store_build_number.rb:11:in run'
11:57:01 	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/fastlane/lib/fastlane/actions/latest_testflight_build_number.rb:11:in run' 11:57:01 	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/fastlane/lib/fastlane/runner.rb:256:in block (2 levels) in execute_action'
11:57:01 	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/fastlane/lib/fastlane/actions/actions_helper.rb:50:in execute_action' 11:57:01 	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/fastlane/lib/fastlane/runner.rb:235:in block in execute_action'
11:57:01 	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/fastlane/lib/fastlane/runner.rb:227:in chdir' 11:57:01 	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/fastlane/lib/fastlane/runner.rb:227:in execute_action'
11:57:01 	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/fastlane/lib/fastlane/runner.rb:157:in trigger_action_by_name' 11:57:01 	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/fastlane/lib/fastlane/fast_file.rb:154:in method_missing'
11:57:01 	from Fastfile:68:in block (2 levels) in parsing_binding' 11:57:01 	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/fastlane/lib/fastlane/lane.rb:33:in call'
11:57:01 	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/fastlane/lib/fastlane/runner.rb:49:in block in execute' 11:57:01 	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/fastlane/lib/fastlane/runner.rb:45:in chdir'
11:57:01 	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/fastlane/lib/fastlane/runner.rb:45:in execute' 11:57:01 	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/fastlane/lib/fastlane/lane_manager.rb:56:in cruise_lane'
11:57:01 	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/fastlane/lib/fastlane/command_line_handler.rb:36:in handle' 11:57:01 	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/fastlane/lib/fastlane/commands_generator.rb:108:in block (2 levels) in run'
11:57:01 	from /Library/Ruby/Gems/2.3.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in call' 11:57:01 	from /Library/Ruby/Gems/2.3.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in run'
11:57:01 	from /Library/Ruby/Gems/2.3.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in run_active_command' 11:57:01 	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in run!'
11:57:01 	from /Library/Ruby/Gems/2.3.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in run!' 11:57:01 	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/fastlane/lib/fastlane/commands_generator.rb:333:in run'
11:57:01 	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/fastlane/lib/fastlane/commands_generator.rb:41:in start' 11:57:01 	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/fastlane/lib/fastlane/cli_tools_distributor.rb:119:in take_off'
11:57:01 	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/bin/fastlane:23:in <top (required)>' 11:57:01 	from /usr/local/bin/fastlane:22:in load'
11:57:01 	from /usr/local/bin/fastlane:22:in `'
11:57:01 Build step 'Esegui shell' marked build as failure

Unfortunately the upload to testflight line is not working for me.
I'm getting strange error like [Transporter Error Output]: An exception has occurred: Broken pipe (Write failed)
which is strange, cause I can upload via Xcode to AppStore my builds.
Also I've testes more than one time and it all the time fails in the same place.
Logs bellow.
Thanks
INFO [2019-04-10 14:18:38.78]: --- Step: upload_to_testflight ---
INFO [2019-04-10 14:18:38.78]: ----------------------------------
INFO [2019-04-10 14:18:38.93]: Login to App Store Connect<EMAIL_ADDRESS>Reading keychain entry, because either user or password were empty
Loading session from<EMAIL_ADDRESS>Looking for App Store Connect Team with ID XXXXXX
INFO [2019-04-10 14:18:41.45]: Login successful
DEBUG [2019-04-10 14:18:41.46]: App identifier (xx.xxxxxxxxxx)
INFO [2019-04-10 14:18:42.08]: Ready to upload new build to TestFlight (App:<PHONE_NUMBER>)...
DEBUG [2019-04-10 14:18:42.08]: App Platform (ios)
INFO [2019-04-10 14:18:48.53]: Wrote XML data to '/var/folders/cd/gj5_1hl509l7js0hskrhxh_40000gn/T/d20190410-46780-1kz5zxn/1315653715.itmsp'
INFO [2019-04-10 14:18:48.63]: Going to upload updated app to App Store Connect
INFO [2019-04-10 14:18:48.63]: This might take a few minutes. Please don't interrupt the script.
DEBUG [2019-04-10 14:18:48.80]: /Applications/Xcode.app/Contents/Applications/Application\ Loader.app/Contents/itms/java/bin/java -Djava.ext.dirs=/Applications/Xcode.app/Contents/Applications/Application\ Loader.app/Contents/itms/java/lib/ext -XX:NewSize=2m -Xms32m -Xmx1024m -Xms1024m -Djava.awt.headless=true -Dsun.net.http.retryPost=false -jar /Applications/Xcode.app/Contents/Applications/Application\ Loader.app/Contents/itms/lib/itmstransporter-launcher.jar -m upload -u<EMAIL_ADDRESS>-p YourPassword -f /var/folders/cd/gj5_1hl509l7js0hskrhxh_40000gn/T/d20190410-46780-1kz5zxn/1315653715.itmsp -t DAV -t Signiant -k 100000 2>&1
DEBUG [2019-04-10 14:18:53.95]: [Transporter]: INFO: Transporter is searching for new software components.
DEBUG [2019-04-10 14:19:01.58]: [Transporter]: INFO: Update check complete.
DEBUG [2019-04-10 14:19:04.16]: [Transporter]: INFO: Logging configured successfully.
DEBUG [2019-04-10 14:19:04.47]: [Transporter]: DEBUG: Attempting refresh of configuration data from https://contentdelivery.itunes.apple.com/transporter/Defaults.properties
DEBUG [2019-04-10 14:19:04.65]: [Transporter]: DEBUG: Configuration refresh successful.
DEBUG [2019-04-10 14:19:04.65]: [Transporter]: DEBUG: Saving configuration to local path: /Users/user/Library/Caches/com.apple.amp.itmstransporter/Defaults.properties
DEBUG [2019-04-10 14:19:04.65]: [Transporter]: INFO: iTMSTransporter : iTunes Store Transporter [1.13.0]
DEBUG [2019-04-10 14:19:04.65]: [Transporter]: INFO: OS identifier: Mac OS X 10.14.4 (x86_64); jvm=25.71-b02; jre=1.8.0-u131-b11-iTMSTransporter-b02
DEBUG [2019-04-10 14:19:04.66]: [Transporter]: INFO: Memory: [JVM] 956M free, 981M total, 981M max [System] (Physical) 1944M free, 10240M total (Swap) 688M free, 2048M total
DEBUG [2019-04-10 14:19:04.66]: [Transporter]: DBG-X: Memory: [JVM] 956M free, 981M total, 981M max [System] (Physical) 1940M free, 10240M total (Swap) 688M free, 2048M total
DEBUG [2019-04-10 14:19:04.67]: [Transporter]: DBG-X: Using operation named: authenticateForSession
DEBUG [2019-04-10 14:19:04.67]: [Transporter]: DBG-X: Apple's web service operation input parameters:
DEBUG [2019-04-10 14:19:04.67]: [Transporter]: DBG-X:   parameter Application = iTMSTransporter
DEBUG [2019-04-10 14:19:04.67]: [Transporter]: DBG-X:   parameter BaseVersion = 1.11.0
DEBUG [2019-04-10 14:19:04.67]: [Transporter]: DBG-X:   parameter OSIdentifier = Mac OS X 10.14.4 (x86_64); jvm=25.71-b02; jre=1.8.0-u131-b11-iTMSTransporter-b02
DEBUG [2019-04-10 14:19:04.67]: [Transporter]: DBG-X:   parameter StatisticsClientStartDateTimeZoneISO = 2019-04-10T14:19:04+02:00
DEBUG [2019-04-10 14:19:04.67]: [Transporter]: DBG-X:   parameter StatisticsPreviousCallDurationInSecs = 0.411490002
DEBUG [2019-04-10 14:19:04.67]: [Transporter]: DBG-X:   parameter TransporterArguments = -m upload -u<EMAIL_ADDRESS>-p **hidden value** -f /var/folders/cd/gj5_1hl509l7js0hskrhxh_40000gn/T/d20190410-46780-1kz5zxn/1315653715.itmsp -t DAV -t Signiant -k 100000
DEBUG [2019-04-10 14:19:04.67]: [Transporter]: DBG-X:   parameter Version = 1.13.0
DEBUG [2019-04-10 14:19:04.67]: [Transporter]: DBG-X:   parameter iTMSTransporterMode = upload
DEBUG [2019-04-10 14:19:04.68]: [Transporter]: INFO: id =<PHONE_NUMBER>1904-112
DEBUG [2019-04-10 14:19:04.68]: [Transporter]: INFO: iTMSTransporter Correlation Key: 7dd37ffd-df02-460b-8e49-fbdbdbb75195
DEBUG [2019-04-10 14:19:06.45]: [Transporter]: DBG-X: Apple's web service operation return value:
DEBUG [2019-04-10 14:19:06.45]: [Transporter]: DBG-X:   parameter SharedSecret = **hidden value**
DEBUG [2019-04-10 14:19:06.45]: [Transporter]: DBG-X:   parameter MultipartUploadsEnabled = true
DEBUG [2019-04-10 14:19:06.45]: [Transporter]: DBG-X:   parameter EnableJWTForAllCalls = false
DEBUG [2019-04-10 14:19:06.45]: [Transporter]: DBG-X:   parameter TxHeaders = {x-tx-dcroute=pv, jenga=true}
DEBUG [2019-04-10 14:19:06.45]: [Transporter]: DBG-X:   parameter SessionExpiration = 2019-04-14T12:19:06.326Z
DEBUG [2019-04-10 14:19:06.45]: [Transporter]: DBG-X:   parameter SessionId = CLCpDBIQA2Hi/A6tTsuz5wE2hX8BFw==
DEBUG [2019-04-10 14:19:06.45]: [Transporter]: DBG-X:   parameter StreamingSettings = {LogStreamingEnabled=true, MultipartUploadsEnabled=true, AssetDescriptionStreamingEnabled=false}
DEBUG [2019-04-10 14:19:06.50]: [Transporter]: INFO: Upload mode selected.
DEBUG [2019-04-10 14:19:06.51]: [Transporter]: INFO: Examining the package at: /var/folders/cd/gj5_1hl509l7js0hskrhxh_40000gn/T/d20190410-46780-1kz5zxn/1315653715.itmsp
DEBUG [2019-04-10 14:19:06.51]: [Transporter]: INFO: Ensuring that package has well formed metadata file...
DEBUG [2019-04-10 14:19:06.51]: [Transporter]: DEBUG: Getting case-sensitive metadata xml filename...
DEBUG [2019-04-10 14:19:06.51]: [Transporter]: INFO: Gathering the list of valid files from the package ...
DEBUG [2019-04-10 14:19:06.51]: [Transporter]: DEBUG:   640d7e84d2b71a8c30059facaeb50e5a961cee4f9f4a753edd3bf9714ed0ddc4.ipa will be verified by Apple's web service to determine if it is a valid file.
DEBUG [2019-04-10 14:19:06.51]: [Transporter]: DEBUG:   metadata.xml will be verified by Apple's web service to determine if it is a valid file.
DEBUG [2019-04-10 14:19:06.51]: [Transporter]: INFO: Finished gathering the list of valid files from the package.
DEBUG [2019-04-10 14:19:06.51]: [Transporter]: DEBUG:   Case-sensitive metadata filename is: metadata.xml
DEBUG [2019-04-10 14:19:06.54]: [Transporter]: INFO: Performing authentication of package<PHONE_NUMBER>.itmsp ...
DEBUG [2019-04-10 14:19:06.66]: [Transporter]: DBG-X: Memory: [JVM] 937M free, 981M total, 981M max [System] (Physical) 2026M free, 10240M total (Swap) 688M free, 2048M total
DEBUG [2019-04-10 14:19:06.66]: [Transporter]: DBG-X: Deflated 485 bytes to 424
DEBUG [2019-04-10 14:19:06.66]: [Transporter]: DBG-X: Using operation named: validateMetadata
DEBUG [2019-04-10 14:19:06.66]: [Transporter]: DBG-X: Apple's web service operation input parameters:
DEBUG [2019-04-10 14:19:06.66]: [Transporter]: DBG-X:   parameter Application = iTMSTransporter
DEBUG [2019-04-10 14:19:06.66]: [Transporter]: DBG-X:   parameter BaseVersion = 1.11.0
DEBUG [2019-04-10 14:19:06.66]: [Transporter]: DBG-X:   parameter Files = [640d7e84d2b71a8c30059facaeb50e5a961cee4f9f4a753edd3bf9714ed0ddc4.ipa, metadata.xml]
DEBUG [2019-04-10 14:19:06.66]: [Transporter]: DBG-X:   parameter Metadata = <?xml version="1.0" encoding="UTF-8"?>
DEBUG [2019-04-10 14:19:06.66]: [Transporter]: DBG-X:   parameter MetadataChecksum = 8dca4d63b0f6b56214d6909218477a3e
DEBUG [2019-04-10 14:19:06.66]: [Transporter]: DBG-X:   parameter MetadataCompressed = (suppressed)
DEBUG [2019-04-10 14:19:06.66]: [Transporter]: DBG-X:   parameter MetadataInfo = {app_platform=ios, primary_bundle_identifier=, device_id=, bundle_identifier=, packageVersion=software5.4, apple_id=1315653715, asset_types=[bundle], bundle_version=, bundle_short_version_string=}
DEBUG [2019-04-10 14:19:06.66]: [Transporter]: DBG-X:   parameter OSIdentifier = Mac OS X 10.14.4 (x86_64); jvm=25.71-b02; jre=1.8.0-u131-b11-iTMSTransporter-b02
DEBUG [2019-04-10 14:19:06.66]: [Transporter]: DBG-X:   parameter PackageName =<PHONE_NUMBER>.itmsp
DEBUG [2019-04-10 14:19:06.66]: [Transporter]: DBG-X:   parameter PackageSize = 159437295
DEBUG [2019-04-10 14:19:06.67]: [Transporter]: DBG-X:   parameter StatisticsClientStartDateTimeZoneISO = 2019-04-10T14:19:06+02:00
DEBUG [2019-04-10 14:19:06.67]: [Transporter]: DBG-X:   parameter Throttle = 100000
DEBUG [2019-04-10 14:19:06.67]: [Transporter]: DBG-X:   parameter TransporterArguments = -m upload -u<EMAIL_ADDRESS>-p **hidden value** -f /var/folders/cd/gj5_1hl509l7js0hskrhxh_40000gn/T/d20190410-46780-1kz5zxn/1315653715.itmsp -t DAV -t Signiant -k 100000
DEBUG [2019-04-10 14:19:06.67]: [Transporter]: DBG-X:   parameter Version = 1.13.0
DEBUG [2019-04-10 14:19:06.67]: [Transporter]: DBG-X:   parameter iTMSTransporterMode = upload
DEBUG [2019-04-10 14:19:06.67]: [Transporter]: INFO: id =<PHONE_NUMBER>1906-092
DEBUG [2019-04-10 14:19:06.67]: [Transporter]: INFO: iTMSTransporter Correlation Key: 7dd37ffd-df02-460b-8e49-fbdbdbb75195
DEBUG [2019-04-10 14:19:12.49]: [Transporter]: DBG-X: Apple's web service operation return value:
DEBUG [2019-04-10 14:19:12.49]: [Transporter]: DBG-X:   parameter EnableJWTForAllCalls = false
DEBUG [2019-04-10 14:19:12.49]: [Transporter]: DBG-X:   parameter SessionExpiration = 2019-04-14T12:19:07.626Z
DEBUG [2019-04-10 14:19:12.49]: [Transporter]: DBG-X:   parameter MinimumFileSizeThresholdForCheckum = 104857600
DEBUG [2019-04-10 14:19:12.49]: [Transporter]: DBG-X:   parameter SoftwareMediaDescriptionFormat = binary
DEBUG [2019-04-10 14:19:12.49]: [Transporter]: DBG-X:   parameter SoftwareMediaDescriptionThresholds = {in-app-purchase-content={extensions=[pkg], size=100000000}, ccats={extensions=[pdf], size=100000000}, product-archive={extensions=[pkg], size=100000000}, developer-id-package={extensions=[zip, pkg, dmg], size=100000000}, bundle={extensions=[zip, ipa], size=100000000}, large-icon={extensions=[jpg, png, jpeg], size=100000000}}
DEBUG [2019-04-10 14:19:12.49]: [Transporter]: DBG-X:   parameter Success = true
DEBUG [2019-04-10 14:19:12.49]: [Transporter]: DBG-X:   parameter StreamingSettings = {LogStreamingEnabled=true, MultipartUploadsEnabled=true, AssetDescriptionStreamingEnabled=false}
DEBUG [2019-04-10 14:19:12.49]: [Transporter]: DBG-X:   parameter FilesToUpload = [metadata.xml, 640d7e84d2b71a8c30059facaeb50e5a961cee4f9f4a753edd3bf9714ed0ddc4.ipa]
DEBUG [2019-04-10 14:19:12.49]: [Transporter]: DBG-X:   parameter AssetsToDescribe = [{Role=source, Filename=640d7e84d2b71a8c30059facaeb50e5a961cee4f9f4a753edd3bf9714ed0ddc4.ipa, ShouldDescribeAsset=true, UTI=com.apple.ipa}]
DEBUG [2019-04-10 14:19:12.49]: [Transporter]: DBG-X:   parameter CPUToken = 229b88d3-feff-4f91-ab0a-a3920c53fc25/1554898752046
DEBUG [2019-04-10 14:19:12.49]: [Transporter]: DBG-X:   parameter Checksums = {640d7e84d2b71a8c30059facaeb50e5a961cee4f9f4a753edd3bf9714ed0ddc4.ipa=e831af81edc48aab94f5867e01512b3c}
DEBUG [2019-04-10 14:19:12.49]: [Transporter]: DBG-X:   parameter FileSizes = {640d7e84d2b71a8c30059facaeb50e5a961cee4f9f4a753edd3bf9714ed0ddc4.ipa=159436810}
DEBUG [2019-04-10 14:19:12.49]: [Transporter]: DBG-X:   parameter ProviderNameForToken = COMPANY
DEBUG [2019-04-10 14:19:12.49]: [Transporter]: INFO: The list of files requested for upload by Apple is: [metadata.xml, 640d7e84d2b71a8c30059facaeb50e5a961cee4f9f4a753edd3bf9714ed0ddc4.ipa].  These are the files that will be uploaded.
DEBUG [2019-04-10 14:19:12.50]: [Transporter]: INFO: Starting media analysis of assets
DEBUG [2019-04-10 14:19:13.21]: [Transporter]: DEBUG: Handling asset: filename=640d7e84d2b71a8c30059facaeb50e5a961cee4f9f4a753edd3bf9714ed0ddc4.ipa,uti=com.apple.ipa,role=source,describe=true
DEBUG [2019-04-10 14:19:13.21]: [Transporter]: DEBUG: Using container type tool name and version: iOS App Describer:1.26
DEBUG [2019-04-10 14:19:13.21]: [Transporter]: DEBUG: Using path: /var/folders/cd/gj5_1hl509l7js0hskrhxh_40000gn/T/d20190410-46780-1kz5zxn/1315653715.itmsp/640d7e84d2b71a8c30059facaeb50e5a961cee4f9f4a753edd3bf9714ed0ddc4.ipa
DEBUG [2019-04-10 14:20:10.28]: [Transporter]: DBG-X: description length:0
DEBUG [2019-04-10 14:20:10.28]: [Transporter]: DBG-X: Asset description:
DEBUG [2019-04-10 14:20:10.29]: [Transporter]: DEBUG: Asset successfully described: com.apple.jingle.leghorn.software.AbstractSoftwareDescriber$1@3122b117
DEBUG [2019-04-10 14:20:10.44]: [Transporter]: DBG-X: Deflated 629 bytes to 383
DEBUG [2019-04-10 14:20:10.44]: [Transporter]: INFO: Asset media analysis has completed
DEBUG [2019-04-10 14:20:10.44]: [Transporter]: DBG-X: Memory: [JVM] 886M free, 981M total, 981M max [System] (Physical) 1888M free, 10240M total (Swap) 701M free, 2048M total
DEBUG [2019-04-10 14:20:10.44]: [Transporter]: DBG-X: Using operation named: lookupTransportDiagnostic
DEBUG [2019-04-10 14:20:10.44]: [Transporter]: DBG-X: Apple's web service operation input parameters:
DEBUG [2019-04-10 14:20:10.44]: [Transporter]: DBG-X:   parameter Application = iTMSTransporter
DEBUG [2019-04-10 14:20:10.44]: [Transporter]: DBG-X:   parameter BaseVersion = 1.11.0
DEBUG [2019-04-10 14:20:10.44]: [Transporter]: DBG-X:   parameter OSIdentifier = Mac OS X 10.14.4 (x86_64); jvm=25.71-b02; jre=1.8.0-u131-b11-iTMSTransporter-b02
DEBUG [2019-04-10 14:20:10.44]: [Transporter]: DBG-X:   parameter StatisticsClientStartDateTimeZoneISO = 2019-04-10T14:20:10+02:00
DEBUG [2019-04-10 14:20:10.44]: [Transporter]: DBG-X:   parameter TransporterArguments = -m upload -u<EMAIL_ADDRESS>-p **hidden value** -f /var/folders/cd/gj5_1hl509l7js0hskrhxh_40000gn/T/d20190410-46780-1kz5zxn/1315653715.itmsp -t DAV -t Signiant -k 100000
DEBUG [2019-04-10 14:20:10.44]: [Transporter]: DBG-X:   parameter Version = 1.13.0
DEBUG [2019-04-10 14:20:10.44]: [Transporter]: DBG-X:   parameter iTMSTransporterMode = upload
DEBUG [2019-04-10 14:20:10.44]: [Transporter]: INFO: id =<PHONE_NUMBER>2010-650
DEBUG [2019-04-10 14:20:10.46]: [Transporter]: INFO: iTMSTransporter Correlation Key: 7dd37ffd-df02-460b-8e49-fbdbdbb75195
DEBUG [2019-04-10 14:20:25.65]: [Transporter]: DBG-X: Apple's web service operation return value:
DEBUG [2019-04-10 14:20:25.65]: [Transporter]: DBG-X:   parameter AsperaLoggingLevel = OFF
DEBUG [2019-04-10 14:20:25.65]: [Transporter]: DBG-X:   parameter EnableJWTForAllCalls = false
DEBUG [2019-04-10 14:20:25.65]: [Transporter]: DBG-X:   parameter SigniantLoggingLevel = OFF
DEBUG [2019-04-10 14:20:25.65]: [Transporter]: DBG-X:   parameter SessionExpiration = 2019-04-14T12:20:10.752Z
DEBUG [2019-04-10 14:20:25.65]: [Transporter]: DBG-X:   parameter StreamingSettings = {LogStreamingEnabled=true, MultipartUploadsEnabled=true, AssetDescriptionStreamingEnabled=false}
DEBUG [2019-04-10 14:20:28.81]: [Transporter]: DBG-X: WebDAV status: 401
DEBUG [2019-04-10 14:20:28.83]: [Transporter]: DEBUG: Using token file path /Users/user/Library/Caches/com.apple.amp.itmstransporter/UploadTokens/mac-mini-developers.local_COMPANY_1315653715.itmsp.token
DEBUG [2019-04-10 14:20:28.83]: [Transporter]: DEBUG: Attempting exclusive file lock on token file
DEBUG [2019-04-10 14:20:28.83]: [Transporter]: DEBUG: Token exists, examining
DEBUG [2019-04-10 14:20:28.89]: [Transporter]: DEBUG: Token pid: 14128, found process = false; my pid: 46978
DEBUG [2019-04-10 14:20:28.94]: [Transporter]: DEBUG: Reusing existing token: 8a4e0fef-d96f-4efc-add6-be9099046606/1554892269720
DEBUG [2019-04-10 14:20:28.95]: [Transporter]: DEBUG: Set token: 8a4e0fef-d96f-4efc-add6-be9099046606/1554892269720
DEBUG [2019-04-10 14:20:28.95]: [Transporter]: DBG-X: Memory: [JVM] 877M free, 981M total, 981M max [System] (Physical) 1875M free, 10240M total (Swap) 701M free, 2048M total
DEBUG [2019-04-10 14:20:28.95]: [Transporter]: DBG-X: Deflated 485 bytes to 424
DEBUG [2019-04-10 14:20:28.95]: [Transporter]: DBG-X: Using operation named: validateAssets
DEBUG [2019-04-10 14:20:28.95]: [Transporter]: DBG-X: Apple's web service operation input parameters:
DEBUG [2019-04-10 14:20:28.95]: [Transporter]: DBG-X:   parameter Application = iTMSTransporter
DEBUG [2019-04-10 14:20:28.95]: [Transporter]: DBG-X:   parameter BaseVersion = 1.11.0
DEBUG [2019-04-10 14:20:28.95]: [Transporter]: DBG-X:   parameter CPUToken = 8a4e0fef-d96f-4efc-add6-be9099046606/1554892269720
DEBUG [2019-04-10 14:20:28.95]: [Transporter]: DBG-X:   parameter Files = [640d7e84d2b71a8c30059facaeb50e5a961cee4f9f4a753edd3bf9714ed0ddc4.ipa, metadata.xml]
DEBUG [2019-04-10 14:20:28.95]: [Transporter]: DBG-X:   parameter MetadataChecksum = 8dca4d63b0f6b56214d6909218477a3e
DEBUG [2019-04-10 14:20:28.95]: [Transporter]: DBG-X:   parameter MetadataCompressed = (suppressed)
DEBUG [2019-04-10 14:20:28.95]: [Transporter]: DBG-X:   parameter MetadataInfo = {app_platform=ios, primary_bundle_identifier=, device_id=, bundle_identifier=, packageVersion=software5.4, apple_id=1315653715, asset_types=[bundle], bundle_version=, bundle_short_version_string=}
DEBUG [2019-04-10 14:20:28.95]: [Transporter]: DBG-X:   parameter OSIdentifier = Mac OS X 10.14.4 (x86_64); jvm=25.71-b02; jre=1.8.0-u131-b11-iTMSTransporter-b02
DEBUG [2019-04-10 14:20:28.95]: [Transporter]: DBG-X:   parameter PackageName =<PHONE_NUMBER>.itmsp
DEBUG [2019-04-10 14:20:28.95]: [Transporter]: DBG-X:   parameter PackageSize = 159437295
DEBUG [2019-04-10 14:20:28.95]: [Transporter]: DBG-X:   parameter RequestUUID = b10a9c47-89b2-4f9b-8f0e-e91401f781da
DEBUG [2019-04-10 14:20:28.95]: [Transporter]: DBG-X:   parameter StatisticsClientStartDateTimeZoneISO = 2019-04-10T14:20:28+02:00
DEBUG [2019-04-10 14:20:28.95]: [Transporter]: DBG-X:   parameter StreamingInfoList = [file: ef634036-9628-4de0-acd7-9d80e299c9901802750822170094236.swinfo.plist.gz, content-length: 588870, content-type: application/binary, MD5: f6f8647105b87becdde0125c9c938862]
DEBUG [2019-04-10 14:20:28.95]: [Transporter]: DBG-X:   parameter Throttle = 100000
DEBUG [2019-04-10 14:20:28.95]: [Transporter]: DBG-X:   parameter Transport = DAV
DEBUG [2019-04-10 14:20:28.95]: [Transporter]: DBG-X:   parameter TransporterArguments = -m upload -u<EMAIL_ADDRESS>-p **hidden value** -f /var/folders/cd/gj5_1hl509l7js0hskrhxh_40000gn/T/d20190410-46780-1kz5zxn/1315653715.itmsp -t DAV -t Signiant -k 100000
DEBUG [2019-04-10 14:20:28.95]: [Transporter]: DBG-X:   parameter Version = 1.13.0
DEBUG [2019-04-10 14:20:28.95]: [Transporter]: DBG-X:   parameter iTMSTransporterMode = upload
DEBUG [2019-04-10 14:20:28.95]: [Transporter]: INFO: id =<PHONE_NUMBER>2028-244