Bug 16544 - synthesizer.StartSpeakingStringtoURL not working
Summary: synthesizer.StartSpeakingStringtoURL not working
Status: RESOLVED DUPLICATE of bug 16543
Alias: None
Product: Xamarin.Mac
Classification: Desktop
Component: Library (Xamarin.Mac.dll) ()
Version: 1.6.19
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Aaron Bockover [MSFT]
URL:
Depends on:
Blocks:
 
Reported: 2013-12-02 05:11 UTC by Mike James
Modified: 2013-12-02 05:12 UTC (History)
1 user (show)

Tags:
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:
Status:
RESOLVED DUPLICATE of bug 16543

Description Mike James 2013-12-02 05:11:22 UTC
A customer a found that the StartSpeakingStringtoURL method of NSSpeechSynthesizer doesn't work. 

He is using the following to reproduce the issue: 

var synthesizer = new NSSpeechSynthesizer ();

// synthesizer.StartSpeakingString ("hello”); // this works

synthesizer.StartSpeakingStringtoURL("test hello", new NSUrl("test"));

The above does not create the file (he checked the file and it is not there, he has also created the delegate and it doesn’t get called either)
Comment 1 Mike James 2013-12-02 05:12:32 UTC

*** This bug has been marked as a duplicate of bug 16543 ***