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 opening a monodroid project in visual studio it crashes instantly and leaves this nice message in logs. In monodevelop it crashes once i try to open a .axml file.
Info on VS
Does this happen for all solutions you try to open? Does it happen when you create or open a new solution created from scratch?
If you are running MonoDevelop 3.0 on windows, can you please attach the last log file you'll find in the following directory? thanks:
Sorry, another request: which java version do you have? (try running "java -version" in a console)
It dose it on creating a brand new monodroid application as well as opening old ones.
However i seemed to have fixed the issue (thanks for the java -version) what ended up happening was that i had set my path to java to a jre run time then what probably happened is i guess the sdk got installed when i installed monodroid but the path was never set to the jdk or something and so when i typed java -version i got could not read jvm.cfg just switching my path to the jdk fixed it.
now i am getting mono.debugging.soft.DisconnectedException which is probably unrelated.
Fixed in master and 4.2 branch
*** Bug 5073 has been marked as a duplicate of this bug. ***
*** Bug 5301 has been marked as a duplicate of this bug. ***