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 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.
Created attachment 1980 [details]
build time error Emulator
Since We purchased and activated your product we are not yet able to run application. We used get error defferent type of errors. so we formated new system and try to install. installation is finished. (not yet activated or transfered licencekey)
but still we are not able to get emulator here we gave screen shots.
I'm experiencing the same problem with 4.2.2 in Visual Studio. It appears to only happen when starting an emulator from within VS. Once the emulator is loaded, you can restart VS (and thus the plugin) and it shows up in the list. I've attached the full log file.
I have another customer with a similar case.
Created attachment 2073 [details]
Same problem here. With earlier versions of Mondroid it was still possible to kill adb.exe from the task manager, then the emulator would be shown in the list. However, now even this trick does not work anymore and I have to restart Visual Studio. This is very annoyoing.
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?
If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.
Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.