Bug 13346 - CTFont constructor checking incorrectly that argument can't be null.
Summary: CTFont constructor checking incorrectly that argument can't be null.
Alias: None
Product: Xamarin.Mac
Classification: Desktop
Component: Library (Xamarin.Mac.dll) ()
Version: 1.4.x
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Aaron Bockover [MSFT]
Depends on:
Reported: 2013-07-19 13:26 UTC by Jon Lipsky
Modified: 2013-09-26 12:21 UTC (History)
1 user (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 Jon Lipsky 2013-07-19 13:26:35 UTC
I am trying to use CoreText in a Xamarin.Mac (and eventually a Xamarin.iOS) application and I believe there a "non null" check in one of the CTFont constructors that shouldn't be there.

Specifically, I think the following method is incorrectly enforcing that the "language" argument is not null:
MonoMac.CoreText.CTFont..ctor (CTFontUIFontType uiType, Single size, System.String language)

Here's a link to the iOS documentation for CTFont:

Specifically, look at the entry for "CTFontCreateUIFontForLanguage".  Is says that the language argument can be null.

Comment 1 Aaron Bockover [MSFT] 2013-09-26 12:21:49 UTC
This has been fixed (for both mac and iOS) and will be in the next xammac release. Thanks Jon!