Bug 58937 - PdfDocument.FindAsync method overloads all return void, rather than Task
Summary: PdfDocument.FindAsync method overloads all return void, rather than Task
Alias: None
Product: iOS
Classification: Xamarin
Component: Tools ()
Version: XI 10.99 (xcode9)
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2017-08-21 21:42 UTC by Mike Norman
Modified: 2017-08-22 00:28 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description Mike Norman 2017-08-21 21:42:29 UTC
PdfDocument.FindAsync method overloads all return void, rather than Task

They return Task? :D
Comment 1 Timothy Risi 2017-08-22 00:28:54 UTC
These methods are not actually C# async/await methods.  They're bindings for 

- (void)beginFindStrings:(NSArray<NSString *> *)strings 

FindAsync simply triggers the asynchronous search for strings.  Notifications are issued after that when things are happening.  From the documentation (https://developer.apple.com/documentation/pdfkit/pdfdocument/1436096-beginfindstrings?language=objc):

"This method returns immediately. It causes notifications to be issued when searching begins and ends, on each search hit, and when the search proceeds to a new page. For options, refer to Searching, Comparing, and Sorting Strings."