-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
upload_to_testflight(distribute_only:true) stuck on "Waiting for the build to show up in the build list" #18606
Comments
As I have to get this particular app out to TestFlight, I tried to move ahead with using my FastLane script to build from source and upload to TestFlight, but
$ fastlane beta
[✔] 🚀
[18:59:00]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
[18:59:03]: ---------------------
[18:59:03]: --- Step: team_id ---
[18:59:03]: ---------------------
[18:59:03]: Setting Team ID to 'xxx' for all build steps
[18:59:03]: ------------------------------
[18:59:03]: --- Step: default_platform ---
[18:59:03]: ------------------------------
[18:59:03]: Driving the lane 'ios beta' 🚀
[18:59:03]: ------------------------------------------
[18:59:03]: --- Step: Switch to ios edit_file lane ---
[18:59:03]: ------------------------------------------
[18:59:03]: Cruising over to lane 'ios edit_file' 🚖
[18:59:07]: Cruising back to lane 'ios beta' 🚘
[18:59:07]: ---------------------------------------------------
[18:59:07]: --- Step: Switch to ios ipa_from_xcarchive lane ---
[18:59:07]: ---------------------------------------------------
[18:59:07]: Cruising over to lane 'ios ipa_from_xcarchive' 🚖
[18:59:07]: ---------------------
[18:59:07]: --- Step: xcbuild ---
[18:59:07]: ---------------------
[18:59:07]: For a more detailed xcodebuild log open /Users/xxx/Library/Logs/fastlane/xcbuild/2021-04-26/12503/xcodebuild.log
[18:59:07]: $ set -o pipefail && xcodebuild -exportArchive -archivePath "XXX 4-26-21, 6.56 PM.xcarchive" -exportPath "." -exportOptionsPlist "../../../ios-support/export_options.plist" build | tee '/Users/xxx/Library/Logs/fastlane/xcbuild/2021-04-26/12503/xcodebuild.log' | xcpretty --color --simple
[18:59:08]: ▸ 2021-04-26 18:59:08.918 xcodebuild[12515:7122859] [MT] IDEDistribution: -[IDEDistributionLogging _createLoggingBundleAtPath:]: Created bundle at path '/var/folders/qz/bjhhs9x127l0jp8rrv7c_hvr0000gp/T/XXX_2021-04-26_18-59-08.917.xcdistributionlogs'.
[18:59:10]: ▸ Export Succeeded
[18:59:10]: Exported .ipa from XXX 4-26-21, 6.56 PM.xcarchive
[18:59:10]: Cruising back to lane 'ios beta' 🚘
[18:59:10]: -------------------------------------------
[18:59:10]: --- Step: Switch to ios resign_ipa lane ---
[18:59:10]: -------------------------------------------
[18:59:10]: Cruising over to lane 'ios resign_ipa' 🚖
[18:59:10]: --------------------------------------
[18:59:10]: --- Step: get_provisioning_profile ---
[18:59:10]: --------------------------------------
+-------------------------------------+------------------------+ [18:59:10]: Starting login with user 'xxx@xxx.xxx' [18:59:16]: Successfully signed xxx.ipa! +------+------------------------+-------------+ [19:04:17]: fastlane finished with errors Looking for related GitHub issues on fastlane/fastlane... ➡️ 500 server error ➡️ beta_pa path is relative to the fastlane directory, not the project directory ➡️ Deliver fails with error 500 on price tire update phase 🔗 You can ⌘ + double-click on links to open them directly in your browser. [!] The request could not be completed because: Unfortunately, I didn't get a stack trace as I didn't use the
$ fastlane beta distribute_only:true --verbose
[✔] 🚀
[19:16:33]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
DEBUG [2021-04-26 19:16:34.96]: Checking if there are any plugins that should be loaded...
Successfully loaded Appfile at path '/xxx/ios/fastlane/Appfile'
- app_identifier: 'xxx'
-------
Successfully loaded Appfile at path '/xxx/ios/fastlane/Appfile'
- app_identifier: 'xxx'
-------
DEBUG [2021-04-26 19:16:36.73]: Using distribute_only: true
Successfully loaded Appfile at path '/xxx/ios/fastlane/Appfile'
- app_identifier: 'xxx'
-------
Successfully loaded Appfile at path '/xxx/ios/fastlane/Appfile'
- app_identifier: 'xxx'
-------
INFO [2021-04-26 19:16:36.75]: ---------------------
INFO [2021-04-26 19:16:36.75]: --- Step: team_id ---
INFO [2021-04-26 19:16:36.75]: ---------------------
INFO [2021-04-26 19:16:36.76]: Setting Team ID to 'xxx' for all build steps
Successfully loaded Appfile at path '/xxx/ios/fastlane/Appfile'
- app_identifier: 'xxx'
-------
INFO [2021-04-26 19:16:36.76]: ------------------------------
INFO [2021-04-26 19:16:36.76]: --- Step: default_platform ---
INFO [2021-04-26 19:16:36.76]: ------------------------------
Successfully loaded Appfile at path '/xxx/ios/fastlane/Appfile'
- app_identifier: 'xxx'
-------
Successfully loaded Appfile at path '/xxx/ios/fastlane/Appfile'
- app_identifier: 'xxx'
-------
INFO [2021-04-26 19:16:36.76]: Driving the lane 'ios beta' 🚀
INFO [2021-04-26 19:16:36.77]: ------------------------------------------
INFO [2021-04-26 19:16:36.77]: --- Step: Switch to ios edit_file lane ---
INFO [2021-04-26 19:16:36.77]: ------------------------------------------
INFO [2021-04-26 19:16:36.77]: Cruising over to lane 'ios edit_file' 🚖
INFO [2021-04-26 19:17:33.51]: Cruising back to lane 'ios beta' 🚘
Successfully loaded Appfile at path '/xxx/ios/fastlane/Appfile'
- app_identifier: 'xxx'
-------
Successfully loaded Appfile at path '/xxx/ios/fastlane/Appfile'
- app_identifier: 'xxx'
-------
Successfully loaded Appfile at path '/xxx/ios/fastlane/Appfile'
- app_identifier: 'xxx'
-------
Successfully loaded Appfile at path '/xxx/ios/fastlane/Appfile'
- app_identifier: 'xxx'
-------
Successfully loaded Appfile at path '/xxx/ios/fastlane/Appfile'
- app_identifier: 'xxx'
-------
Successfully loaded Appfile at path '/xxx/ios/fastlane/Appfile'
- app_identifier: 'xxx'
-------
Successfully loaded Appfile at path '/xxx/ios/fastlane/Appfile'
- app_identifier: 'xxx'
-------
Successfully loaded Appfile at path '/xxx/ios/fastlane/Appfile'
- app_identifier: 'xxx'
-------
Successfully loaded Appfile at path '/xxx/ios/fastlane/Appfile'
- app_identifier: 'xxx'
-------
Successfully loaded Appfile at path '/xxx/ios/fastlane/Appfile'
- app_identifier: 'xxx'
-------
Successfully loaded Appfile at path '/xxx/ios/fastlane/Appfile'
- app_identifier: 'xxx'
-------
Successfully loaded Appfile at path '/xxx/ios/fastlane/Appfile'
- app_identifier: 'xxx'
-------
INFO [2021-04-26 19:17:33.66]: ----------------------------------
INFO [2021-04-26 19:17:33.66]: --- Step: upload_to_testflight ---
INFO [2021-04-26 19:17:33.66]: ----------------------------------
INFO [2021-04-26 19:17:33.66]: Login to App Store Connect (xxx@xxx.xxx)
Reading keychain entry, because either user or password were empty
Loading session from '/Users/xxx/.fastlane/spaceship/xxx@xxx.xxx/cookie'
Looking for App Store Connect Team with name Georgia Tech Research Corporation
Looking for App Store Connect Team with ID 420283
INFO [2021-04-26 19:17:34.66]: Login successful
DEBUG [2021-04-26 19:17:34.66]: App Platform (ios)
DEBUG [2021-04-26 19:17:34.68]: App identifier (xxx)
INFO [2021-04-26 19:17:37.85]: Waiting for processing on... app_id: xxx, app_version: 1.0.0, build_version: 2, platform: IOS
INFO [2021-04-26 19:17:38.30]: Successfully finished processing the build 1.0.0 - 2 for IOS
WARN [2021-04-26 19:17:38.30]: No build specified - fetching latest build
DEBUG [2021-04-26 19:17:38.30]: App Platform (ios)
WARN [2021-04-26 19:17:39.43]: Using App Store Connect's default for notifying external testers (which is true) - set `notify_external_testers` for full control
INFO [2021-04-26 19:17:39.43]: Distributing new build to testers: 1.0.0 - 2
Timeout received! Retrying after 3 seconds (remaining: 5)...
Timeout received! Retrying after 3 seconds (remaining: 4)...
Timeout received! Retrying after 3 seconds (remaining: 3)...
Timeout received! Retrying after 3 seconds (remaining: 2)...
Timeout received! Retrying after 3 seconds (remaining: 1)...
WARN [2021-04-26 19:17:40.94]: Lane Context:
INFO [2021-04-26 19:17:40.94]: {:DEFAULT_PLATFORM=>:ios, :PLATFORM_NAME=>:ios, :LANE_NAME=>"ios beta"}
ERROR [2021-04-26 19:17:40.94]: Server error got 500
INFO [2021-04-26 19:17:40.95]: Successfully generated documentation at path '/xxx/ios/fastlane/README.md'
+------+----------------------+-------------+ ERROR [2021-04-26 19:17:40.96]: fastlane finished with errors Looking for related GitHub issues on fastlane/fastlane... URL: https://api.github.com/search/issues?q=The%20request%20could%20not%20be%20completed%20because%3A%0A%09Server%20error%20got%20500+repo:fastlane/fastlane ➡️ beta_pa path is relative to the fastlane directory, not the project directory ➡️ Deliver fails with error 500 on price tire update phase 🔗 You can ⌘ + double-click on links to open them directly in your browser. These errors may be distinct from my original error, but I wanted to include them for context. Also, these errors may be related to other |
What is the build / version code? How is it different to your "old"/other apps? |
Thanks, @max-ott. In the first case ("Waiting..." loop), there was only a single build (build '1') and I used |
sadly, also getting this issue. it seemed to have started the last few days, prior to that, was working fine. Apple's API status indicates an outage on 4/28/21 https://developer.apple.com/system-status/ that could be related and started this, but whatever it is, something is still going on. We run our actions mostly on github actions and they usually work fine. I have noticed that randomly, if I run this command locally on my own mac, it works fine, whereas Github gets stuck. I'm wondering if Apple changed something that breaks this command. |
We've been having the same issue. We had to fall back on manually uploading the files to the App Store. Btw...when I ran fastlane to send the dSyms to Firebase Apple sent me a text code that I had to type into fastlane. Is there a chance that Apple's APIs now have a new layer of security that's blocking fastlane? Btw, we use fastlane with CircleCI. |
2 factor authentication is now required for already 2 months or so. |
Thanks @max-ott, our fastlane+CircleCI started failing just last week |
@max-ott how would we even do 2FA with fastlane and a hosted CircleCI build process? |
Apple ID sessions are usually valid for 30 days, that’s why yours might have worked so long. Use App Store Connect API key (recommended) or copy over Apple ID session Cookies (https://docs.fastlane.tools/best-practices/continuous-integration/#authenticating-with-apple-services) |
Wow, thanks @max-ott. It's so kind of you to reply, on a Sunday no less! |
p.s. Method 3 looks like a winner! Thanks again @max-ott https://docs.fastlane.tools/best-practices/continuous-integration/#method-3-application-specific-passwords |
This appears to be the same issue that I am having. I am using the AppStore API key and manually grabbing the latest build number (because it was failing to automatically select the latest build number). fastfile:
output:
And it continues waiting until the bulid server times out. |
@andrewclaus I ensure that our main App Store account and the app specific password were in CircleCI and it worked again. See the link from @max-ott above. |
We are suddenly running into this problem as well. The build is correctly uploaded, but then at the end we're getting the
Not sure if this related to the |
Setting The only difference in the |
@EmDee it's related to Apple's 2FA. We did the apple id and app-specific password and it's back to working fine. @max-ott shared https://docs.fastlane.tools/best-practices/continuous-integration/#method-3-application-specific-passwords and it has other options |
Mine (and I think OP‘s) is a different issue though. I‘ve been using the session cookie solution for a while now. The server 500 error is definitely a new one. I would venture and say something has changed on Apple‘s side, but I just don’t understand (yet) why another of our apps doesn’t run into this problem (both using the same session cookie). |
As expected changing the This error sounds very similar to #17886 (comment), but that one was closed stating that Apple has fixed it. @HolySamosa Are you still experiencing the same behavior? |
It seems like there was a new fastlane release with an update to the build watcher that went live today, #18682 So instead of the infinite loop of "Waiting for the build to show up in the build list", I get this error instead: I am not sure what is wrong.. This new error is still not helpful in tracking down the problem. I am trying to distribute this testflight version to my external test group. This build version exists in testflight in the "Approved" status. Additional ouput
|
I am not sure if this can help you, but we just had a similar issue. Before we were only passing the build number to the pilot call in order to submit the build. After latest update that does not work anymore, and we had now to also pass the app version as a parameter, otherwise it was trying to get a different version from the app store connect API. |
I spent some time investigating how fastlane/fastlane_core/lib/fastlane_core/build_watcher.rb Lines 63 to 78 in 44431ba
When
fastlane/pilot/lib/pilot/build_manager.rb Lines 92 to 110 in 7cc8c67
My understanding is that for To have the same logic as before and match the logic without waiting for build processing enabled: fastlane/pilot/lib/pilot/build_manager.rb Lines 125 to 138 in 7cc8c67
code below fastlane/fastlane_core/lib/fastlane_core/build_watcher.rb Lines 84 to 92 in 7cc8c67
could be changed to: if versions.empty?
message = watched_build_version.nil? ? "Searching for the latest build" : "Searching for the latest build with build number: #{watched_build_version}"
UI.message(message)
versions = [nil]
end |
I've tried running the This is the output:
|
Wow, I should've caught this one earlier... my problem is (probably) completely unrelated to this issue. I've switched the main app language a while back and apparently forgot to setup the information for the testers. The TestFlight section in the App Store Connect was telling me all along, but I somehow completely missed/ignored it. That's why it was failing for me with the server error 500 message. |
New Issue Checklist
Issue Description
In my Fastfile, I'm executing
upload_to_testflight()
with the optiondistribute_only:true
, however Fastlane is is becoming stuck on "Waiting for the build to show up in the build list"-- which shouldn't happen for thedistribute_only:true
option.I use this same Fastfile for many apps and this has worked previously for other apps. One key difference, however, is the other apps had builds that were previously submitted to TestFlight through a typical FastLane build process, i.e. FastLane building the app locally and then uploading to TestFlight. This problem is appearing with a new app with a build uploaded by another developer and my FastLane script is trying to distribute this build as the first submission to TestFlight.
Command executed
fastlane beta distribute_only:true
The "beta" action from my FastFile follows.
Complete output when running fastlane, including the stack trace and command used
The following output includes the breaking of the script with
control-C
. Otherwise, the script seems to remain indefinitely stuck in the "Waiting..." loop.Environment
The text was updated successfully, but these errors were encountered: