Context provider NGSI v2 endpoint not returning data

Hi,
I'm following the Step-by-Step tutorial and trying out OpenWeatherMap API. I'm testing using docker. (I slightly changed the docker-compose.yml in the tutorial, but the architecture is the same)
However, I found for context-provide, the endpoint in the example "/random/weatherConditions" works fine. I tried other endpoints listed in the menu , such as "random/temperature", "/weather/number/cairo%2ceg/temp", and "/weather/weatherConditions", they all returned
{"error":"NotFound","description":"The entity does not have such an attribute"} in my curl client.
If I checked the logs of orion and context provider. I can see that for "/weather/weatherConditions", there's an issue with OpenWeatherMap API
fiware-tutorial | POST /weather/weatherConditions/op/query 400 883.080 ms - 1319 orion_1        | INFO@16:20:36  httpRequestSend.cpp[619]: Notification Successfully Sent to http://host.docker.internal:3000/weather/weatherConditions/op/query orion_1        | WARN@16:20:36  httpRequestSend.cpp[632]: Notification response NOT OK, http code: 400
However, for "random/temperature" or "/weather/number/cairo%2ceg/temp", the logs show that the query operarion goes well. However the response in my curl client is still {"error":"NotFound","description":"The entity does not have such an attribute"}...The logs are below
orion_1        | INFO@16:20:35  logMsg.h[1844]: Starting transaction to http://host.docker.internal:3000/random/temperature/op/query orion_1        | INFO@16:20:35  httpRequestSend.cpp[599]: Sending message 55 to HTTP server: sending message of 310 bytes to HTTP server fiware-tutorial | POST /random/temperature/op/query 200 0.899 ms - 34 orion_1        | INFO@16:20:35  httpRequestSend.cpp[619]: Notification Successfully Sent to http://host.docker.internal:3000/random/temperature/op/query orion_1        | INFO@16:20:35  httpRequestSend.cpp[628]: Notification response OK, http code: 200
Since I only change part of the provider url... so I don't know if it's an issue with the context provider or with my settings.
Thanks so much for helping in advance!!!!

This was a bug, introduced during the restructuring when NGSI-LD support was added.  I have since corrected the NGSI v2 Query String parameter for the Weather proxy. Please obtain the latest docker images using .services create and re-try.
Fixed: ef9c08b


New version: LoopManagers v0.1.4

Registering package: LoopManagers
Repository: https://github.com/ClimFlows/LoopManagers.jl
Created by: @dubosipsl
Version: v0.1.4
Commit: 15bbb2565606efd6db8913ac49b2b254b61369c5
Reviewed by: @dubosipsl
Reference: https://github.com/ClimFlows/LoopManagers.jl/commit/15bbb2565606efd6db8913ac49b2b254b61369c5#commitcomment-142926768
Description: LoopManagers is the companion package of ManagedLoops. It provides managers to execute loops with SIMD, on multiple threads or on GPUs.
Release notes:

* measure multithread performance when testing

The correct version number was v0.1.3, which has now been registered by another PR, #108541. Please close this PR.


Feature request: debugging inside test runners

First, thanks for building such a great tool! Puppeteer is making end-to-end tests fun to write without all the flakiness of traditional e2e tests.
The debugging options are awesome:
const browser = await puppeteer.launch({
  headless: false,
  slowMo: 250 // slow down by 250ms
})

However, Chrome isn't launched when this code is inside of a test runner; for example, with Jest:
import puppeteer from 'puppeteer'

const appUrlBase = 'http://localhost:4000'

let browser
let page

beforeAll(async () => {
  const options = process.env.NODE_ENV === 'testDebug'
    ? {
        headless: false,
        slowMo: 250 // slow down by 250ms
      }
    : {}
  browser = await puppeteer.launch(options)
  page = await browser.newPage()
})

test('user sees browser title', async () => {
  await page.goto(appUrlBase)
  const browserTitle = await page.title()
  expect(browserTitle).toBe('ropig')
})

test('user is redirected to login when logged out on private routes', async () => {
  await page.goto(appUrlBase)
  await page.waitForSelector('[data-testId="userLoginForm"]')
})

afterAll(async () => {
  browser.close()
})

Right now I'm using page.plainText() to debug output, but having the non-headless and slowMo options would be fantastic if possible. Thank you.

Does this code throw an error, or just not work? Or it works but you want it baked into Puppeteer?
Assuming Chrome isn't working, can you add dumpio: true to the options and see if there is anything useful in its output? Thanks!

@JoelEinbinder It wasn't working and a dumpio: true didn't have any useful output so I tried wiping and reinstalling node_modules and that did the trick: it is working now. So this doesn't seem to be a problem in Puppeteer, sorry for the issue. Closing now.


Stuck in Installing pip dependencies /   for more than 18 hours

Stuck in Installing pip dependencies /   for more than 18 hours，can you install your environment through environment.yaml successfully？

Please try to remove the cudatoolkit=11.3 dependency from environment.yaml. Or install the environment seperately.
pip3 install torch==1.12.1+cu113 torchvision==0.13.1+cu113 --extra-index-url https://download.pytorch.org/whl/cu113


Allow integration tests to run on Windows

any subprocess needs to be killed since SIGINT is not a thing on
Windows
ensure blackboxRunner.Stop() is called at the end of every test
close logfile before renaming (this is the only way files can be
renamed on Windows)
in the "tails files when server takes a long time to start" test, use
separate buffers to ensure each server receives the expected data
when the test TCPSyslogServer is signalled, close the underlying TCP
connection and ignore the resulting io.Copy error

closing since I don't have my pivotal.io email address linked to my github account


Buildscript improvements

This fixes a few issues I've encountered in the build scripts. Please see the individual commits.

link.sh should report an error if the prerequisites are missing (elfshaker/manyclangs#5).
Remove the filter_dupes hack and use --start-lib and --end-lib which does the same thing but better, providing binaries which should be equivalent to those you'd get if you had build the archives.
Fix a bug where comm and jq could diverge.
Other minor cleanups.

There may yet be more to follow but I am happy with this as a start.


Routes and source

Closes #1116

Coverage decreased (-0.4%) to 81.803% when pulling ce1b4ff78247b856b4383405492ed41e67f6b5b7 on na3d:routes-and-source into b3eb2801fb49b86a4b8942b5133ed301a6176023 on linode:master.

Coverage decreased (-0.4%) to 81.795% when pulling 5a8f0d6e49ce9ea9ed7cd130a2cbffc0b962ccaf on na3d:routes-and-source into b3eb2801fb49b86a4b8942b5133ed301a6176023 on linode:master.

Looks good.


docs: add keyrings.artifacts to the list of project built with pixi

This PR add my project jslorrma/keyrings.artifacts to Community.md.
See https://github.com/prefix-dev/pixi/issues/1857#issuecomment-2307470213

Thank you 🙏

Thank you 😊


compute-mfccs-feats

Thanks for sharing your code! I'm trying to get it to run and would appreciate any help!
I run:  python diarization.py -c ../configs/vbdiar.yml -l lists/list_spk.scp --audio-dir wav/fisher-english-p1 --vad-dir vad/fisher-english-p1 -m diarization
And get: ValueError: /Users/admin/kaldi/src/featbin/compute-mfcc-feats binary returned error code None.
So I'm using the wavfiles and scp that's included in the github repo.
I've tried extracting the .gz files in /vad/fisher-english-p1,
and I've tried downsampling the wav files from 16 to 8 kHz but neither helped.
Any Idea what I'm doing wrong?
Full output below:
/Users/admin/miniconda3/lib/python3.7/site-packages/sklearn/externals/joblib/init.py:15: DeprecationWarning: sklearn.externals.joblib is deprecated in 0.21 and will be removed in 0.23. Please import this functionality directly from joblib, which can be installed with: pip install joblib. If this warning is raised when loading pickled models, you may need to re-serialize those models with scikit-learn 0.21+.
warnings.warn(msg, category=DeprecationWarning)
2019-07-29 23:48:37,730 - main - INFO - Running diarization.py -c ../configs/vbdiar.yml -l lists/list_spk.scp --audio-dir wav/fisher-english-p1 --vad-dir vad/fisher-english-p1 -m diarization.
2019-07-29 23:48:37,732 - main - WARNING - Failed to import libmkl_rt.so, it will not be possible to use mkl backend.
/Users/admin/miniconda3/lib/python3.7/site-packages/vbdiar/utils/utils.py:428: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the default Loader is unsafe. Please read https://msg.pyyaml.org/load for full details.
return yaml.load(ymlfile)
2019-07-29 23:48:37,862 - main - INFO - Processing file fisher-english-p1/fe_03_00001-a.
2019-07-29 23:48:37,867 - vbdiar.kaldi.mfcc_features_extraction - INFO - Extracting MFCC features from /Users/admin/Dropbox/sr/wavread/VBDiarization/VBDiarization/examples/wav/fisher-english-p1/fisher-english-p1/fe_03_00001-a.wav.
Traceback (most recent call last):
File "diarization.py", line 266, in
n_jobs=1)
File "diarization.py", line 78, in process_files
ret = _process_files((fns, kwargs))
File "diarization.py", line 48, in _process_files
ret.append(process_file(file_name=fn, **kwargs))
File "diarization.py", line 116, in process_file
features = features_extractor.audio2features(os.path.join(wav_dir, f'{file_name}{wav_suffix}'))
File "/Users/admin/miniconda3/lib/python3.7/site-packages/vbdiar/kaldi/mfcc_features_extraction.py", line 90, in audio2features
raise ValueError(f'{self.compute_mfcc_feats_bin} binary returned error code '
ValueError: /Users/admin/kaldi/src/featbin/compute-mfcc-feats binary returned error code None.
b'/Users/admin/kaldi/src/featbin/apply-cmvn-sliding --norm-vars=false --center=true --cmn-window=300 ark:- ark:/var/folders/9t/nb4clh4907j8gb5bsdbp0gdh0000gp/T/tmpuaw5ixfc \nLOG (apply-cmvn-sliding[5.5.433~1-7637d]:main():apply-cmvn-sliding.cc:75) Applied sliding-window cepstral mean normalization to 0 utterances, 0 had errors.\n'

Hi,
can you post here your mfcc kaldi config? Sample rate in config must match the sample rate of audios.
Can you please also run soxi on one of the example audios?
If none of this helps, try to run kaldi command from the command line (this python code is basically just a wrapper for kaldi).

Thanks for the quick response! I'm using the included "mfcc.config" referenced from "vbdiar.yml"
vbdiar.yml:
MFCC:
config_path: ../configs/mfcc.conf
apply_cmvn_sliding: True
norm_vars: False
center: True
cmn_window: 300
mfcc.config:
--sample-frequency=16000
--frame-length=25 # the default is 25
--low-freq=20 # the default.
--high-freq=7700 # the default is zero meaning use the Nyquist (4k in this case).
--num-ceps=23 # higher than the default which is 12.
--snip-edges=false
And soxi gives me:
Input File     : '/Users/admin/Dropbox/sr/wavread/VBDiarization/VBDiarization/examples/wav/fisher-english-p1/fe_03_00001-a.wav'
Channels       : 1
Sample Rate    : 16000
Precision      : 16-bit
Duration       : 00:00:07.00 = 112000 samples ~ 525 CDDA sectors
File Size      : 224k
Bit Rate       : 256k
Sample Encoding: 16-bit Signed Integer PCM
I will try to run kaldi from command line!

configs and also audio format looks fine, try to print and run command directly from command line

Hi,
I meet the same problem as @jadujoel ,and I am not sure the command I used is right or not.
python diarization.py -l lists/AMI_dev-eval.scp -c ../configs/vbdiar.yml -m diarization --audio-dir ./wav/4133/ --vad-dir vad_dir
What files should I put in the vad-dir?
My aim is to diarize a phone record.
I'm trying to get it to run and would appreciate any help!

Hi, I was able to replicate the issue, I am gonna fix that.

Thanks for the quick response!And I would like to konw the performance of speaker diarization in this project.

Problem should be fixed. Performance of diarization is shown in README on AMI.
@jadujoel please let me know if it fixed the problem so I can close the issue. I fixed also run.sh script in examples directory, so you can run directly that one.

I will try as soon as possible.Thanks for the your response!

I have update the examples/diarization.py and the run.sh, and I get a error like this(and how to generate embeddings or what should be put in the --in-emb-dir ):
Traceback (most recent call last):
File "diarization.py", line 258, in
raise ValueError('At least one of --in-emb-dir or --out-emb-dir must be specified.')
ValueError: At least one of --in-emb-dir or --out-emb-dir must be specified.

You should run run.sh script.

Yes, I use command  'sh run.sh', and it shows the error.

Wonderful it works now after pulling your update, thanks!
I needed to make a folder (i called it "embout") in examples dir, then added " --out-emb-dir embout " to run.sh and after that all good!

Also i added diarization.py at line 152
    from sys import platform
    if platform == "darwin":
        mkl_rt = ctypes.CDLL('libmkl_rt.dylib')
    else:
        mkl_rt = ctypes.CDLL('libmkl_rt.so')

@jadujoel I forgot to fix --out-emb-dir parameter in run.sh, now it should be fine
mkl_rt = ctypes.CDLL('libmkl_rt.dylib')
``` is it MAC specific?

well when you install the mkl library either directly from intel, or from pip: no .so files are created on my mac atleast, but the .dylib file with the same name seems to do the same thing so my guess is its the same thing different extension.

in the end, MKL should not be needed at all, so I will try to remove this code in the future
closing the issue

Hi, Running into same error, but trying with different file. Could you help?
This is the error I got:
Traceback (most recent call last):
File "diarization.py", line 268, in
n_jobs=1)
File "diarization.py", line 78, in process_files
ret = _process_files((fns, kwargs))
File "diarization.py", line 48, in _process_files
ret.append(process_file(file_name=fn, **kwargs))
File "diarization.py", line 116, in process_file
features = features_extractor.audio2features(os.path.join(wav_dir, f'{file_name}{wav_suffix}'))
File "/anaconda3/envs/convy/lib/python3.6/site-packages/vbdiar/kaldi/mfcc_features_extraction.py", line 90, in audio2features
raise ValueError(f'{self.compute_mfcc_feats_bin} binary returned error code '
ValueError: /Documents/Sajal/Convy/kaldi/src/featbin/compute-mfcc-feats binary returned error code None.
b'/Documents/Sajal/Convy/kaldi/src/featbin/apply-cmvn-sliding --norm-vars=false --center=true --cmn-window=300 ark:- ark:/tmp/tmpxa447z2z \nLOG (apply-cmvn-sliding[5.5]:main():apply-cmvn-sliding.cc:75) Applied sliding-window cepstral mean normalization to 0 utterances, 0 had errors.\n'

Hi, I have the same issue  "ValueError: /Users/admin/kaldi/src/featbin/compute-mfcc-feats binary returned error code None." with the current version. Tried to run run.sh directly and also tried using my own data. In both cases, I got the same value error.

This exact issue has been reproduced now again. @Jamiroquai88 would you please let us know what can we do about this?


Stop browser from navigating away while editing/creating a post

Context
If you press the back button or click on a tab/link while editing a post, you navigate away without warning and lose all your progress. This is compounded by the fact that automatic drafts haven't been implemented yet.
Ideal behavior
If editing/creating a post, there should be an error window if you navigate away.

Things to consider
Consider all browsers
Anywhere else this behavior should be implemented?

I hacked this together with some JavaScript. The window pops up whenever you try to navigate away from the edit post page.
It isn't 'smart' because it will still warn you even if you haven't typed anything. Since I am the only one using this UI, it works for me!
See -> https://github.com/jsolly/blogthedata/commit/7028b487339e7795be47a9bc2b6d86fd25df1aa2


Cannot Install digs

Hi. I find a problem when installing cargo installs errors here:
  Compiling thiserror-impl v1.0.30
   Compiling enum-as-inner v0.3.3
   Compiling clap_derive v3.0.0-beta.5
   Compiling thiserror v1.0.30
   Compiling trust-dns-proto v0.20.3
   Compiling clap v3.0.0-beta.5
error[E0658]: arbitrary expressions in key-value attributes are unstable
 --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/clap-3.0.0-beta.5/src/lib.rs:8:10
  |
8 | #![doc = include_str!("../README.md")]
  |          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  |
  = note: see issue #78835 <https://github.com/rust-lang/rust/issues/78835> for more information

error: aborting due to previous error

For more information about this error, try `rustc --explain E0658`.
error: could not compile `clap`

To learn more, run the command again with --verbose.
warning: build failed, waiting for other jobs to finish...
error: failed to compile `digs v0.1.6 (/home/n00b/Documents/Tools/digs)`, intermediate artifacts can be found at `/home/n00b/Documents/Tools/digs/target`

Caused by:
  build failed
n00b@n00b:~/Documents/Tools/digs$
n00b@n00b:~/Documents/Tools/digs$ rustc -V
rustc 1.53.0
n00b@n00b:~/Documents/Tools/digs$

If you use binary so far there is no problem.
n00b@n00b:~/Documents/Tools$ ./digs-linux-amd64 belajarlinux.id A -f config.toml
Google
  A belajarlinux.id. <IP_ADDRESS>
Quad9
  A belajarlinux.id. <IP_ADDRESS>
Cloudflare
  A belajarlinux.id. <IP_ADDRESS>
n00b@n00b:~/Documents/Tools$

Thank you.

Hi.
Thanks for the report.
The root cause was the unstable API of Clap v3 beta. This is expected though. So we move back to the stable version of v2.
It is fixed here: https://github.com/BiznetGIO/digs/commit/f79b2c386f00c35311988a4464c4f7cb87fc5b1a
Please run cargo install digs again then report any error here.

Hi Problem solved,

Thank you.


[RFE] CLI

Lets build a CLI wrapper around fmatch  to allow the user to pass specific tests they want to capture historical data about.
Below is just a example of some input I could envision.
---
tests :
  - name : aws-small-scale-cluster-density-v2
    platform: aws
    masterSize: m6a.xlarge
    workerSize: m6a.xlarge
    <all other meta>
    metrics :
    - metric : podReadyLatency
      metricType : latency

    - metric : apiserverCPU
      metricType : cpu
      namespace: openshift-kube-apiserver

    - metric: ovnCPU
      metricType: cpu
      namespace: openshift-ovn-kubernetes

Moving to Orion


dead links

Build a containerized web application with Docker -pages has dead links:
for example: https://docs.microsoft.com/en-us/Azure/containers/1-introduction

@miktuo thanks for reporting this issue. Could you provide link to the topic where you are seeing the broken link

It was all the subpages in this address:
https://docs.microsoft.com/en-us/learn/paths/administer-containers-in-azure/
But, now they seem to be fixed, they were giving error about week in time before today.
From: Sudeep Kumar<EMAIL_ADDRESS>Sent: keskiviikko 29. toukokuuta 2019 1:47
To: MicrosoftDocs/feedback<EMAIL_ADDRESS>Cc: Mikko Tuomela<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/feedback] dead links (#1550)
@miktuohttps://github.com/miktuo thanks for reporting this issue. Could you provide link to the topic where you are seeing the broken link
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/feedback/issues/1550?email_source=notifications&email_token=AMFVRXF2IMLIBRPKNWRLNA3PXWY45A5CNFSM4HPZPUK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWNVAJA#issuecomment-496717860, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMFVRXHJVLLMF2VZABZ5KITPXWY45ANCNFSM4HPZPUKQ.


NTR: regulation of oxytocin secretion

Please provide as much information as you can:

regulation of oxytocin secretion

Definition (free text) Any process that modulates the rate, frequency, or extent of the regulated release of a oxytocin.

Reference, in format PMID:25096581

Parent term(s)
GO:0036162 oxytocin secretion

Children terms (if applicable) Should any existing terms that should be moved underneath this new proposed term?
positive regulation of oxytocin secretion

Synonyms (please specify, EXACT, BROAD, NARROW or RELATED)

Cross-references

For enzymes, please provide RHEA and/or EC numbers.

Can also provide MetaCyc, KEGG, Wikipedia, and other links.

Any other information

need to have the regulation terms in line with the other hormone secretion terms

Hi @RLovering
Should we treat this like the cytokines and use 'regulation of production' instead?
Thanks, Pascale

Note that     GO:0036162  oxytocin secretion has no reference and no annotations.

yes please do change to 'regulation of  oxytocin production' and create the positive regulation of oxytocin production term too
Many thanks
Ruth

+[Term]
+id: GO:0140667
+name: regulation of oxytocin production
+namespace: biological_process
+def: "Any process that modulates the frequency, rate, or extent of production of oxytocin." [PMID:25096581]
+intersection_of: GO:0065007 ! biological regulation
+intersection_of: regulates GO:0036162 ! oxytocin production
+property_value: term_tracker_item https://github.com/geneontology/go-ontology/issues/21535 xsd:anyURI
+created_by: pg
+creation_date: 2021-06-24T11:28:07Z
+
+[Term]
+id: GO:0140668
+name: positive regulation of oxytocin production
+namespace: biological_process
+def: "Any process that activates or increases the frequency, rate or extent of production of oxytocin." [PMID:25096581]
+intersection_of: GO:0065007 ! biological regulation
+intersection_of: positively_regulates GO:0036162 ! oxytocin production
+property_value: term_tracker_item https://github.com/geneontology/go-ontology/issues/21535 xsd:anyURI
+created_by: pg
+creation_date: 2021-06-24T11:31:26Z
+
+[Term]
+id: GO:0140669
+name: negative regulation of oxytocin production
+namespace: biological_process
+def: "Any process that stops, prevents, or reduces the rate of production of oxytocin." [PMID:25096581]
+intersection_of: GO:0065007 ! biological regulation
+intersection_of: negatively_regulates GO:0036162 ! oxytocin production
+property_value: term_tracker_item https://github.com/geneontology/go-ontology/issues/21535 xsd:anyURI
+created_by: pg
+creation_date: 2021-06-24T11:31:45Z
+

Plus changed oxytocin secretion to oxytocin production (term label + defs)


NSFW checks iOS

When trying to change the NSFW setting, the dApp crashes.

@aliseyalvi this could be a clue to solving the issue...


Responsive featured images

I have done this with my own site and it works perfectly.
It allows you to put a featured image into the single pages and load it responsively, this might be a good way to do things, but I think it could be expanded to the options page to allow for users to select where they want their featured image to be loaded on the single page.
This was inspired by this post: http://isabelcastillo.com/featured-image-accelerated-mobile

This code no longer works, however it is still needed after 0.8, will be changing later to make it work with the new update.


Result of search operation on resources filtering by date does not match the actual state.

GOAL: To perform search operation on recently created resources filtering by date.
ISSUE: The right amount of resources does not match the actual state.
REQUEST WE ARE SENDING:
http://localhost:8080/fhir/Encounter?_filter=(pldate ge 2019-06-16T22%3A00%3A10.528%2B02%3A00 and pldate le 2021-06-16T22%3A00%3A10.528%2B02%3A00)
DIAGNOSIS:

Reloading profiles, value sets, code systems, search parameters and performing a search operation solves the problem until the next resource is created and we try to perform search operation on it using the same request.
Performing READ by resource id (READ/id) confirms that resource is present in database.
According to the documentation:

https://hapifhir.io/hapi-fhir/docs/server_jpa/configuration.html#search-result-caching
we confirmed that:

HTTP header : Cache-Control: no-cache doesn`t work.
HTTP header : Cache-Control: no-store, max-results=20 doesn`t work.
set on our DAO : myDaoConfig.setReuseCachedSearchResultsForMillis(null); doesn`t work.

EXPECTED BEHAVIOR:
After performing search operation amount of resources matches the actual state.
Environment:

HAPI FHIR 4.1.0-e05ea676
OS: WIN10
Browser FIREFOX 77.0.1 (64 bit) /Postman/REST

Search param pldate definition:
<?xml version="1.0" encoding="UTF-8"?>
<SearchParameter xmlns="http://hl7.org/fhir">
    <id value="xxx"/>
    <text><status value="generated"/>
Search
</text>
    <url value="https://ezdrowie.gov.pl/fhir/SearchParameter/xxx"/>
    <name value="Encounter by author Search Parameter"/>
    <status value="active"/>
    <experimental value="true"/>
    <date value="2019-08-01"/>
    <description value="Search by Encounter"/>
    <purpose value="Need to search Encounter"/>

    <base value="Encounter"/>
    <type value="string"/>
    <expression value="Encounter.meta.lastUpdated" />
    <xpathUsage value="normal"/>
</SearchParameter>


Thanks Micheal! I intended to write ^2, but it looks like I wrote a strict 2.


Avoid robot backtracking when a RobotCommandHandle::follow_new_path() is triggered

rmf_fleet_adapter uses rxcpp for reactively generating a new plan for the robot on a number of occasions including during traffic negotiation and when itinerary delays accumulate past a threshold. As a response, the RobotCommandHandle::follow_new_path() may be triggered to instruct the robot to follow the updated itinerary. However, between the time of the interruption and when the implementation of follow_new_path() sends an instruction to the robot, the robot would have continued moving along its previous path. As a result when the robot follows the new set of waypoints, it "backtracks", ie moves to the first position in the path which is slightly behind the robots current position, before continuing along the remaining path. Presently the workaround for this is to perform some filtering in the waypoints received.
Using this ticket to discuss potential solutions for this problem.
One easy solution would be to request the robot to stop immediately whenever the interrupt is triggered. The RobotUpdateHandle could accept a callback from users that would get their robots to stop when triggered. However, this is a big change in the behavior as I think one of the goals with the current implementation is to have the robots continue along their plans while the negotiations occur.
Another possible approach is to have the planner perform some kind of trajectory tuning/optimization based on the kinematics of the fleet.
Looking for feedback on these ideas along with other suggestions.

I think post-processing of the plan based on the latest robot state is the best approach. We would compare the plan's expectations to our knowledge of the latest physical reality of the robot and just prune some waypoints off the front of the trajectory if the robot has already passed them.
One difficulty with this is identifying cases where the robot does need to backtrack, e.g. to escape a conflict with another robot. In those cases, pruning the start of the plan would lead to a deadlock. This issue has been the primary blocker that's prevented us from taking action on this problem.
I think when we have the event-driven traffic system that can recognize the purpose behind each wait, we can leverage the event expectation system to identify when the robot needs to backtrack versus when it's safe to prune the front of the trajectory.

Thanks for the valuable insights @mxgrey. Could we look at the time property of the first waypoint in the new path to determinate whether the intention is to wait at the previous location? Maybe check if the if the wait duration is above a certain threshold? I assume if the robot is not meant to wait, the first waypoint in the new path will have time very close to now?

Looking at time alone would not be reliable since it's possible that the plan was generated some time in the past and needs your robot to back off to let another robot pass. If you ignore the initial waypoints because they were targeting "some time ago" then you might continue to block the path of the other robot (while it most likely also blocks yours), leaving both in a deadlock.
Granted, if planning and negotiation works fast enough then the problem that I described shouldn't happen, but I don't think critical systems should rely on an assumption about how fast any sub-process will manage to run.

Closed by https://github.com/open-rmf/rmf_ros2/pull/167

Thanks for that insight! The tricky part previously with interpolation has been the estimation of the distance the robot travelled in the time duration between a replan interrupt and the when the fleet adapter submits a navigation request to the robot. And depending on the goal tolerance of the robot's navigation stack, the robot may or may not backtrack depending on how far it is from the interrupt location.
But with the new system, its great to know that we can ignore the waypoints that fall behind the robot 👍🏼


Add tracing for federated targets API

Describe the solution you'd like

Instrument tracing spans for the federated APIs. This should include the proxy (querier) side as well as the leaf store sides.

Hi!
I can take a look on this topic and try to help 👍

Thanks @ebarped, please go ahead.


Unexpected Error

Unexpected Error
Unexpected errors detected. We're sorry for
the inconvenience.
Would you like to send the following error
logs to Fuel Wallet team?
"error:[
e":t,
"name": "AbortError",
"message": "TimeoutError Transaction timed out
due to inactivity:
"inner":
"reactError":
"timestamp":<PHONE_NUMBER>406,
"id": "06f266b0-a890-46ec-a816-
47d271802dca"
"error":/
Send reports
Ignore

Compared to when I first used fuel wallet, it's better now. GOOD WORK GUYS. Its very commendable

This is the repository for Sway. For wallet related issues you want https://github.com/FuelLabs/fuels-wallet


Multiple capture crashes the Application

Whenever i am taking the image from gallery or from camera multiple times App crashes due to increased memory of the App. How to do clean up in case of Android? is there a way to do it?
Whenever i am selecting some images from gallery then one copy was there in this below path-
content://com.android.providers.downloads.documents/document/1144
Please suggest me how to remove this one from android.

Are these two different questions or problems? If so, please create a second issue so those can be handled separately.

As per my understanding both are interlinked . because of memory increase app got crashed.

Ok, then I just don't understand your issue.

How to do clean up in case of Android?

What do you want to clean up?

Whenever i am selecting some images from gallery then one copy was there in this below path-

What does that mean?

Please suggest me how to remove this one from android.

Remove what from Android?

Okay let me explain again.

suppose i have selected some image from gallery.
So in network tab i can see the url of blob file and jpg file both such as

blob:file:///1e6c0487-a0f4-4ae2-bed1-44a620a0ecdb
content://com.android.providers.downloads.documents/document/1144

So after the completion of uploading process i want to remove these two file from my app temporary folder.

Where is the connection to your Android app crashing here?

If i am doing those process explained above multiple times then Android app is crashing.

When user add document image to preview from camera or gallery, then storage increase, and it does not get cleared up on cancelling the preview or uploading the document successfully. If user adds image to preview and cancel it- Repeat 5 times, then storage keeps on increasing and finally crashing.

Yes, that I got. But does it have to do with your question in https://github.com/apache/cordova-plugin-camera/issues/374#issuecomment-439011146?

yes due to multiple capture these crash things are happening.

I got that. But does this have to do with your question on how to remove some files?

stale


upload_to_testflight(distribute_only:true) stuck on "Waiting for the build to show up in the build list"

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
In my Fastfile, I'm executing upload_to_testflight() with the option distribute_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 the distribute_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.

  desc "Upload to TestFlight"
  lane :beta do |options|
    edit_file(file: "../testflight/what_to_test.txt")
    beta_app_review_info = {
      contact_email: File.read("../testflight/contact_email_address.txt").strip,
      contact_first_name: File.read("../testflight/contact_first_name.txt").strip,
      contact_last_name: File.read("../testflight/contact_last_name.txt").strip,
      contact_phone: File.read("../testflight/contact_phone_number.txt").strip,
      demo_account_name: File.read("../testflight/demo_user.txt").strip,
      demo_account_password: File.read("../testflight/demo_password.txt").strip,
      notes: File.read("../testflight/review_notes.txt").strip,
    }
    localized_build_info = {
      default: {
        whats_new: File.read("../testflight/what_to_test.txt").strip,
      },
    }
    distribute_external = options.fetch(:distribute_external, true);
    groups = nil
    if distribute_external
      external_group =  File.read("../testflight/internal/external_testers_group.txt").strip
      groups = [external_group]
    end
distribute_only = options.fetch(:distribute_only, false);

if !distribute_only && !options[:skip_xcarchive]
  ipa_from_xcarchive
end

if !distribute_only && !options[:skip_resign]
  resign_ipa(options)
end

upload_to_testflight(
  beta_app_review_info: beta_app_review_info,
  localized_build_info: localized_build_info,
  distribute_external: distribute_external,
  distribute_only: distribute_only,
  build_number: options[:build_number],
  groups: groups,
)

end

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.

$ fastlane beta distribute_only:true --verbose
[✔] 🚀
[18:02:28]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
DEBUG [2021-04-26 18:02:29.15]: Checking if there are any plugins that should be loaded...
Successfully loaded Appfile at path '/XXX/ios/fastlane/Appfile'
- app_identifier: 'xxx.xxxx.xxxxx'
-------
Successfully loaded Appfile at path '/XXX/ios/fastlane/Appfile'
- app_identifier: 'xxx.xxxx.xxxxx'
-------
DEBUG [2021-04-26 18:02:29.32]: Using distribute_only: true
Successfully loaded Appfile at path '/XXX/ios/fastlane/Appfile'
- app_identifier: 'xxx.xxxx.xxxxx'
-------
Successfully loaded Appfile at path '/XXX/ios/fastlane/Appfile'
- app_identifier: 'xxx.xxxx.xxxxx'
-------
INFO [2021-04-26 18:02:29.33]: ---------------------
INFO [2021-04-26 18:02:29.33]: --- Step: team_id ---
INFO [2021-04-26 18:02:29.33]: ---------------------
INFO [2021-04-26 18:02:29.33]: Setting Team ID to 'XXXXXXXXX' for all build steps
Successfully loaded Appfile at path '/XXX/ios/fastlane/Appfile'
- app_identifier: 'xxx.xxxx.xxxxx'
-------
INFO [2021-04-26 18:02:29.33]: ------------------------------
INFO [2021-04-26 18:02:29.33]: --- Step: default_platform ---
INFO [2021-04-26 18:02:29.33]: ------------------------------
Successfully loaded Appfile at path '/XXX/ios/fastlane/Appfile'
- app_identifier: 'xxx.xxxx.xxxxx'
-------
Successfully loaded Appfile at path '/XXX/ios/fastlane/Appfile'
- app_identifier: 'xxx.xxxx.xxxxx'
-------
INFO [2021-04-26 18:02:29.34]: Driving the lane 'ios beta' 🚀
INFO [2021-04-26 18:02:29.34]: ------------------------------------------
INFO [2021-04-26 18:02:29.34]: --- Step: Switch to ios edit_file lane ---
INFO [2021-04-26 18:02:29.34]: ------------------------------------------
INFO [2021-04-26 18:02:29.34]: Cruising over to lane 'ios edit_file' 🚖
INFO [2021-04-26 18:02:32.20]: Cruising back to lane 'ios beta' 🚘
Successfully loaded Appfile at path '/XXX/ios/fastlane/Appfile'
- app_identifier: 'xxx.xxxx.xxxxx'
-------
Successfully loaded Appfile at path '/XXX/ios/fastlane/Appfile'
- app_identifier: 'xxx.xxxx.xxxxx'
-------
Successfully loaded Appfile at path '/XXX/ios/fastlane/Appfile'
- app_identifier: 'xxx.xxxx.xxxxx'
-------
Successfully loaded Appfile at path '/XXX/ios/fastlane/Appfile'
- app_identifier: 'xxx.xxxx.xxxxx'
-------
Successfully loaded Appfile at path '/XXX/ios/fastlane/Appfile'
- app_identifier: 'xxx.xxxx.xxxxx'
-------
Successfully loaded Appfile at path '/XXX/ios/fastlane/Appfile'
- app_identifier: 'xxx.xxxx.xxxxx'
-------
Successfully loaded Appfile at path '/XXX/ios/fastlane/Appfile'
- app_identifier: 'xxx.xxxx.xxxxx'
-------
Successfully loaded Appfile at path '/XXX/ios/fastlane/Appfile'
- app_identifier: 'xxx.xxxx.xxxxx'
-------
Successfully loaded Appfile at path '/XXX/ios/fastlane/Appfile'
- app_identifier: 'xxx.xxxx.xxxxx'
-------
Successfully loaded Appfile at path '/XXX/ios/fastlane/Appfile'
- app_identifier: 'xxx.xxxx.xxxxx'
-------
Successfully loaded Appfile at path '/XXX/ios/fastlane/Appfile'
- app_identifier: 'xxx.xxxx.xxxxx'
-------
Successfully loaded Appfile at path '/XXX/ios/fastlane/Appfile'
- app_identifier: 'xxx.xxxx.xxxxx'
-------
INFO [2021-04-26 18:02:32.32]: ----------------------------------
INFO [2021-04-26 18:02:32.32]: --- Step: upload_to_testflight ---
INFO [2021-04-26 18:02:32.32]: ----------------------------------
INFO [2021-04-26 18:02:32.32]: 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 name XXXXXXX
Looking for App Store Connect Team with ID XXXXX
INFO [2021-04-26 18:02:33.40]: Login successful
DEBUG [2021-04-26 18:02:33.40]: App Platform (ios)
DEBUG [2021-04-26 18:02:33.40]: App identifier (xxx.xxxx.xxxxx)
INFO [2021-04-26 18:02:36.25]: Waiting for processing on... app_id: XXXXXXX, app_version: , build_version: , platform: IOS
WARN [2021-04-26 18:02:36.25]: Read more information on why this build isn't showing up yet - https://github.com/fastlane/fastlane/issues/14997
INFO [2021-04-26 18:02:36.25]: 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)
INFO [2021-04-26 18:03:06.25]: 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)
^CWARN [2021-04-26 18:03:09.84]: Lane Context:
INFO [2021-04-26 18:03:09.84]: {:DEFAULT_PLATFORM=>:ios, :PLATFORM_NAME=>:ios, :LANE_NAME=>"ios beta"}
INFO [2021-04-26 18:03:09.84]: Successfully generated documentation at path '/XXX/ios/fastlane/README.md'
+------+----------------------+-------------+
|             fastlane summary              |
+------+----------------------+-------------+
| Step | Action               | Time (in s) |
+------+----------------------+-------------+
| 1    | team_id              | 0           |
| 2    | default_platform     | 0           |
| 3    | Switch to ios        | 0           |
|      | edit_file lane       |             |
| 4    | upload_to_testflight | 37          |
+------+----------------------+-------------+
ERROR [2021-04-26 18:03:09.85]: fastlane finished with errors
Traceback (most recent call last):
31: from /usr/local/bin/fastlane:23:in <main>' 	30: from /usr/local/bin/fastlane:23:in load'
29: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/bin/fastlane:23:in <top (required)>' 	28: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/cli_tools_distributor.rb:122:in take_off'
27: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/commands_generator.rb:41:in start' 	26: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/commands_generator.rb:352:in run'
25: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in run!' 	24: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in run!'
23: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in run_active_command' 	22: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in run'
21: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in call' 	20: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/commands_generator.rb:108:in block (2 levels) in run'
19: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/command_line_handler.rb:36:in handle' 	18: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/lane_manager.rb:47:in cruise_lane'
17: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/runner.rb:45:in execute' 	16: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/runner.rb:45:in chdir'
15: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/runner.rb:49:in block in execute' 	14: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/lane.rb:33:in call'
13: from ../../../../ios-support/iOS.Fastfile:200:in block (2 levels) in parsing_binding' 	12: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/fast_file.rb:159:in method_missing'
11: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/runner.rb:157:in trigger_action_by_name' 	10: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/runner.rb:229:in execute_action'
9: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/runner.rb:229:in chdir' 	 8: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/runner.rb:255:in block in execute_action'
7: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/actions/actions_helper.rb:69:in execute_action' 	 6: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/runner.rb:263:in block (2 levels) in execute_action'
5: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/actions/upload_to_testflight.rb:28:in run' 	 4: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/pilot/lib/pilot/build_manager.rb:102:in wait_for_build_processing_to_be_complete'
3: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane_core/lib/fastlane_core/build_watcher.rb:27:in wait_for_build_processing_to_be_complete' 	 2: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane_core/lib/fastlane_core/build_watcher.rb:27:in loop'
1: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane_core/lib/fastlane_core/build_watcher.rb:56:in block in wait_for_build_processing_to_be_complete' /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane_core/lib/fastlane_core/build_watcher.rb:56:in sleep': Interrupt

Environment

  ✅ fastlane environment ✅
Stack

Key
Value

OS
11.2.3

Ruby
2.6.3

Bundler?
false

Git
git version 2.24.3 (Apple Git-128)

Installation Source
/usr/local/bin/fastlane

Host
macOS 11.2.3 (20D91)

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.4

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
# import common Fastfile from appstore-submissions repo (intended to be the root
# of individual app submission repos)
import "../../../../ios-support/iOS.Fastfile"

`./fastlane/Appfile`
# Appfile provides values shared by fastlane tools

app_identifier File.read("../metadata/app_identifier.txt").strip

fastlane gems

Gem
Version
Update-Status

fastlane
2.181.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.3.0

slack-notifier
2.3.2

atomos
0.1.3

CFPropertyList
2.3.6

claide
1.0.3

colored2
3.1.2

nanaimo
0.2.6

xcodeproj
1.13.0

rouge
2.0.7

xcpretty
0.3.0

terminal-notifier
2.0.0

unicode-display_width
1.6.0

terminal-table
1.8.0

plist
3.5.0

public_suffix
2.0.5

addressable
2.7.0

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.7.0

tty-cursor
0.7.0

tty-spinner
0.9.1

artifactory
3.0.15

babosa
1.0.3

colored
1.2

highline
1.7.10

commander-fastlane
4.4.6

excon
0.72.0

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

ruby2_keywords
0.0.2

faraday
1.1.0

faraday_middleware
1.0.0

fastimage
2.1.7

gh_inspector
1.1.3

json
2.1.0

mini_magick
4.10.1

naturally
2.2.0

rubyzip
2.3.0

security
0.1.3

xcpretty-travis-formatter
1.0.0

dotenv
2.7.5

bundler
1.17.3

simctl
1.6.8

jwt
2.1.0

uber
0.1.0

declarative
0.0.10

declarative-option
0.1.0

representable
3.0.4

retriable
3.1.2

mini_mime
1.0.2

multi_json
1.14.1

signet
0.13.0

memoist
0.16.2

os
1.0.1

googleauth
0.11.0

httpclient
2.8.3

google-api-client
0.38.0

google-cloud-env
1.3.1

google-cloud-errors
1.0.0

google-cloud-core
1.5.0

digest-crc
0.5.0

google-cloud-storage
1.25.1

emoji_regex
1.0.1

jmespath
1.4.0

aws-partitions
1.297.0

aws-eventstream
1.0.3

aws-sigv4
1.1.1

aws-sdk-core
3.94.0

aws-sdk-kms
1.30.0

aws-sdk-s3
1.61.2

forwardable
1.2.0

logger
1.3.0

stringio
0.0.2

ipaddr
1.2.2

openssl
2.1.2

ostruct
0.1.0

strscan
1.0.0

date
2.0.0

fileutils
1.1.0

etc
1.0.1

io-console
0.4.7

zlib
1.0.0

libxml-ruby
3.1.0

rexml
3.1.9

psych
3.1.0

mutex_m
0.1.0

webrick
1.4.2

generated on: 2021-04-26

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 upload_to_testflight() failed with Server error got 500.  Output is below:

$ 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]: --------------------------------------
+-------------------------------------+------------------------+
|                   Summary for sigh 2.181.0                   |
+-------------------------------------+------------------------+
| filename                            | app.mobileprovision    |
| adhoc                               | false                  |
| developer_id                        | false                  |
| development                         | false                  |
| skip_install                        | false                  |
| force                               | false                  |
| app_identifier                      | xxx   |
| username                            |<EMAIL_ADDRESS>|
| team_id                             | xxx             |
| ignore_profiles_with_different_name | false                  |
| skip_fetch_profiles                 | false                  |
| skip_certificate_verification       | false                  |
| platform                            | ios                    |
| readonly                            | false                  |
| fail_on_name_taken                  | false                  |
+-------------------------------------+------------------------+
[18:59:10]: Starting login with user<EMAIL_ADDRESS>[18:59:11]: Successfully logged in
[18:59:11]: Fetching profiles...
[18:59:12]: Verifying certificates...
[18:59:12]: No existing profiles found, that match the certificates you have installed locally! Creating a new provisioning profile for you
[18:59:12]: Creating new provisioning profile for 'xxx' with name 'xxx AppStore' for 'ios' platform
[18:59:14]: Downloading provisioning profile...
[18:59:14]: Successfully downloaded provisioning profile...
[18:59:15]: Installing provisioning profile...
/xxx/ios/app.mobileprovision
[18:59:15]: Setting Provisioning Profile type to 'app-store'
[18:59:15]: --------------------------------------
[18:59:15]: --- Step: get_ipa_info_plist_value ---
[18:59:15]: --------------------------------------
[18:59:15]: --------------------------------------
[18:59:15]: --- Step: get_ipa_info_plist_value ---
[18:59:15]: --------------------------------------
[18:59:15]: --------------------------------------
[18:59:15]: --- Step: get_ipa_info_plist_value ---
[18:59:15]: --------------------------------------
[18:59:15]: Original bundle information:
[18:59:15]: App ID: xxx
[18:59:15]: Version: 1.0.0
[18:59:15]: Build number: 2
[18:59:15]: --------------------
[18:59:15]: --- Step: resign ---
[18:59:15]: --------------------
/Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/sigh/lib/assets/resign.sh xxx.ipa D7CCBE667AEE486645E7CF21870E8AAE8F3BAFD0 -p /xxx/ios/app.mobileprovision          xxx.ipa
_floatsignTemp/Payload/GTSeaLevelApp.app: replacing existing signature
[18:59:16]: Successfully signed xxx.ipa!
[18:59:16]: Successfully re-signed .ipa 🔏.
[18:59:16]: Cruising back to lane 'ios beta' 🚘
[18:59:16]: ----------------------------------
[18:59:16]: --- Step: upload_to_testflight ---
[18:59:16]: ----------------------------------
[18:59:16]: Login to App Store Connect<EMAIL_ADDRESS>[18:59:17]: Login successful
[18:59:20]: Ready to upload new build to TestFlight (App: xxx)...
[18:59:34]: iTunes Transporter successfully finished its job
[18:59:34]: Going to upload updated app to App Store Connect
[18:59:34]: This might take a few minutes. Please don't interrupt the script.
[19:00:05]: iTunes Transporter successfully finished its job
[19:00:05]: --------------------------------------------------------------------
[19:00:05]: Successfully uploaded package to App Store Connect. It might take a few minutes until it's visible online.
[19:00:05]: --------------------------------------------------------------------
[19:00:05]: Successfully uploaded the new binary to App Store Connect
[19:00:05]: If you want to skip waiting for the processing to be finished, use the skip_waiting_for_build_processing option
[19:00:05]: Note that if skip_waiting_for_build_processing is used but a changelog is supplied, this process will wait for the build to appear on AppStoreConnect, update the changelog and then skip the remaining of the processing steps.
[19:00:05]: Waiting for processing on... app_id: xxx, app_version: 1.0.0, build_version: 2, platform: IOS
[19:00:05]: Read more information on why this build isn't showing up yet - https://github.com/fastlane/fastlane/issues/14997
[19:00:05]: 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)
[19:00:36]: 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)
[19:01:09]: Waiting for App Store Connect to finish processing the new build (1.0.0 - 2) for IOS
[19:01:40]: Waiting for App Store Connect to finish processing the new build (1.0.0 - 2) for IOS
[19:02:11]: Waiting for App Store Connect to finish processing the new build (1.0.0 - 2) for IOS
[19:02:42]: Waiting for App Store Connect to finish processing the new build (1.0.0 - 2) for IOS
[19:03:13]: Waiting for App Store Connect to finish processing the new build (1.0.0 - 2) for IOS
[19:03:44]: Waiting for App Store Connect to finish processing the new build (1.0.0 - 2) for IOS
[19:04:14]: Successfully finished processing the build 1.0.0 - 2 for IOS
[19:04:15]: Using App Store Connect's default for notifying external testers (which is true) - set notify_external_testers for full control
[19:04:15]: Distributing new build to testers: 1.0.0 - 2
[19:04:15]: Export compliance has been set to 'false'. Need to wait for build to finishing processing again...
[19:04:15]: Set 'ITSAppUsesNonExemptEncryption' in the 'Info.plist' to skip this step and speed up the submission
+--------------------------------------+--------------------------------------+
|                                Lane Context                                 |
+--------------------------------------+--------------------------------------+
| DEFAULT_PLATFORM                     | ios                                  |
| PLATFORM_NAME                        | ios                                  |
| LANE_NAME                            | ios beta                             |
| XCODEBUILD_DERIVED_DATA_PATH         |                                      |
| SIGH_PROFILE_PATH                    | /Users/xxx/Developer/source/apps  |
|                                      | tore-submissions/submissions/sea-le  |
|                                      | vel-sensing/ios/app.mobileprovision  |
| SIGH_PROFILE_PATHS                   | ["/Users/xxx/Developer/source/ap  |
|                                      | pstore-submissions/submissions/sea-  |
|                                      | level-sensing/ios/app.mobileprovisi  |
|                                      | on"]                                 |
| SIGH_UDID                            | 55a432b1-03ed-4db6-8afb-8b7404a0cdc  |
|                                      | e                                    |
| SIGH_UUID                            | 55a432b1-03ed-4db6-8afb-8b7404a0cdc  |
|                                      | e                                    |
| SIGH_NAME                            | xxx AppStore        |
| SIGH_PROFILE_TYPE                    | app-store                            |
| GET_IPA_INFO_PLIST_VALUE_CUSTOM_VAL  | 2                                    |
| UE                                   |                                      |
+--------------------------------------+--------------------------------------+
[19:04:17]: Server error got 500
+------+------------------------+-------------+
|              fastlane summary               |
+------+------------------------+-------------+
| Step | Action                 | Time (in s) |
+------+------------------------+-------------+
| 1    | team_id                | 0           |
| 2    | default_platform       | 0           |
| 3    | Switch to ios          | 0           |
|      | edit_file lane         |             |
| 4    | Switch to ios          | 0           |
|      | ipa_from_xcarchive     |             |
|      | lane                   |             |
| 5    | xcbuild                | 3           |
| 6    | Switch to ios          | 0           |
|      | resign_ipa lane        |             |
| 7    | get_provisioning_prof  | 4           |
|      | ile                    |             |
| 8    | get_ipa_info_plist_va  | 0           |
|      | lue                    |             |
| 9    | get_ipa_info_plist_va  | 0           |
|      | lue                    |             |
| 10   | get_ipa_info_plist_va  | 0           |
|      | lue                    |             |
| 11   | resign                 | 1           |
| 💥   | upload_to_testflight   | 300         |
+------+------------------------+-------------+
[19:04:17]: fastlane finished with errors
Looking for related GitHub issues on fastlane/fastlane...
➡  500 server error
https://github.com/fastlane/fastlane/issues/17886 [open] 49 💬
3 weeks ago
➡  beta_pa path is relative to the fastlane directory, not the project directory
https://github.com/fastlane/fastlane/issues/500 [closed] 4 💬
22 Sep 2016
➡  Deliver fails with error 500 on price tire update phase
https://github.com/fastlane/fastlane/issues/17736 [open] 10 💬
4 weeks ago
and 24 more at: https://github.com/fastlane/fastlane/search?q=The request could not be completed because%3A
	Server error got 500&type=Issues&utf8=✓
🔗  You can ⌘ + double-click on links to open them directly in your browser.
[!] The request could not be completed because:
Server error got 500

Unfortunately, I didn't get a stack trace as I didn't use the --verbose flag.  However, I noticed that the build was successfully uploaded to App Store Connect, so I tried running my script again using distribute_only:true to distribute this new build.  This time the script did not hang looping on "Waiting for the build to show up in the build list", but it did fail with Server error got 500.  This time I did get a stack trace, with the failure occuring in post_beta_app_review_submissions().  Output follows:

$ 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<EMAIL_ADDRESS>Reading keychain entry, because either user or password were empty
Loading session from<EMAIL_ADDRESS>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'
+------+----------------------+-------------+
|             fastlane summary              |
+------+----------------------+-------------+
| Step | Action               | Time (in s) |
+------+----------------------+-------------+
| 1    | team_id              | 0           |
| 2    | default_platform     | 0           |
| 3    | Switch to ios        | 0           |
|      | edit_file lane       |             |
| 💥   | upload_to_testflight | 7           |
+------+----------------------+-------------+
ERROR [2021-04-26 19:17:40.96]: fastlane finished with errors
Looking for related GitHub issues on fastlane/fastlane...
Search query: The request could not be completed because:
Server error got 500
URL: https://api.github.com/search/issues?q=The request could not be completed because%3A
	Server error got 500+repo:fastlane/fastlane
➡  500 server error
https://github.com/fastlane/fastlane/issues/17886 [open] 49 💬
3 weeks ago
➡  beta_pa path is relative to the fastlane directory, not the project directory
https://github.com/fastlane/fastlane/issues/500 [closed] 4 💬
22 Sep 2016
➡  Deliver fails with error 500 on price tire update phase
https://github.com/fastlane/fastlane/issues/17736 [open] 10 💬
4 weeks ago
and 24 more at: https://github.com/fastlane/fastlane/search?q=The request could not be completed because%3A
	Server error got 500&type=Issues&utf8=✓
🔗  You can ⌘ + double-click on links to open them directly in your browser.
Traceback (most recent call last):
33: from /usr/local/bin/fastlane:23:in <main>' 	32: from /usr/local/bin/fastlane:23:in load'
31: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/bin/fastlane:23:in <top (required)>' 	30: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/cli_tools_distributor.rb:122:in take_off'
29: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/commands_generator.rb:41:in start' 	28: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/commands_generator.rb:352:in run'
27: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in run!' 	26: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in run!'
25: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in run_active_command' 	24: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in run'
23: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in call' 	22: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/commands_generator.rb:108:in block (2 levels) in run'
21: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/command_line_handler.rb:36:in handle' 	20: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/lane_manager.rb:47:in cruise_lane'
19: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/runner.rb:45:in execute' 	18: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/runner.rb:45:in chdir'
17: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/runner.rb:49:in block in execute' 	16: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/lane.rb:33:in call'
15: from ../../../../ios-support/iOS.Fastfile:200:in block (2 levels) in parsing_binding' 	14: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/fast_file.rb:159:in method_missing'
13: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/runner.rb:157:in trigger_action_by_name' 	12: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/runner.rb:229:in execute_action'
11: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/runner.rb:229:in chdir' 	10: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/runner.rb:255:in block in execute_action'
9: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/actions/actions_helper.rb:69:in execute_action' 	 8: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/runner.rb:263:in block (2 levels) in execute_action'
7: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/actions/upload_to_testflight.rb:29:in run' 	 6: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/pilot/lib/pilot/build_manager.rb:177:in distribute'
5: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/pilot/lib/pilot/build_manager.rb:401:in distribute_build' 	 4: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/spaceship/lib/spaceship/connect_api/models/build.rb:176:in post_beta_app_review_submission'
3: from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/forwardable.rb:230:in post_beta_app_review_submissions' 	 2: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/spaceship/lib/spaceship/connect_api/testflight/testflight.rb:115:in post_beta_app_review_submissions'
1: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/spaceship/lib/spaceship/connect_api/api_client.rb:124:in post' /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/spaceship/lib/spaceship/connect_api/api_client.rb:191:in handle_response': Server error got 500 (Spaceship::InternalServerError)
33: from /usr/local/bin/fastlane:23:in <main>' 	32: from /usr/local/bin/fastlane:23:in load'
31: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/bin/fastlane:23:in <top (required)>' 	30: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/cli_tools_distributor.rb:122:in take_off'
29: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/commands_generator.rb:41:in start' 	28: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/commands_generator.rb:352:in run'
27: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in run!' 	26: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in run!'
25: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in run_active_command' 	24: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in run'
23: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in call' 	22: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/commands_generator.rb:108:in block (2 levels) in run'
21: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/command_line_handler.rb:36:in handle' 	20: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/lane_manager.rb:47:in cruise_lane'
19: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/runner.rb:45:in execute' 	18: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/runner.rb:45:in chdir'
17: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/runner.rb:49:in block in execute' 	16: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/lane.rb:33:in call'
15: from ../../../../ios-support/iOS.Fastfile:200:in block (2 levels) in parsing_binding' 	14: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/fast_file.rb:159:in method_missing'
13: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/runner.rb:157:in trigger_action_by_name' 	12: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/runner.rb:229:in execute_action'
11: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/runner.rb:229:in chdir' 	10: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/runner.rb:255:in block in execute_action'
9: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/actions/actions_helper.rb:69:in execute_action' 	 8: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/runner.rb:263:in block (2 levels) in execute_action'
7: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/fastlane/lib/fastlane/actions/upload_to_testflight.rb:29:in run' 	 6: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/pilot/lib/pilot/build_manager.rb:177:in distribute'
5: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/pilot/lib/pilot/build_manager.rb:401:in distribute_build' 	 4: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/spaceship/lib/spaceship/connect_api/models/build.rb:176:in post_beta_app_review_submission'
3: from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/forwardable.rb:230:in post_beta_app_review_submissions' 	 2: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/spaceship/lib/spaceship/connect_api/testflight/testflight.rb:115:in post_beta_app_review_submissions'
1: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/spaceship/lib/spaceship/connect_api/api_client.rb:124:in post' /Library/Ruby/Gems/2.6.0/gems/fastlane-2.181.0/spaceship/lib/spaceship/connect_api/api_client.rb:191:in handle_response': [!] The request could not be completed because: (Spaceship::InternalServerError)
Server error got 500

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 Server error got 500 issues (https://github.com/fastlane/fastlane/issues/17886, https://github.com/fastlane/fastlane/issues/17736) , but in my case are breaking during the TestFlight actions, rather than in other FastLane actions documented in existing issues.  Please let me know if I should file a different issue related to these errors.

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 distribute_only:true without specifying the build-- when should default to the latest.  I did the the same when using distribute_only:true with the second build (build '2', 500 error).   If my recollection is correct, before uploading the second build I did try distribute_only:true while explicitly specifying build '1', having the same results ('Waiting..' loop).

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:
  lane :external_pilot do |options|
    set_appstore_api_key

    build_number = app_store_build_number(live: false)

    testflight(
      distribute_only: true,
      groups: ["External Pilot Testers"],
      build_number: build_number.to_s
    )
  end

  lane :set_appstore_api_key do
    app_store_connect_api_key(
      key_id: "XXXXXX",
      issuer_id: "XXXXXX",
      key_filepath: "./AppStoreConnectAPIKey.p8",
      duration: 1200, # optional (maximum 1200)
      in_house: false, # optional but may be required if using match/sigh
    )
  end

output:
[18:41:23]: ------------------------------
[18:41:23]: --- Step: default_platform ---
[18:41:23]: ------------------------------
[18:41:23]: Driving the lane 'ios external_pilot' 🚀
[18:41:23]: -----------------------------------------------------
[18:41:23]: --- Step: Switch to ios set_appstore_api_key lane ---
[18:41:23]: -----------------------------------------------------
[18:41:23]: Cruising over to lane 'ios set_appstore_api_key' 🚖
[18:41:23]: ---------------------------------------
[18:41:23]: --- Step: app_store_connect_api_key ---
[18:41:23]: ---------------------------------------
[18:41:23]: Cruising back to lane 'ios external_pilot' 🚘
[18:41:23]: ------------------------------------
[18:41:23]: --- Step: app_store_build_number ---
[18:41:23]: ------------------------------------
[18:41:23]: Using App Store Connect API token...
[18:41:25]: Fetching the latest build number for any version
[18:41:27]: Latest upload for version 2.0.1 on ios platform is build: 2408
[18:41:27]: build_number: 2408
[18:41:27]: ------------------------
[18:41:27]: --- Step: testflight ---
[18:41:27]: ------------------------
[18:41:27]: Creating authorization token for App Store Connect API
[18:41:30]: Waiting for processing on... app_id: 929744216, app_version: , build_version: 2408, platform: IOS
[18:41:30]: Read more information on why this build isn't showing up yet - https://github.com/fastlane/fastlane/issues/14997
[18:41:30]: 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)

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.

It seems like there was a new fastlane release with an update to the build watcher that went live today, https://github.com/fastlane/fastlane/pull/18682
So instead of the infinite loop of "Waiting for the build to show up in the build list", I get this error instead:
"There is no app version to watch"
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

2021-05-14T20:44:25.9882910Z [20:44:25]: ------------------------
2021-05-14T20:44:25.9884590Z [20:44:25]: --- Step: testflight ---
2021-05-14T20:44:25.9886750Z [20:44:25]: ------------------------
2021-05-14T20:44:25.9887800Z [20:44:25]: Creating authorization token for App Store Connect API
2021-05-14T20:44:27.4449300Z [20:44:27]: Waiting for processing on... app_id: 715582067, app_version: , build_version: 3809, platform: IOS
2021-05-14T20:44:27.4477600Z +---------------------+--------------------+
2021-05-14T20:44:27.4488660Z |               Lane Context               |
2021-05-14T20:44:27.4490000Z +---------------------+--------------------+
2021-05-14T20:44:27.4490910Z | DEFAULT_PLATFORM    | ios                |
2021-05-14T20:44:27.4491690Z | PLATFORM_NAME       | ios                |
2021-05-14T20:44:27.4492620Z | LANE_NAME           | ios external_pilot |
2021-05-14T20:44:27.4493390Z | LATEST_BUILD_NUMBER | 3809               |
2021-05-14T20:44:27.4497010Z | LATEST_VERSION      | 3.8.5              |
2021-05-14T20:44:27.4501760Z +---------------------+--------------------+
2021-05-14T20:44:27.4503200Z [20:44:27]: There is no app version to watch
2021-05-14T20:44:27.5327600Z
2021-05-14T20:44:27.5345720Z +------+-----------------------------------------+-------------+
2021-05-14T20:44:27.5348390Z |                       fastlane summary                       |
2021-05-14T20:44:27.5349970Z +------+-----------------------------------------+-------------+
2021-05-14T20:44:27.5351080Z | Step | Action                                  | Time (in s) |
2021-05-14T20:44:27.5352840Z +------+-----------------------------------------+-------------+
2021-05-14T20:44:27.5353790Z | 1    | default_platform                        | 0           |
2021-05-14T20:44:27.5354740Z | 2    | Switch to ios set_appstore_api_key lane | 0           |
2021-05-14T20:44:27.5356450Z | 3    | app_store_connect_api_key               | 0           |
2021-05-14T20:44:27.5358800Z | 4    | app_store_build_number                  | 2           |
2021-05-14T20:44:27.5360130Z | 💥   | testflight                              | 1           |
2021-05-14T20:44:27.5361720Z +------+-----------------------------------------+-------------+
2021-05-14T20:44:27.5362020Z
2021-05-14T20:44:27.5362770Z [20:44:27]: fastlane finished with errors
2021-05-14T20:44:27.5480820Z
2021-05-14T20:44:27.5482670Z Looking for related GitHub issues on fastlane/fastlane...
2021-05-14T20:44:27.5486140Z
2021-05-14T20:44:28.8400420Z ➡  [Regression][fastlane_core][deliver] Fix deliver is unable to automatically select the latest build and submit it for review
2021-05-14T20:44:28.8402550Z     https://github.com/fastlane/fastlane/pull/18682 [closed] 3 💬
2021-05-14T20:44:28.8406910Z     an hour ago
2021-05-14T20:44:28.8413500Z
2021-05-14T20:44:28.8414880Z ➡  Uploading to TestFlight hangs at "waiting for the build..." for very long time
2021-05-14T20:44:28.8416460Z     https://github.com/fastlane/fastlane/issues/18054 [open] 13 💬
2021-05-14T20:44:28.8417320Z     3 weeks ago
2021-05-14T20:44:28.8417830Z
2021-05-14T20:44:28.8419030Z ➡  DELIVER (2.150.0.rc3/4) always ask attribute whatsNew
2021-05-14T20:44:28.8420390Z     https://github.com/fastlane/fastlane/issues/16700 [open] 80 💬
2021-05-14T20:44:28.8421300Z     2 weeks ago
2021-05-14T20:44:28.8421900Z
2021-05-14T20:44:28.8423220Z and 184 more at: https://github.com/fastlane/fastlane/search?q=There is no app version to watch&type=Issues&utf8=✓
2021-05-14T20:44:28.8424030Z
2021-05-14T20:44:28.8425200Z 🔗  You can ⌘ + double-click on links to open them directly in your browser.
2021-05-14T20:44:28.8427000Z bundler: failed to load command: fastlane (/usr/local/lib/ruby/gems/2.7.0/bin/fastlane)
2021-05-14T20:44:28.8428820Z /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane_core/lib/fastlane_core/build_watcher.rb:90:in matching_build': \e[31m[!] There is no app version to watch\e[0m (FastlaneCore::BuildWatcherError) 2021-05-14T20:44:28.8430800Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane_core/lib/fastlane_core/build_watcher.rb:31:in block in wait_for_build_processing_to_be_complete'
2021-05-14T20:44:28.8432450Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane_core/lib/fastlane_core/build_watcher.rb:30:in loop' 2021-05-14T20:44:28.8434170Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane_core/lib/fastlane_core/build_watcher.rb:30:in wait_for_build_processing_to_be_complete'
2021-05-14T20:44:28.8435850Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/pilot/lib/pilot/build_manager.rb:102:in wait_for_build_processing_to_be_complete' 2021-05-14T20:44:28.8437790Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane/lib/fastlane/actions/upload_to_testflight.rb:28:in run'
2021-05-14T20:44:28.8440810Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane/lib/fastlane/runner.rb:263:in block (2 levels) in execute_action' 2021-05-14T20:44:28.8442650Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane/lib/fastlane/actions/actions_helper.rb:69:in execute_action'
2021-05-14T20:44:28.8444230Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane/lib/fastlane/runner.rb:255:in block in execute_action' 2021-05-14T20:44:28.8445830Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane/lib/fastlane/runner.rb:229:in chdir'
2021-05-14T20:44:28.8447410Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane/lib/fastlane/runner.rb:229:in execute_action' 2021-05-14T20:44:28.8449030Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane/lib/fastlane/runner.rb:157:in trigger_action_by_name'
2021-05-14T20:44:28.8450580Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane/lib/fastlane/fast_file.rb:159:in method_missing' 2021-05-14T20:44:28.8452050Z 	from Fastfile:170:in block (2 levels) in parsing_binding'
2021-05-14T20:44:28.8454040Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane/lib/fastlane/lane.rb:33:in call' 2021-05-14T20:44:28.8455610Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane/lib/fastlane/runner.rb:49:in block in execute'
2021-05-14T20:44:28.8457120Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane/lib/fastlane/runner.rb:45:in chdir' 2021-05-14T20:44:28.8458670Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane/lib/fastlane/runner.rb:45:in execute'
2021-05-14T20:44:28.8460190Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane/lib/fastlane/lane_manager.rb:47:in cruise_lane' 2021-05-14T20:44:28.8461880Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane/lib/fastlane/command_line_handler.rb:36:in handle'
2021-05-14T20:44:28.8463490Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane/lib/fastlane/commands_generator.rb:109:in block (2 levels) in run' 2021-05-14T20:44:28.8465080Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/commander-4.6.0/lib/commander/command.rb:187:in call'
2021-05-14T20:44:28.8466530Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/commander-4.6.0/lib/commander/command.rb:157:in run' 2021-05-14T20:44:28.8468080Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/commander-4.6.0/lib/commander/runner.rb:444:in run_active_command'
2021-05-14T20:44:28.8469620Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in run!' 2021-05-14T20:44:28.8471190Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/commander-4.6.0/lib/commander/delegates.rb:18:in run!'
2021-05-14T20:44:28.8473120Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane/lib/fastlane/commands_generator.rb:353:in run' 2021-05-14T20:44:28.8474730Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane/lib/fastlane/commands_generator.rb:42:in start'
2021-05-14T20:44:28.8476290Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane/lib/fastlane/cli_tools_distributor.rb:122:in take_off' 2021-05-14T20:44:28.8477870Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/bin/fastlane:23:in <top (required)>'
2021-05-14T20:44:28.8479230Z 	from /usr/local/lib/ruby/gems/2.7.0/bin/fastlane:23:in load' 2021-05-14T20:44:28.8480640Z 	from /usr/local/lib/ruby/gems/2.7.0/bin/fastlane:23:in <top (required)>'
2021-05-14T20:44:28.8482030Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.17/lib/bundler/cli/exec.rb:63:in load' 2021-05-14T20:44:28.8483560Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.17/lib/bundler/cli/exec.rb:63:in kernel_load'
2021-05-14T20:44:28.8485140Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.17/lib/bundler/cli/exec.rb:28:in run' 2021-05-14T20:44:28.8486680Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.17/lib/bundler/cli.rb:494:in exec'
2021-05-14T20:44:28.8488160Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.17/lib/bundler/vendor/thor/lib/thor/command.rb:27:in run' 2021-05-14T20:44:28.8489790Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.17/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in invoke_command'
2021-05-14T20:44:28.8491320Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.17/lib/bundler/vendor/thor/lib/thor.rb:392:in dispatch' 2021-05-14T20:44:28.8492930Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.17/lib/bundler/cli.rb:30:in dispatch'
2021-05-14T20:44:28.8494410Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.17/lib/bundler/vendor/thor/lib/thor/base.rb:485:in start' 2021-05-14T20:44:28.8496030Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.17/lib/bundler/cli.rb:24:in start'
2021-05-14T20:44:28.8497500Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.17/exe/bundle:49:in block in <top (required)>' 2021-05-14T20:44:28.8499070Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.17/lib/bundler/friendly_errors.rb:130:in with_friendly_errors'
2021-05-14T20:44:28.8500410Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.17/exe/bundle:37:in <top (required)>' 2021-05-14T20:44:28.8502360Z 	from /usr/local/lib/ruby/gems/2.7.0/bin/bundle:23:in load'
2021-05-14T20:44:28.8503620Z 	from /usr/local/lib/ruby/gems/2.7.0/bin/bundle:23:in <main>' 2021-05-14T20:44:28.8505480Z /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane_core/lib/fastlane_core/build_watcher.rb:90:in matching_build': There is no app version to watch (FastlaneCore::BuildWatcherError)
2021-05-14T20:44:28.8507290Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane_core/lib/fastlane_core/build_watcher.rb:31:in block in wait_for_build_processing_to_be_complete' 2021-05-14T20:44:28.8509360Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane_core/lib/fastlane_core/build_watcher.rb:30:in loop'
2021-05-14T20:44:28.8510890Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane_core/lib/fastlane_core/build_watcher.rb:30:in wait_for_build_processing_to_be_complete' 2021-05-14T20:44:28.8512520Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/pilot/lib/pilot/build_manager.rb:102:in wait_for_build_processing_to_be_complete'
2021-05-14T20:44:28.8514060Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane/lib/fastlane/actions/upload_to_testflight.rb:28:in run' 2021-05-14T20:44:28.8515550Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane/lib/fastlane/runner.rb:263:in block (2 levels) in execute_action'
2021-05-14T20:44:28.8517090Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane/lib/fastlane/actions/actions_helper.rb:69:in execute_action' 2021-05-14T20:44:28.8518550Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane/lib/fastlane/runner.rb:255:in block in execute_action'
2021-05-14T20:44:28.8520470Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane/lib/fastlane/runner.rb:229:in chdir' 2021-05-14T20:44:28.8521870Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane/lib/fastlane/runner.rb:229:in execute_action'
2021-05-14T20:44:28.8523360Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane/lib/fastlane/runner.rb:157:in trigger_action_by_name' 2021-05-14T20:44:28.8524850Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane/lib/fastlane/fast_file.rb:159:in method_missing'
2021-05-14T20:44:28.8526200Z 	from Fastfile:170:in block (2 levels) in parsing_binding' 2021-05-14T20:44:28.8527480Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane/lib/fastlane/lane.rb:33:in call'
2021-05-14T20:44:28.8529200Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane/lib/fastlane/runner.rb:49:in block in execute' 2021-05-14T20:44:28.8531140Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane/lib/fastlane/runner.rb:45:in chdir'
2021-05-14T20:44:28.8532660Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane/lib/fastlane/runner.rb:45:in execute' 2021-05-14T20:44:28.8534070Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane/lib/fastlane/lane_manager.rb:47:in cruise_lane'
2021-05-14T20:44:28.8535580Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane/lib/fastlane/command_line_handler.rb:36:in handle' 2021-05-14T20:44:28.8537050Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane/lib/fastlane/commands_generator.rb:109:in block (2 levels) in run'
2021-05-14T20:44:28.8538500Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/commander-4.6.0/lib/commander/command.rb:187:in call' 2021-05-14T20:44:28.8539810Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/commander-4.6.0/lib/commander/command.rb:157:in run'
2021-05-14T20:44:28.8541340Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/commander-4.6.0/lib/commander/runner.rb:444:in run_active_command' 2021-05-14T20:44:28.8542750Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in run!'
2021-05-14T20:44:28.8544180Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/commander-4.6.0/lib/commander/delegates.rb:18:in run!' 2021-05-14T20:44:28.8546080Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane/lib/fastlane/commands_generator.rb:353:in run'
2021-05-14T20:44:28.8547540Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane/lib/fastlane/commands_generator.rb:42:in start' 2021-05-14T20:44:28.8548970Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/fastlane/lib/fastlane/cli_tools_distributor.rb:122:in take_off'
2021-05-14T20:44:28.8550390Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.183.0/bin/fastlane:23:in <top (required)>' 2021-05-14T20:44:28.8551620Z 	from /usr/local/lib/ruby/gems/2.7.0/bin/fastlane:23:in load'
2021-05-14T20:44:28.8553100Z 	from /usr/local/lib/ruby/gems/2.7.0/bin/fastlane:23:in <top (required)>' 2021-05-14T20:44:28.8554370Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.17/lib/bundler/cli/exec.rb:63:in load'
2021-05-14T20:44:28.8555720Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.17/lib/bundler/cli/exec.rb:63:in kernel_load' 2021-05-14T20:44:28.8557050Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.17/lib/bundler/cli/exec.rb:28:in run'
2021-05-14T20:44:28.8558390Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.17/lib/bundler/cli.rb:494:in exec' 2021-05-14T20:44:28.8559730Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.17/lib/bundler/vendor/thor/lib/thor/command.rb:27:in run'
2021-05-14T20:44:28.8561190Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.17/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in invoke_command' 2021-05-14T20:44:28.8562640Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.17/lib/bundler/vendor/thor/lib/thor.rb:392:in dispatch'
2021-05-14T20:44:28.8564470Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.17/lib/bundler/cli.rb:30:in dispatch' 2021-05-14T20:44:28.8565820Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.17/lib/bundler/vendor/thor/lib/thor/base.rb:485:in start'
2021-05-14T20:44:28.8567190Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.17/lib/bundler/cli.rb:24:in start' 2021-05-14T20:44:28.8568510Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.17/exe/bundle:49:in block in <top (required)>'
2021-05-14T20:44:28.8569940Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.17/lib/bundler/friendly_errors.rb:130:in with_friendly_errors' 2021-05-14T20:44:28.8571280Z 	from /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.17/exe/bundle:37:in <top (required)>'
2021-05-14T20:44:28.8572530Z 	from /usr/local/lib/ruby/gems/2.7.0/bin/bundle:23:in load' 2021-05-14T20:44:28.8573700Z 	from /usr/local/lib/ruby/gems/2.7.0/bin/bundle:23:in '

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:
"There is no app version to watch"
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 BuildWatcher was working before for deliver and pilot and both of them got a seperate treatment based on select_latest flag.
https://github.com/fastlane/fastlane/blob/44431ba06480ab586fae3893208ea36451f553ab/fastlane_core/lib/fastlane_core/build_watcher.rb#L63-L78
When select_latest for deliver is true BuildWatcher attempts to select latest build even if only build_number is provided and app_version is skipped. I think that if there were two builds, e.g. 1.1.0(2) and 1.0.0(1), and we were searching with 'build_number' = '1', it would fetch 1.0.0(1) as the latest.
upload_to_testflight/pilot calls BuildWatcher through BuildManager with select_latest = false:
https://github.com/fastlane/fastlane/blob/7cc8c67a42ada48d83f1d1c25d3f2a8c89d0c3c2/pilot/lib/pilot/build_manager.rb#L92-L110
My understanding is that for pilot if AppStore ConnectAPI returns more than 1 build, it should crash.
For example, if we had builds 1.0.0(1) and 1.1.0(1) and used pilot with only build_number = 1 it would crash.
I think that it wouldn't crash only if build_number values were unique across all builds for the app, because AppStore would return only 1 build. Using only build_number without app_version may lead to unexpected results.
Please correct me if my understanding is wrong.
To have the same logic as before and match the logic without waiting for build processing enabled:
https://github.com/fastlane/fastlane/blob/7cc8c67a42ada48d83f1d1c25d3f2a8c89d0c3c2/pilot/lib/pilot/build_manager.rb#L125-L138
code below
https://github.com/fastlane/fastlane/blob/7cc8c67a42ada48d83f1d1c25d3f2a8c89d0c3c2/fastlane_core/lib/fastlane_core/build_watcher.rb#L84-L92
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 upload_to_testflight with verbose logging, but don't out much more. I think pilot is running into timeout problems, although I'm not sure if this is related to the server error though.
This is the output:
INFO [2021-05-21 15:45:33.66]: Distributing new build to testers: 21.20.5 -<PHONE_NUMBER>
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-05-21 15:45:35.50]: Lane Context:
INFO [2021-05-21 15:45:35.50]: {:DEFAULT_PLATFORM=>:ios, :PLATFORM_NAME=>:ios, :LANE_NAME=>"ios publish_testflight", :KEYCHAIN_PATH=>"~/Library/Keychains/tmp_keychain"}
ERROR [2021-05-21 15:45:35.50]: Server error got 500

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.