Bug 15479 - xamarin dictionary "Destination array cannot hold the requested elements!"
Summary: xamarin dictionary "Destination array cannot hold the requested elements!"
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: 7.0.4.x
Hardware: PC Windows
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2013-10-18 03:52 UTC by technology
Modified: 2016-05-24 20:26 UTC (History)
2 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 technology 2013-10-18 03:52:46 UTC
Hi all,

were having some issues when serializing data on iOS in a multithreaded fashion. At some point in our app, multiple webservice calls are being done in a asynchronous way and the result (xml) is then serialized to disk. However, when we do that usually one or more serialization actions failed with the following error:

Destination array cannot hold the requested elements!

Anyone seen this as well?


Comment 1 technology 2013-10-18 04:07:33 UTC
In some other cases I get another error which is:

Array index is out of range.
Comment 2 Sebastien Pouliot 2013-10-18 08:30:44 UTC
No, that does not ring any bell.

Could you attach a test case that reproduce the issue ? you can mark the attachment as private (so only Xamarin will be avble to see/download it).

Exception and stack traces can also be useful (but less than a test case). Also include all the software version you're using.

The easiest way to get exact version information is to use the "Xamarin Studio" menu, "About Xamarin Studio" item, "Show Details" button and copy/paste the version informations (you can use the "Copy Information" button).
Comment 3 technology 2013-10-18 09:48:19 UTC
Here's the version information.

=== Xamarin Studio ===

Version 4.0.13 (build 38)
Installation UUID: ce710a02-7b2b-4804-a448-2ebba3236f1c
	Mono 3.2.3 ((no/8d3b4b7)
	GTK+ 2.24.20 theme: Raleigh
	GTK# (
	Package version: 302030000

=== Apple Developer Tools ===

Xcode 4.6.2 (2067.2)
Build 4H1003

=== Xamarin.iOS ===

Version: (Business Edition)
Hash: 57edee2
Build date: 2013-04-10 18:05:51-0400

=== Xamarin.Mac ===

Xamarin.Mac: Not Installed

=== Xamarin.Android ===

Not Installed

=== Build Information ===

Release ID: 400130038
Git revision: 07afec667f7be5d0ee511eb7115bbac6377fbae8
Build date: 2013-09-24 08:53:29+0000
Xamarin addins: 61140345a5b109633a94409edcbc7a4c19a425c6

=== Operating System ===

Mac OS X 10.7.5
Darwin Mathieus-Mac.local 11.4.2 Darwin Kernel Version 11.4.2
    Thu Aug 23 16:26:45 PDT 2012
    root:xnu-1699.32.7~1/RELEASE_I386 i386
Comment 4 Sebastien Pouliot 2016-05-24 20:26:55 UTC
We have not received the requested information. If you are still experiencing this issue please provide all the requested information and re-open the bug report. Thanks!