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.
Customer reports that the implementation of Android.Runtime.JavaCollection<T>.CopyTo is lacking a IntPtr.Zero check on JavaCollection.id_toArray.
Using the Xamarin Studio assembly browser, the code for this method seems to be:
Indeed, there is no IntPtr.Zero check.
The customer states that they work around this by manually iterating over the collection, as GetEnumerator() does not contain the same bug.
The customer's Xamarin.Android version is Xamarin.Android 18.104.22.168 (5f55a9ef61c11b6ce0890bc91e4c71b1b92be214)
The full version info is here: https://gist.github.com/natfriedman/2f271f70aeb4a739e0d9
Fixed in monodroid/57822ef0.
Thanks Jon. Where do I check what release that will be in?
> Where do I check what release that will be in?
Release notes. Or the Target Milestone (which wasn't previously set), though that's frequently only a guideline (e.g. if a "new" "hotfoot" release is inserted before the "expected" C6SR1, that will "push down" the expected release numbers, so at best Target Milestone is only a guideline.)
I have checked this issue with the latest master build both on Mac and Windows:
Now this issue is working fine.
screencast for Mac XS: http://www.screencast.com/t/KgqQVPznh
Screencast for Windows XS: http://www.screencast.com/t/AxfLl7vaXu
Hence closing the issue.