Bug 11043 - Aes.Create Function Returns Null
Summary: Aes.Create Function Returns Null
Status: RESOLVED DUPLICATE of bug 7771
Alias: None
Product: Android
Classification: Xamarin
Component: BCL Class Libraries ()
Version: 4.8.x
Hardware: PC Windows
: High normal
Target Milestone: ---
Assignee: Jonathan Pryor
Depends on:
Reported: 2013-03-11 10:01 UTC by Andrew Reitz
Modified: 2014-01-14 16:02 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 Andrew Reitz 2013-03-11 10:01:57 UTC
I am passing the Aes.Create function into a function as a Func<SymmetricAlgorithm>.  When calling this function on a desktop system the Aes object is created.  In Monodroid a null value is returned.
Comment 1 Seifer 2013-03-15 09:14:57 UTC
I experience the same issue on Xamarion.Android: Aes.Create() returns null.

Passing values described in MSDN do not help.

Xamarin.iOS returns correct value.
Comment 2 Jonathan Pryor 2013-03-22 14:34:54 UTC
This is probably a dup or variation on Bug #7771.

As a workaround, create a new instance of System.Security.Cryptography.AesManaged.
Comment 3 Andrew Reitz 2013-03-25 09:28:17 UTC
Your work around worked. Thank you!
Comment 4 Jonathan Pryor 2014-01-14 16:02:48 UTC

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