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.
[VS 2012, VS 2013] "Tools > iOS > Device Log..." menu item is always displayed and disabled, but it doesn't directly indicate a reason why
## Regression status: not a regression, but it is a _new_ behavior of new feature
## Steps to replicate
1. Install Xamarin Cycle 8 on Windows.
2. Open Visual Studio 2012 or Visual Studio 2013 (tested with VS 2013 Update 3).
3. Open an iOS project.
4. Allow Visual Studio to connect to a Mac build host with an iOS device attached.
5. Click the "TOOLS" menu and navigate to "iOS".
The "Device Log..." entry is always displayed but it is also always disabled (grayed out).
## Possible improvements
A. Change the wording of the "Device Log..." entry on Visual Studio 2012 and 2013 to indicate that the feature is only available on Visual Studio 2015?
Perhaps something like:
"Device Log... (requires VS 2015)"
B. Remove the menu entry "Device Log..." from Visual Studio 2012 and 2013.
My rough suspicion is that (B) might be more consistent with other UI element differences across Visual Studio versions, but keeping the deactivated menu item (A) is also sort of nice in some ways because users on older versions might otherwise ask why that menu item doesn't appear for them. From my personal perspective, I think I'd be ok with either approach.
This should be already resolved in C9 since the DeviceLog feature should not be included at all in the final extension bundle if VS < dev14. If you can still see the command please let know.
I have checked this issue with latest build of C9 i.e. XVS 188.8.131.527 _ 526a008aede9e857a169ac2d0e1411a30d746c87 on lane 'xvs-win-cycle9' and observed that this issue still exist as shown in screencast : https://www.screencast.com/t/cvLaGZvb9quv
I have checked it with C8 build i.e. 184.108.40.206 and observed the same behaviour as I have mentioned in screencast.
As of now I am reopening this issue, please let me know with which build version of C9 this issue has been fixed.
Fixed in version 220.127.116.117 (master)
Author: Adrian Alonso
Commit: 400becb388e835789115fd6a6c0fda01fd6b7fcd (xamarin/XamarinVS)
Fixed in version 18.104.22.1681 (cycle9)
Author: Adrian Alonso
Commit: 2136747d6ce129c4d175635a94d81bbc7ac81cc9 (xamarin/XamarinVS)