Bug 44988 - Invalid value when adding a SecRecord
Summary: Invalid value when adding a SecRecord
Status: RESOLVED DUPLICATE of bug 44361
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: XI 10.0 (iOS10)
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2016-10-03 18:29 UTC by jmgomez
Modified: 2016-10-03 20:51 UTC (History)
3 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 jmgomez 2016-10-03 18:29:15 UTC
With iOS 10 adding a SecRecord with the method SecKeyChain returns a value (-34018) which has no map in the current Enum (SecStatusCode).

There is another users in the forums experimenting this issue as well: https://forums.xamarin.com/discussion/78759/seckeychain-add-new-secrecord-seckind-genericpassword-returns-an-invalid-code

Code to reproduce it: 
var record = new SecRecord{ Service = "", Label = "", Account = "", Generic = NSData.FromString("", NSStringEncoding.UTF8) };
Comment 1 jmgomez 2016-10-03 18:32:17 UTC
The assembly version is:
Comment 2 Timothy Risi 2016-10-03 20:51:46 UTC
This is an known issue with Apple's simulator (affects everyone, not just XI).


There is a workaround in https://bugzilla.xamarin.com/show_bug.cgi?id=44361

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