Bug 14223 - CoreData / Null values with [Export] statement
Summary: CoreData / Null values with [Export] statement
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: 6.4.0
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: Untriaged
Assignee: Manuel de la Peña [MSFT]
Depends on:
Reported: 2013-08-24 05:16 UTC by StephaneC
Modified: 2016-05-16 09:27 UTC (History)
3 users (show)

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

Sample to reproduce the problem (1.41 MB, application/zip)
2013-08-24 05:16 UTC, StephaneC

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 StephaneC 2013-08-24 05:16:11 UTC
Created attachment 4708 [details]
Sample to reproduce the problem

I have created a sample (attached to this report) to use CoreData.

If you execute it as is, it will work and data are inserted into the SQLite repository.

But if you uncomment the [Export] statements in the Employee class, NULL values are inserted instead of expected values.

The [Export] statements are required if you want to use validation predicates (see CoreDataSampleViewController).

Am I missing something or is it a real problem ?
Comment 1 StephaneC 2013-08-24 12:27:51 UTC
I investigated in more details and the problem seems linked to KVC.

I attached an observer to my object to understand what happens.

When you uncomment the [Export] statement and you call SetValueForKey, the observer is not notified about the modification.

When you comment the [Export] statement, the observer is notified about modifications as expected.
Comment 2 Sebastien Pouliot 2016-05-13 14:50:42 UTC
@Manuel can you have a look if this issue still exists in master ? thanks!
Comment 3 Manuel de la Peña [MSFT] 2016-05-16 09:27:41 UTC
Using the provided app I have done the following:

1. Executed the application with master and without the [Export] attribute and using SetValueForKey: Result => Successful.
2. Executed the application with master without the [Export] attribute using the properties: Result => Successful.
3. Executed the application with master with the [Export] attribute using the SetValueForKey: Result => Successful.
4. Executed the application with master with the [Export] attribute using the properties: Result -> Successful.

We can say that the bug does not longer exist. Will set the bug not reproducible because we do not know the commit in which the bug was fixed.