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 for Bug 32157 on
GitHub or Developer Community if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Description of Problem:
Double clicking on the warning attempts to open the path as a file and errors in a dialog.
Steps to reproduce the problem:
1. Open an iOS project
2. Double click on PushKit warning
Generates error, try to open warning as a file
Not sure if it's the task or the IDE that should handle this properly - but Jeff will know.
The IDE handles it properly. When the user tries to jump to the error, It reports that the file doesn't exist, which is true. The build target should not report an error location that doesn't exist.
This is actually probably a bug in mtouch since the MSBuild output parser is used on the mtouch output to parse file/line/column/etc info.
This is what mtouch prints:
> warning MT0043: The Boehm garbage collector is currently not supported when referencing 'Xamarin.iOS.dll'. The SGen garbage collector has been selected instead.
This is what shows up in the IDE output log:
> MTOUCH: warning MT0043: The Boehm garbage collector is currently not supported when referencing 'Xamarin.iOS.dll'. The SGen garbage collector has been selected instead.
so it's not an mtouch bug.
Then it's a bug in xbuild's parser.
The MTouchTask does not parse the error/warning messages. That all gets handled by xbuild.