Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
`SFSpeechRecognizer.GetRecognitionTaskAsync(recognitionRequest)` is the async-ified version of the callback-ish `SFSpeechRecognizer.GetRecognitionTask(recognitionRequest, Action<SFSpeechRecognitionResult,NSError>)` but the callback handler is called *multiple* times as the speech recognizer refines things.
So, if one uses:
var recoResult = await speechRecognizer.GetRecognitionTaskAsync(recognitionRequest);
if (recoResult.BestTranscription != null) //...etc...
That runs fine *the first time* and then you get an exception, at least if you're running this via Task.Run(). I'm not sure if the async method is a mistake or if there's an iOS technique for manipulating the ExecutionContext that I don't know.
@Alex, please check other [Async]ified API, with Apple documentation, to see if other similar cases exists.
Fixed in xamarin-macios/xcode8 @ eedc7f618584c73cbdd0d558325af60232ae4504