Created attachment 13908 [details]
In a very simple test project, placing a breakpoint in an XUnit test causes the test runner app to hang.
## Steps to reproduce
1. Load the attached test project into Visual Studio.
2. Place a breakpoint on the Assert line in BreakpointRepro.Test.cs some_test() method.
3. Launch the BreakpointRepro.Droid app to a simulator or device.
4. Run the test from the app
Expected result: Breakpoint in some_test() method will be hit.
Actual result: Breakpoint is never hit and app hangs with constant spinning activity indicator (or sometimes indicator does not spin but is frozen).
I noted that the Forms version was different in each project, 1.3.3 in the PCL and 1.5.0 in the app project. Changing both to be version 1.5.0 did not affect the issue, nor did updating to Forms 2.0.0 in both projects.
I also confirmed both project are being built in all configurations.
Customer reports this worked until updating to the C6 base builds currently in the Stable Channel.
## Version info (mine)
Microsoft Visual Studio Professional 2015
Version 14.0.23107.0 D14REL
Microsoft .NET Framework
Installed Version: Professional
Visual Basic 2015 00322-40000-00000-AA850
Microsoft Visual Basic 2015
Visual C# 2015 00322-40000-00000-AA850
Microsoft Visual C# 2015
Visual C++ 2015 00322-40000-00000-AA850
Microsoft Visual C++ 2015
Visual F# 2015 RC 00322-40000-00000-AA850
Microsoft Visual F# 2015 RC
Windows Phone SDK 8.0 - ENU 00322-40000-00000-AA850
Windows Phone SDK 8.0 - ENU
Application Insights Tools for Visual Studio Package 1.0
Application Insights Tools for Visual Studio
ASP.NET and Web Tools 14.0.20626.0
ASP.NET and Web Tools
ASP.NET Web Frameworks and Tools 2013 5.2.30624.0
For additional information, visit http://www.asp.net/
Common Azure Tools 1.5
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.
Generates unit test code for methods in classes under test.
A Visual Studio Extension that brings the GitHub Flow into Visual Studio.
Microsoft Azure Mobile Services Tools 1.4
Microsoft Azure Mobile Services Tools
NuGet Package Manager 3.2.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/.
PreEmptive Analytics Visualizer 1.2
Microsoft Visual Studio extension to visualize aggregated summaries from the PreEmptive Analytics product.
SQL Server Data Tools 14.0.50616.0
Microsoft SQL Server Data Tools
Visual Studio Tools for Universal Windows Apps 14.0.23309.00 d14oob
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 (f860fe4)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.
Xamarin.Android 184.108.40.206 (3efa14c)
Visual Studio plugin to enable development for Xamarin.Android.
Xamarin.iOS 220.127.116.11 (3c0ec35)
Visual Studio extension to enable development for Xamarin.iOS.
Any updates on this?
We are also looking for updates on this. Is there a workaround?
Assigning the issue for investigation. We'll add more info tomorrow based on results.
I have a successful repro. Looking for a fix.
I have not found the root cause for the issue and have a working fix. I'm trying to improve it a little, but this should be fixed soon. I'll keep the thread updated.
Potential fix for public use: http://xvs.xamarin.com/patcheddrops/Xamarin.VisualStudio_18.104.22.168.msi
Please note that this an untested build that may introduce other issues. If you do install, please let us know if it works or not.
Seems to work: https://github.com/xunit/devices.xunit/issues/29#issuecomment-190837363
For me the installer above fixed the issue... Is this fix included in the 22.214.171.124 beta release?
This fix is not included in 126.96.36.199 because it didn't make the testing deadline. If you need 188.8.131.52 with this included please do tell and I'll create a hotfix for it.
I would really appreciate a new hotfix based on 184.108.40.206... Thanks for your help.
We need to get this into the stable release before Evolve at the very least. I have a talk on cross-platform unit testing with xUnit and this part needs to work :)
I will make sure to let the correct people now. Evolve shouldn't be a problem (and it will be awesome, as always :)). That said, this issue only manifests if you manually edit the csproj and add AssemblyName on configuration groups, so it shouldn't be a blocker.
The hotfix is being built. I'll update as soon as it's done.
Dismiss my last comment, wrong bug :S. Still building for this.
This is a version of 145 + the fix for this issue: xvs.xamarin.com/patcheddrops/Xamarin.VisualStudio_220.127.116.11.msi
As always, this version is completely untested and should be used at your own risk. You can always revert to .145 if it doesn't work for you.
Did this make it into the .147 stable release? I don't see any mention of it on the release notes page: https://releases.xamarin.com/xamarin-studio-and-xamarin-vs-stable-hotfix-for-debugging-of-ios-6-7-devices/
The candidate fix is _not_ yet included in the current Stable channel version XamarinVS 18.104.22.168.
In this case the version number of "22.214.171.124" from Comment 17 is (a bit confusingly) not comparable to the Stable channel releases because the untested build from Comment 17 was built from a separate source code branch.
## Target milestone Cycle 7
The candidate fix _is_ included in the current Cycle 7 Preview version available on the Alpha channel. I will update the target milestone and resolution status accordingly.
So if I need to use this in demo's during Xamarin Evolve, what should I do? Will 4.1 be stable by then?
I have sent a follow-up to Comment 20 via email. The short summary is that the release calendar for April is under planning and additional information will be made available as soon as possible.
Fixed in version 126.96.36.199 (cycle6)
Author: Jose Gallardo
Commit: e7da20816dc45bc8a9f2b8609bfa0b2c0993ebb2 (xamarin/XamarinVS)