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 55622 on
Developer Community or GitHub 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
You get errors such as these.
Error MM4162: The type 'AVFoundation.AVContentKeyRequest' (used as a parameter in AVFoundation.AVContentKeySession.RenewExpiringResponseData) is not available in macOS 10.12.2 (it was introduced in macOS 10.12.4). Please build with a newer macOS SDK (usually done by using the most recent version of Xcode).<--- (MM4162) (projname) ---> (Inner Exception #0)
It should be reasonable to search the error message for something like "is not available in macOS" and show a custom error that suggests:
- Enable linking
- Upgrade Xcode
- Disable static registrar.
See https://bugzilla.xamarin.com/show_bug.cgi?id=54998 for an example.
Who should search the error message? If Xamarin Studio, then the bug should be moved there. If mmp, then there's no need to search the error message, we can just change it.
We should also document mmp errors (like we do for mtouch errors).
I was thinking mtouch/mmp.
So we convert MM4162 into another error with it embedded. Since we know that:
- We are invoking clang on our static registrar
- We know that the compiler came back with an error
- We can parse the output looking for a hint that we need a newer XCode).
We already do some return code checking here:
But i'm not opposed if you have a better idea.
When we show MM4162, it's because we already know that clang won't be able to compile the generated output. We can change the message to say whatever we want.
Note that we generate this entire message , it's not something we're re-throwing from a clang error.
Let me think if I can come up with a better error message.