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.
Created attachment 2190 [details]
The example is a bit strange, but was the easiest to hack together. It appears that returning an NSData without Length and Bytes defined will crash in native code. Defining those property overloads "fixes" the problem.
The methods can not be abstract, since NSData is a concrete type (you can instantiate it).
It merely means that if you subclass, you need to implement both.
Not sure that there is much that can be done, beyond documenting it.
Is there no way you could make deriving from NSData but not overriding these methods a compile warning/error or something else that doesn't crash in native code?
I can not think of anything bullet proof.