fastlane: [spaceship, pilot] Getting "410 gone"
New Issue Checklist
- Updated fastlane to the latest version
- I read the Contribution Guidelines
- I read docs.fastlane.tools
- 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 (engineering@shoguninc.com) [14:20:49]: Login successfulLooking 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’: [!] <html> (Spaceship::UnexpectedResponse)
<head> <meta http-equiv="Content-Type" content="text/html;charset=utf-8"/> <title>Error 410 Gone</title> </head> <body>HTTP ERROR 410
Problem accessing /v2/providers/118458784/apps/1383073333/platforms/ios/trains. Reason:
Gone</body> </html>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 `<main>'
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 124
- Comments: 177 (75 by maintainers)
Hey everyone! I will be finishing this up tomorrow 💪 Getting married next week and had a migraine thing 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
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
pilotstill which involves completely removing the use of theSpaceship::TestFlightmodule in favor ofSpaceship::ConnectAPI🔥 Once this next phase is complete it should end up with a more stable version ofpilotsince 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 🤘🚀
I appreciated everyone offering any help ❤️ I think the biggest thing here would just be patience 😇
I’m super close but I need to get some 💤s now 😔 Hopefully I can button some things up here in the morning 🤞
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 🤞BTW… nobody installs my apps 😇 Those 0s are correct 😢
Going to be releasing a version with this tonight 😬😬😬😬😬😬😬😬😬😬😬😬😬😬😬😬
NOW
pilot/upload_to_testflight,latest_testflight_build_number, anddownload_dsymsshould be back to normal ❤️ Put this in yourGemfileto switch to my branch and run withbundle installorbundle update. The latest commit is https://github.com/fastlane/fastlane/pull/14523/commits/e476888f4c537e81885275471890b073a8493b72Let me know if there is anything else that you run into that is busted. In the meantime I’ll be fixing all those tests 🔨
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 inSpaceship::TestFlightover to new API inSpaceship::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 🙃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
buildDeliveriesthat is a holding spot for builds while they are processing. After a while the build will then appear inbuildsfor a bit and been seen as processing. After a little bit there it will then be shown inbuildsasVALID🙄The final fix is now to fix the
/v2/providers/.../apps/.../groups. And THEN clean up some code 💪@joshdholtz hey, still getting it. Error for
fastlane pilot builds:Seems to be an issue with App Store Connect.
RIP this route ☠️ Will look into to see what we can replace it with tonight 🙃
@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!
Not a problem! Pre-thanks to everyone who will be yolo testing branch 🙃
No rush @joshdholtz. We found a way to fix our pipeline meanwhile.
@joshdholtz Thanks for all your hard work on this.
I am receiving this issue as well. On top of the getting the latest build number is not working either.
Ahhh, I will tackle that one next before working on tests 😇 That’s more fun anyway 😉
We did it!!! Thanks again for all the patience ❤️ Put this in your
Gemfileto switch to my branch and run withbundle installorbundle updateMy 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
Thank you so much for the hard work and dedication, not only for this issue but the entire product!
@adamirowe That is probably exactly why 🙄 I’m currently working on retrofitting the
Spaceship::TestFlight::Buildmethods andFastlaneCore::BuildWatcherto 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 😬
@cubedivone @florianbuerger @tberman @joelgetaction
Okay! Just removed the
wait_for_uploaded_buildoption as its not longer needed and was confusing. Thing should work for everybody now ❤️ Put this in yourGemfileto switch to my branch and run withbundle installorbundle update. Latest commit is https://github.com/fastlane/fastlane/pull/14523/commits/e83b17724412b671b867db25979069ea0c5e5d78@PatrickNLT Pushed another fix for that! If you want to try running
bundle updateagain you should be 💯@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 💪
👋 @joshdholtz
I just switch to your branch and executed the lane where we are using
latest_testflight_build_number. Below you can find the logs:X.Y.ZandXXXare the correct ones (I did hide them, cannot make it public 🙂) - version and build number 🎉Amazing job 👏 👏
This issue is still there in fastlane 2.120.0 :
@cubedivone I THINK I FOUND YOUR ERROR! Fixing 💪
Fixed. Thank you so much @joshdholtz !
fwiw I’m getting it as well …
And the stack trace is …
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 💪
@AvdLee WAAIIITTT… I think I know!! Fix incoming
I pushed up some more changes!
@cubedivone This should fix your error!
👋 Also, if there is anybody that is having
latest_testflight_build_number, if you could update to this and paste your console output in a comment that would be a huge help ❤️Put this in your
Gemfileto switch to my branch and run withbundle installorbundle update. Latest commit is https://github.com/fastlane/fastlane/pull/14523/commits/e83b17724412b671b867db25979069ea0c5e5d78I 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.
Have a good mariage and take time to enjoy the moment, the big day is really short 😃
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:
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!
(@lancedolan
pilotis the code “part” that is run when usingupload_to_testflight, andspaceshipis one more level down that is used bypilotto communicate with Apple’s services in the background 🚀 )/v2/providers/xxxx/apps/xxxx/groups- API used for retrieving the TestFlight groups, seems also broken for us:Anyone facing the same issue?
Yes even though I only have 1 version number and I deployed last night with no issues
@mystikxkemix, @rajivshah3 I’ve been temporarily using the workaround posted here: https://github.com/fastlane/fastlane/issues/14521#issuecomment-480975140
add_tester_to_group!creates the tester and adds it to the group@jsilarow have you created an issue for the problem you mentioned? (https://github.com/fastlane/fastlane/issues/14521#issuecomment-481605625)
I see the same error.
2.119 works in terms of getting
latest_testflight_build_numberif the bundleVersion doesn’t exist already. 2.220 only works withlatest_testflight_build_numberif the bundleVersion is already there.I’m still having hard times with
latest_testflight_build_numberWhen 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:
@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::TestFlightis 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!Same for
/v2/providers/xxx/apps/xxx/testersand/v2/providers/xxx/apps/xxx/groupsWe use spaceship on a ruby script to invite users to TestFlight. Multiple operations stated failing recently, like
Spaceship::TestFlight::Tester.create_app_level_tester.I was able to create some alternative versions on my side by doing:
I’m not sure those APIs are public, but I was able to find those by introspecting XHR requests made by AppStore Connect web interface. Not the best code either, but those workarounds are working for me.
It takes not the latest one version for example my latest 1.2.1 but it takes first one 1.1.3
I didn’t wanna bog up the notifications but to hell with it 😅, +1 with ^. Amazing work @joshdholtz, and very thoughtful to keep everyone informed with the statuses along the way.
Have a great wedding! 🕺
Yes, I’m still getting
410 Gonewhile trying to upload tf build viaupload_to_testflightaction. The fastlane is installed with bundler fromjoshdholtz-pilot-fixes-removed-build-trains@e191207. If you need logs, please, let me know.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
Yes @adamirowe, the error is exactly the same
The custom branch fixes publishing but not pilot import of a testers.csv, you get the same type of error.
<meta http-equiv="Content-Type" content="text/html;charset=utf-8"/> <title>Error 410 Gone</title> </head> <body>HTTP ERROR 410
Problem accessing /v2/providers/098723876r23/apps/24535t356/groups. Reason:
</body> </html>@nihp and anyone else who is experiencing the “No Builds” issue on TestFlight – there is a forum issue that I’ve been following for this: https://forums.developer.apple.com/message/355676
I called apple dev support and they said they’re aware of the issue and that it has been passed along to their engineers but they couldn’t give me a timeline or priority level. I too am able to uploads builds to TestFlight after the fixes mentioned above, but the build just doesn’t show up 😦
I see a lot of people hitting issues - just thought I’d say all looks well for us! Working great.
@joshdholtz Getting the latest build number is not working. I’m getting an error saying “Could not find a build number for version”.
The fastlane version I’m using is 2.120.0
Hi, as @jsilarow pointed out, the fix works well for an existing version, with the new one seems not working (also using the initial_build_number parameter).
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!': [31m[!] Could not find a build number for version 1.1.7[0m (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:inmethod_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:inget_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:inrun’ 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:inrun' 11:57:01 from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/fastlane/lib/fastlane/runner.rb:256:inblock (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:inexecute_action' 11:57:01 from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/fastlane/lib/fastlane/runner.rb:235:inblock in execute_action’ 11:57:01 from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/fastlane/lib/fastlane/runner.rb:227:inchdir' 11:57:01 from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/fastlane/lib/fastlane/runner.rb:227:inexecute_action’ 11:57:01 from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/fastlane/lib/fastlane/runner.rb:157:intrigger_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:inmethod_missing’ 11:57:01 from Fastfile:68:inblock (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:incall’ 11:57:01 from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/fastlane/lib/fastlane/runner.rb:49:inblock in execute' 11:57:01 from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/fastlane/lib/fastlane/runner.rb:45:inchdir’ 11:57:01 from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/fastlane/lib/fastlane/runner.rb:45:inexecute' 11:57:01 from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/fastlane/lib/fastlane/lane_manager.rb:56:incruise_lane’ 11:57:01 from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/fastlane/lib/fastlane/command_line_handler.rb:36:inhandle' 11:57:01 from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/fastlane/lib/fastlane/commands_generator.rb:108:inblock (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:incall' 11:57:01 from /Library/Ruby/Gems/2.3.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:inrun’ 11:57:01 from /Library/Ruby/Gems/2.3.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:inrun_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:inrun!’ 11:57:01 from /Library/Ruby/Gems/2.3.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:inrun!' 11:57:01 from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/fastlane/lib/fastlane/commands_generator.rb:333:inrun’ 11:57:01 from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/fastlane/lib/fastlane/commands_generator.rb:41:instart' 11:57:01 from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.120.0/fastlane/lib/fastlane/cli_tools_distributor.rb:119:intake_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:inload’ 11:57:01 from /usr/local/bin/fastlane:22:in `<main>’You were right, it’s fixed! 🎉 Great work @joshdholtz. Time for you to get a beer and take a moment to relax! 😄
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:
We’re running the TestFlight command as following:
Let me know if this helps and if you have any further questions!
@fossage Can you run
bundle update fastlaneif 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 😊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_sand replaced calls to latest_testflight_build_number with ENV[‘BUILD_NUMBER’] I also moved my addTagAndPush lane before calling pilot.
Upload_to_testflight work for me. With the modified Gemfile. Did not test latest_testflight_build_number. Thanks for good work!
@arnmtk Probably not this one 😬 Can you create a brand new issue with what you are seeing?
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
Let me know if anyone faces any issue with this.
@sonjz I’ve temporarily replaced
Spaceship::TestFlight::Tester.create_app_level_testerby theadd_tester_to_group!function I posted here. That works as a workaround. It creates the tester and adds it to thegroup_id.FYI, that was just an example. Other actions that were failing for us are:
Spaceship::TestFlight::Group.all,Spaceship::TestFlight::Tester.remove_from_testflight!andSpaceship::TestFlight::Tester.remove_from_app!This worked for me. Thank you! ❤️
@joshdholtz I just uploaded using
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_buildand I believe that defaults tofalse.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.
@joshdholtz I’m having a failure here 🤔
Another big thank you to @joshdholtz for resolving this !
Nice work
@joshdholtz looks good now, thanks a lot!
@mario462 @cubedivone @mwoollard Can you update to the latest commit and try again?! This should do it 🤞 Just pushed some stuff (https://github.com/fastlane/fastlane/pull/14523/commits/b0eb8ce3fd106194a7636ee9c09810e81f12a9f4) which should also fix the
download_dsymsaction@ramnac I will have a commit for the
latest_testflight_build_numberbut thanks for posting that in the meantime ❤️@joshdholtz I am still getting a version number of
1when I runbundle exec fastlane run latest_testflight_build_numberwith latest from your branch.
Anything I can do to help figure out whats happening there?
I’ve tried
fastlane update_fastlaneand I’m still getting the error. How do I update fastlane to the latest version which works?Hi ya’ll. @jbruce2112 @paulkite and I came across this issue too, but we tag our releases with the build number. If you tag your releases, you can easily perform a workaround by regexing your tags and pulling out the highest 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
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
@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_numbernumber looks like. Progress though! 😃@joshdholtz I believe #14476 is related.
latest_testflight_build_numberfails and always returns 1. Any ideas on a fix for that?I’m not familiar with what
pilotorspaceshipis, but we are hitting this while running these commands in ourFastfile:Hopefully this is helpful and not redundant.
Experiencing the same issue using Spaceship while trying to deploy to Heroku:
Did they really remove an API endpoint without notice?