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.
When debug stepping into an async method on iOS using a physical device (simulator is untested) with linking set to SDK only, the application crashes.
The application does not crash if the debugger is attached, but not stepping through code, or linker is set to don't link, or the debugger is not attached.
Scenario has not been tested in the iOS simulator, customer does development solely on hardware.
Xamarin for Visual Studio 220.127.116.112
Does in happen on the Mac (using XS) ?
Because it sounds like the _old_ (C6?) issue where a different version of Cecil (master) was used (in XVS) and that only affected XVS users. If Cecil was re-bumped, without fixing that old issue, then it might have resurfaced.
As far as I can tell it _is_ that issue, but the thing is I think (not sure) that iOS is still using that very old cecil that's incompatible with newer versions of VS.
Linker is still breaking the symbols. Moving to iOS.
master and C9 are now using the latest revision of Cecil
However this is no test case to check if this was the issue, nor any confirmation that this happened on XS (mac only)
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!