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 5079 [details]
Objective C project and Xamarin solution replicating the issue.
We are having the issue described here http://stackoverflow.com/questions/19188924/xamarin-binding-to-ios-block
iOS passes a block to C# that is later on called from C#, the block gets called but it seems to have lost the context, ie: local variables that are supposed to have values get the values lost.
Attached is the complete Xamarin project replicating the issue. Also, XCode project used to create the static library was included.
Thanks for the perfect test case.
The problem is that we take an NSStackBlock and store it in heap memory. We need to copy that to a NSMallocBlock.
Any idea when it will be fixed?
Will we get notified when it is fixed?
I can't promise any date it'll be fixed (hopefully soon, I believe I know how to do it), but I'll be notified here when it happens.
You'll be notified too :)
At this point I do not know yet which release will contain the fix (but the bug # will be listed in the corresponding release notes).