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.
Created attachment 23985 [details]
Sample showing issue
Set a breakpoint in the "TestClass" in the PCL. Set "Enable device-specific builds" to true in the iOS project. Debug to a iOS device, note that the breakpoints will not hit (breakpoints hit in the iOS project though, such as in the AppDelegate class)
Change "Enable device-specific builds" to false and run again, note that the PCL breakpoints hit.
Note: this is the same bug as 42359 but I couldn't figure out how to re open a bug, and this is for VS2017 instead of 2015.
Microsoft Visual Studio Community 2017
Version 15.2 (26430.16) Release
Microsoft .NET Framework
Installed Version: Community
Visual Basic 2017 00369-60000-00001-AA327
Microsoft Visual Basic 2017
Visual C# 2017 00369-60000-00001-AA327
Microsoft Visual C# 2017
Visual C++ 2017 00369-60000-00001-AA327
Microsoft Visual C++ 2017
Visual F# 4.1 00369-60000-00001-AA327
Microsoft Visual F# 4.1
Application Insights Tools for Visual Studio Package 8.6.00404.2
Application Insights Tools for Visual Studio
ASP.NET and Web Tools 2017 15.0.30503.0
ASP.NET and Web Tools 2017
Common Azure Tools 1.9
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.
A Visual Studio Extension that brings the GitHub Flow into Visual Studio.
Merq 1.1.17-rc (cba4571)
Command Bus, Event Stream and Async Manager for Visual Studio extensions.
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.2.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.26430.06
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 184.108.40.2066 (fec6f88)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.
Xamarin.Android SDK 220.127.116.11 (9dbc4c5)
Xamarin.Android Reference Assemblies and MSBuild support.
Xamarin.iOS and Xamarin.Mac SDK 10.10.0.37 (ad35de4)
Xamarin.iOS and Xamarin.Mac Reference Assemblies and MSBuild support.
Thanks for the test case and the additional observation about the effect of "Enable device-specific builds".
Overall the missing breakpoint behavior of the test case from Comment 0 matches Bug 56893, based on the confirmation and verification testing below. I will accordingly mark this bug as a duplicate.
## Confirmation and verification status of the test case from Comment 0: verified fixed on the "Xamarin 15.3 release" preview
> GOOD: XamarinVS 18.104.22.1685 (306f76a) + Xamarin.iOS 10.12.0.14 (d15-3: bf350ba5) + Visual Studio 2017 Preview version 15.3 Preview 7, "Xamarin 15.3 release" preview
> BAD: XamarinVS 22.214.171.1246 (fec6f88) + Xamarin.iOS 10.10.0.36 (d15-2: d2270eec) + Visual Studio 2017 version 15.2, "Xamarin 15.2.3 release"
Good results: The debugger pauses on the breakpoint as expected.
Bad results: The debugger does not pause on the breakpoint.
*** This bug has been marked as a duplicate of bug 56893 ***