Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
I've been using BinaryFormatter.Deserialize in a project for quite some time.
Today, after updating from 184.108.40.206 to 220.127.116.11 I started getting System.NullReferenceException when using the BinaryFormatter.Deserialize to deseralize a HashTable. I've had to roll back to 18.104.22.168.
We might have inherited a recent mono bug while updated the BCL. Sadly it means that case was not covered by some unit tests (or used in our test applications).
Can you attach a small test case (unit test or a small app) that shows the issue. We'll fix this and ensure it gets part of the test suite. Thanks!
Also do you remember if the NRE occured:
* only occured on the simulator ?
* did the same happen on devices ?
It was in the simulator.
If it works in release (not debug) build for the simulator (or on devices, debug or release) then it's likely a duplicate of bug #14493
Can you try this ? or supply a test case so we can validate this ?
We will try to provide a test case. We are working hard to meet a deadline for a demo and are currently using Version 22.214.171.124 of Xamarin.
I understand, no rush. When you have the time try first 6.4.5 which has a fix (the single fix for that release) for a very similar problem (bug #14552).
Setting back to NEEDINFO (which means we, Xamarin, are waiting on more information on the bug).
I installed 6.4.5 and the issue went away. Thank you.