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.
After building a UITest script, the "Submit to Test Cloud" option is not longer present within Visual Studio, using VS 2017
# Steps to Reproduce
1. Create an app
2. Add a UITest project
4. Right click on UITest
# Expected Results
Submit to Test Cloud should be present
# Actual Results
Submit to Test Cloud is not present
Microsoft Visual Studio Enterprise 2017 RC
Version 15.0.26020.0 D15REL
Microsoft .NET Framework
Installed Version: Enterprise
Architecture Diagrams and Analysis Tools 00369-50000-00000-AA792
Microsoft Architecture Diagrams and Analysis Tools
Visual Basic 2017 RC 00369-50000-00000-AA792
Microsoft Visual Basic 2017 RC
Visual C# 2017 RC 00369-50000-00000-AA792
Microsoft Visual C# 2017 RC
Visual C++ 2017 RC 00369-50000-00000-AA792
Microsoft Visual C++ 2017 RC
Visual F# 4.1 00369-50000-00000-AA792
Microsoft Visual F# 4.1
Application Insights Tools for Visual Studio Package 8.4.01118.2
Application Insights Tools for Visual Studio
ASP.NET and Web Tools 2016 15.0.21206.0
ASP.NET and Web Tools 2016
Command Bus, Event Stream and Async Manager Merq
Provides ICommandBus, IEventStream and IAsyncManager MEF services for loosely coupled Visual Studio extension components communication and integration.
Common Azure Tools 1.8
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.
Microsoft Visual Studio VC Package 1.0
Microsoft Visual Studio VC Package
Mono Debugging for Visual Studio Mono.Debugging.VisualStudio
Support for debugging Mono processes with Visual Studio.
NuGet Package Manager 4.0.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/.
TypeScript tools for Visual Studio
Visual Studio Tools for Universal Windows Apps 15.0.26009.00
The Visual Studio Tools for Universal Windows apps allow you to build a single universal app experience that can reach every device running Windows 10: phone, tablet, PC, and more. It includes the Microsoft Windows 10 Software Development Kit.
Xamarin 188.8.131.529 (7c3dcf2)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.
Xamarin.Android 184.108.40.206 (72366f7)
Visual Studio extension to enable development for Xamarin.Android.
Xamarin.iOS 10.4.0.33 (d93ae7e)
Visual Studio extension to enable development for Xamarin.iOS.
We will re-add this back ASAP.
Fixed in version 220.127.116.114 (master)
Commit: 5e2e85d7a518e732b06c54de21273e3aee1b4491 (xamarin/XamarinVS)
Where Can a get version 18.104.22.1684 (master) for VS 2017.As per my knowledge we access VS 2017 through VPN
Created attachment 20677 [details]
Bug is verified and retested in below build environment:
- Microsoft Visual Studio Enterprise 2017 Preview (2)
- Version 15.1 (26321.1-Preview) d15rel Preview
- Microsoft .NET Framework Version 4.6.01586
- Xamarin 22.214.171.124 (1878e36)
- Xamarin.Android SDK 126.96.36.199 (b8e3884)
- Xamarin.iOS and Xamarin.Mac SDK 10.8.0.26 (0e9e791)
Actual result-As discussed with Ben Beckley on slack Run in Test Cloud phrasing is correct and the fix the for the bug.but for above build configuration, Run in Test Cloud option is not present
Created attachment 20678 [details]
Run in test Cloud option is missing in 2017
Pleas refer the attached log and image.Hence Reopening the bug
## Regression and verification status: regression in Cycle 9 compared to Cycle 8 SR 2, verified fixed on "15.1" target milestone _except_ in Visual Studio 2017
> BAD: XamarinVS 188.8.131.52 (80d9a02) "15.1" in VS 2017 (26401.1-Preview)
> GOOD: XamarinVS 184.108.40.206 (511c8b5) "15.1" in VS 2015 Update 3
> BAD: XamarinVS 220.127.116.114 (73f58d6) "Cycle 9" in VS 2015 Update 3
> GOOD: XamarinVS 18.104.22.168 (00fa5cc) "Cycle 8 SR 2" in VS 2015 Update 3
Installed VS2017.2, the voice menu is still missing
Installed VS2017.2, the menu item is still missing
Thanks so much for taking the time to submit this report! I can confirm using the latest Visual Studio 15.3 preview builds I am able to reproduce this issue. Marking this report as CONFIRMED.
Missing for me as well, VS 2017 Enterprise 15.2
Xamarin.Android SDK 22.214.171.124
Xamarin.IOS and Xamarin.Mac SDK 10.10.0.37
The "Run in Test Cloud" shortcut no longer being included in Visual Studio 2017 is an intended change. The best way to deploy UITests to Test Cloud is via the command line:
We're working on updating our documentation to reflect this for Visual Studio on Windows. Thanks!
can I ask why this menu item has been removed only from Visual Studio for PC and not for Mac?
Also: as you can see by the number of comments, this issue was really helpful.
Is there an user voice to ask its reintroduction?
P.S: the documentation refers to the device parameter in this way:
--devices <DEVICE ID>: The device ID that was provided in the Test Cloud Upload dialog.
If there is no UI, how can we calculate this parameter?!?
@Curia: You will need to create a Test Run on the Test Cloud website - https://developer.xamarin.com/guides/testcloud/organizations-and-teams/creating-a-test-run/. This is a wizard that will allow you to select the devices for your test run and then generate a DEVICE_ID parameter based on the devices selected.
Note that you can share the DEVICE_ID between projects/test runs; it s not necessary to create a new DEVICE_ID each time you want to run tests.
Understood now. Thank you!
But still I miss the Visual Studio menu item :-)