Uploading to TestFlight hangs at "waiting for the build..." for very long time

[miko1258]

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

Uploading process hangs on Waiting for the build to show up in the build list - this may take a few minutes (check your email for processing issues if this continues). In the AppStore Connect build was processed and has state: "Ready to Submit". I gave up after 173 minutes and manually stopped deployment. I followed the documentation in order to set up this lane. Do I miss something important? I use api key with "App Manager" role to authenticate.

Command executed

fastlane ios_internal artifact:"XXXXXXXX" distribute_groups:"true" notify_groups:"true" group:"XXXX" changelog:"XXXXX" skip_waiting:"false"

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

[bamboo-deployment.log](https://github.com/fastlane/fastlane/files/5874149/bamboo-deployment.log)

Environment

✅ fastlane environment ✅

Stack

Key	Value
OS	11.1
Ruby	2.6.3
Bundler?	false
Git	git version 2.28.0
Installation Source	/usr/local/bin/fastlane
Host	macOS 11.1 (20C69)
Ruby Lib Dir	/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib
OpenSSL Version	LibreSSL 2.8.3
Is contained	false
Is homebrew	false
Is installed via Fabric.app	false
Xcode Path	/Applications/Xcode.app/Contents/Developer/
Xcode Version	12.3

System Locale

Variable	Value
LANG	en_US.UTF-8	✅
LC_ALL	en_US.UTF-8	✅
LANGUAGE

fastlane files:

`./fastlane/Fastfile`

# This file contains the fastlane.tools configuration
# You can find the documentation at https://docs.fastlane.tools
#
# For a list of all available actions, check out
#
#     https://docs.fastlane.tools/actions
#
# For a list of all available plugins, check out
#
#     https://docs.fastlane.tools/plugins/available-plugins
#

# Uncomment the line if you want fastlane to automatically update itself
# update_fastlane

lane :android_internal do |options|
  upload_to_play_store(
    track: 'internal',
    apk: options[:artifact]
  )
end

lane :ios_internal do |options|
    api_key = app_store_connect_api_key(
    key_id: "XXXXXXX",
    issuer_id: "XXXXXXXXXXXXXXXXX",
    key_filepath: "./fastlane/AuthKey_XXXXXXXX.p8",
    in_house: "false"
  )

  upload_to_testflight(
    api_key: api_key,
    ipa: options[:artifact],
    distribute_external: options[:distribute_groups],
    notify_external_testers: options[:notify_groups],
    groups: options[:group],
    changelog: options[:changelog],
    skip_waiting_for_build_processing: options[:skip_waiting]
  )

end

lane :announcement do |options|
  teams(
    title: "XXXXXXXX",
    message: "App was successfully released!",
     facts:[
      {
        "name"=>"Version",
        "value"=>options[:version]
      },
      {
        "name"=>"Build",
        "value"=>options[:build_number]
      },
      {
        "name"=>"Track",
        "value"=>options[:track]
      }
    ],
    teams_url: options[:teams_url]
  )
end

`./fastlane/Appfile`

# For more information about the Appfile, see:
#     https://docs.fastlane.tools/advanced/#appfile

#iOS
app_identifier("XXXXXXXXXXXXXXX")
apple_id("XXXXXXXXXXXXXX@XXXXXX.com")

#Android
json_key_file "fastlane/XXXXXXXXXXXXXXXXXXXXX.json"
package_name "XXXXXXXXXXXXX"

fastlane gems

Gem	Version	Update-Status
fastlane	2.172.0	✅ Up-To-Date

Loaded fastlane plugins:

Plugin	Version	Update-Status
fastlane-plugin-teams	0.2.0	✅ Up-To-Date

Loaded gems

Gem	Version
did_you_mean	1.5.0
slack-notifier	2.3.2
atomos	0.1.3
claide	1.0.3
colored2	3.1.2
nanaimo	0.3.0
xcodeproj	1.19.0
rouge	2.0.7
xcpretty	0.3.0
terminal-notifier	2.0.0
unicode-display_width	1.7.0
terminal-table	1.8.0
public_suffix	4.0.6
addressable	2.7.0
multipart-post	2.0.0
word_wrap	1.0.0
tty-screen	0.8.1
tty-cursor	0.7.1
tty-spinner	0.9.3
artifactory	3.0.15
babosa	1.0.4
colored	1.2
highline	1.7.10
commander-fastlane	4.4.6
unf_ext	0.0.7.7
unf	0.1.4
domain_name	0.5.20190701
http-cookie	1.0.3
faraday-cookie_jar	0.0.7
faraday_middleware	1.0.0
gh_inspector	1.1.3
rubyzip	2.3.0
security	0.1.3
dotenv	2.7.6
naturally	2.2.0
simctl	1.6.8
jwt	2.2.2
uber	0.1.0
declarative	0.0.20
declarative-option	0.1.0
representable	3.0.4
retriable	3.1.2
mini_mime	1.0.2
multi_json	1.15.0
signet	0.14.0
memoist	0.16.2
os	1.1.1
googleauth	0.14.0
httpclient	2.8.3
google-api-client	0.38.0
emoji_regex	3.2.1
CFPropertyList	3.0.3
plist	3.6.0
excon	0.78.1
ruby2_keywords	0.0.2
faraday-net_http	1.0.0
faraday	1.3.0
fastimage	2.2.1
json	2.3.1
mini_magick	4.11.0
xcpretty-travis-formatter	1.0.1
bundler	2.2.4
rake	13.0.3
digest-crc	0.6.3
google-cloud-errors	1.0.1
google-cloud-env	1.4.0
google-cloud-core	1.5.0
google-cloud-storage	1.29.2
aws-eventstream	1.1.0
aws-sigv4	1.2.2
aws-partitions	1.415.0
jmespath	1.4.0
aws-sdk-core	3.110.0
aws-sdk-kms	1.40.0
aws-sdk-s3	1.87.0
forwardable	1.3.2
logger	1.4.3
date	2.0.0
stringio	0.0.2
zlib	1.0.0
ipaddr	1.2.2
openssl	2.1.2
ostruct	0.3.2
strscan	1.0.0
fileutils	1.5.0
io-console	0.4.7
libxml-ruby	3.1.0
rexml	3.2.4
psych	3.1.0
mutex_m	0.1.1
fastlane-plugin-teams	0.2.0

generated on: 2021-01-26

[max-ott]

It seems Apple is tinkering around with the build section. I think this might be the issue here.

[dylanmoo]

@miko1258 I'm encountering the same issue. The builds are uploading to TestFlight fine, but fastlane is hanging while waiting for the build to process.

I'm seeing this after changing the fastfile to use an api key with App Manager permissions.

[miko1258]

@max-ott, any update on this? Do we need to wait for some fix or we should use other authorization methods?

[max-ott]

Please try it both with Apple ID and ASC API key. The API key might be the issue.

[simonmaddox]

I'm seeing the same issue here with Apple ID authentication.

[Mrc527]

Same here, with Apple ID / Password authentication and even with the API Key.

My CI timeouts after one hour, and the package appears on the web console after a few minutes. But Fastlane does not recognise it.

[Mrc527]

Hello guys,

I had a similar experience, I think I've found the root cause. At least for me.
Point is, I'm publishing a version of my application which is NOT the latest. I mean, I've published version 5.0 by mistake a year ago, then I moved back to 1.5 instead.
But, if you open the "Builds" page, version 5.0 is recognised as the latest. Obviously. Therefore, to see my build you've to manually open the version 1.5 container, otherwise you don't see it.

I think Fastlane is relying on finding the build in the very first container, on the latest version. If this is not the case, the script fails to find the build, hanging up with the "Waiting for the build to show up in the build list - this may take a few minutes (check your email for processing issues if this continues)" message forever.

Unfortunately, there is no way to remove my version 5.0. Since I did not publish on the App Store yet (only on Test Flight) I managed to solve by removing and re-creating the app in the App Store. I'm pretty sure I could have solved by incrementing my version to 5.0 or greater as well.

Hope this helps.

[simonmaddox]

I'm publishing a version of my application which is NOT the latest

Same here. Well spotted.

[simonmaddox]

It looks like my issue might come from a change we mode to our version number recently:

Previously, the CFBundleShortVersionString value for one of our upcoming releases was 3.0. Later, we changed it to 3.0.0. TestFlight has a section in the build list for both versions, but puts all new builds into the 3.0 section rather than 3.0.0. I guess fastlane is looking in 3.0.0 and not finding anything, which is probably correct really.

Once the build starts processing, the 3.0.0 section disappears and the build ends up in the 3.0 section - so fastlane never finds it.

[miko1258]

This is exactly my case. We use version 9.9.9 for development. It shouldn't be uploaded on TestFlight but accidently I made a mistake in script and uploaded this version. When I upload version 1.4.0 it hangs on waiting stage.

[fastlane-bot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest fastlane version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with fastlane and feel free to tackle this issue yourself 💪

This issue will be auto-closed if there is no reply within 1 month.

[simonmaddox]

It looks like this pull request fixes this issue in 2.181.0:
#18547

Thanks @joshdholtz

[joshdholtz]

OMG yesssssss! This was suuuccchhh a weird issue 🤯 I had to actually watch somebody who had this behavior and look at some detailed logs in order to have any idea on what was going on 😛

Super super weird behavior but glad it's solved now! 💪

Happy fastlaning 🚀

[fastlane-bot]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest fastlane version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

Friendly reminder: contributions are always welcome! Check out CONTRIBUTING.md for more information on how to help with fastlane and feel free to tackle this issue yourself 💪

This issue will be auto-closed if there is no reply within 1 month.

[fastlane-bot]

This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem 👍

[masterial]

We have this issue. Fastlane sucks. 👎