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.
Also the text in them is grey.
It's in grey because the output (and the error) is from the mtouch tool that we use to run the app, not from the app itself. We can improve that by moving the code to run apps on the simulator into the MD addin itself, and report those kinds of errors in a dialog.
We could maybe mark the output pad's tab red for apps that end with a nonzero exit code?
I think the text should be easier to read, and should be left on the screen if the app crashes.
The text isn't an app crash.
You're right but you're splitting hairs. If my app doesn't run at all, I need to know why. Right now MD leaves me alone in the cold.
In general, it's important to have a way to distinguish the output of the app from the output of the tool that runs the app. That's why it's grey. Maybe we could make it some brighter colour, like blue. But the best solution in this case would be to allow MD to launch the app directly and report errors in an understandable way instead of making the user parse a tool crash.
Let's use a brighter color. Even a brighter grey would be ok.
And let's make sure that the messages don't disappear when the app crashes. That is the larger issue.
We will be checking the error at the MonoDevelop level, before we even ask mtouch to do anything.
And I want to do those checks for other bits there as well, so I am closing this bug (as it is a duplicate)
*** This bug has been marked as a duplicate of bug 460 ***