Bug 56797 - Workbooks client should notify user when Android device is out of space
Summary: Workbooks client should notify user when Android device is out of space
Status: CONFIRMED
Alias: None
Product: Workbooks & Inspector
Classification: Xamarin
Component: Agent: Android ()
Version: 1.2.2
Hardware: PC Windows
: Low enhancement
Target Milestone: 1.4
Assignee: xamarininteractive
URL:
Depends on:
Blocks:
 
Reported: 2017-05-24 11:41 UTC by Gaurav Ganorkar
Modified: 2017-09-11 17:26 UTC (History)
4 users (show)

Tags: Globallogic
Is this bug a regression?: No
Last known good build:


Attachments
Inspector logs (9.39 KB, application/x-zip-compressed)
2017-05-24 11:41 UTC, Gaurav Ganorkar
Details
Logs for the scenario when Simulator is ON and then launched WORKBOOK (2.32 KB, application/x-zip-compressed)
2017-05-25 12:29 UTC, Gaurav Ganorkar
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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 original description:

  • Export the original title and description: Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.
Related Links:
Status:
CONFIRMED

Description Gaurav Ganorkar 2017-05-24 11:41:01 UTC
Created attachment 22418 [details]
Inspector logs

Description
-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.

Build info
-Microsoft Visual Studio Enterprise 2017 d15svc
Version 15.2 (26430.10) d15svc d15svc
VisualStudio.15.int.d15svc/15.2.0+26430.10.d15svc
Microsoft .NET Framework
Version 4.7.02046

Installed Version: Enterprise

Xamarin 4.5.0.475 (70f1268)
Xamarin.Android SDK 7.3.1.1 (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 


Actual
-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

Expected
-Android phone simulator must get started 

ScreenCast link
-https://www.screencast.com/t/NDuduBE1iHV

Reproducible
-50% 

Attached logs
Comment 1 Sandy Armstrong [MSFT] 2017-05-24 13:34:53 UTC
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?
Comment 2 Gaurav Ganorkar 2017-05-25 12:29:19 UTC
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.
Comment 3 Gaurav Ganorkar 2017-05-25 12:30:44 UTC
We are using google emulators. Please go through the screen cast link -https://www.screencast.com/t/MToDaZoO
Comment 4 Gaurav Ganorkar 2017-05-25 12:31:46 UTC
Changing the status of the defect to NEW
Comment 5 Sandy Armstrong [MSFT] 2017-05-25 15:57:04 UTC
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)
Comment 6 Sandy Armstrong [MSFT] 2017-05-25 16:03:44 UTC
> 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.
Comment 7 Brendan Zagaeski (Xamarin Team, assistant) 2017-07-05 20:35:54 UTC
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.