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 56797 on
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
Created attachment 22418 [details]
-When Android workbook is created then initially Android wear simulator starts. Now if we closed the Android wear simulator then Android Phone simulator starts and Even after that it gives us error that unable to connect.
-Also if we have already the simulator and then launched workbook , We are still getting Unable to connect.
-Microsoft Visual Studio Enterprise 2017 d15svc
Version 15.2 (26430.10) d15svc d15svc
Microsoft .NET Framework
Installed Version: Enterprise
Xamarin 22.214.171.1245 (70f1268)
Xamarin.Android SDK 126.96.36.199 (bc24645)
Xamarin.iOS and Xamarin.Mac SDK 10.10.0.35 (4cffddf)
Xamarin Workbook v1.2.2
Steps to Reproduce
1-Launch Xamarin Workbooks
2-Select Xamarin.Android from workbooks template list and click on Create workbook.
3-observe the android simulator getting started
-Android wear simulator starts at first and IF we close that ANdroid phone simulator is getting started but still Workbook is unable to connect to simulator for inspection
-Android phone simulator must get started
We'll look into filtering out Android Wear simulators.
"Also if we have already the simulator and then launched workbook , We are still getting Unable to connect."
Can you specify what simulator you are using here, and provide the logs for the session where you try only this approach?
Created attachment 22456 [details]
Logs for the scenario when Simulator is ON and then launched WORKBOOK
I have attached the logs for the specific scenario you have mentioned above.
We are using google emulators. Please go through the screen cast link -https://www.screencast.com/t/MToDaZoO
Changing the status of the defect to NEW
It looks like your test device is out of internal storage space.
[Error][00:00:17.1975786] AgentProcessManager<AndroidAgentProcess> (StartAsync): StartAsync: System.AggregateException: One or more errors occurred. ---> Mono.AndroidTools.InstallFailedException: Unexpected install output: Error: java.lang.IllegalStateException: ☃Requested internal only, but not enough space
at Mono.AndroidTools.Internal.AdbOutputParsing.CheckInstallSuccess(String output, String packageName)
> We are using google emulators. Please go through the screen cast link
1) Your screencast does not give all the details of the Android emulator. I do not know what API level it is.
2) Details like this should always be provided textually in the bug. This aids searching and reading comprehension and saves time. Bugs are read much more often than they are written.
Aside: It would be great if your team could switch to a screencast tool that does not require Flash when viewing in the browser. It is extra work in modern browsers to enable Flash.
Because this is an enhancement request and the 15.3 target milestone is mostly closed for additions at this time, I will update the target milestone to the next milestone 15.4 for further discussion.