Bug 23426 - Breakpoints not hit in PCL called from iOS app
Summary: Breakpoints not hit in PCL called from iOS app
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 3.11 (C5)
Hardware: PC Mac OS
: Normal normal
Target Milestone: 4.3.1 (C9SR1)
Assignee: Joaquin Jares
Depends on:
Reported: 2014-09-26 19:04 UTC by Kent Green [MSFT]
Modified: 2017-05-29 14:15 UTC (History)
12 users (show)

Is this bug a regression?: ---
Last known good build:

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

Related Links:

Description Kent Green [MSFT] 2014-09-26 19:04:54 UTC
From this priority desk case:

In Xamarin Studio (but not Visual Studio); set breakpoints aren't being hit in the PCL when called from an iOS app. Instead, Xamarin Studio is unable to resolve the breakpoints.

---Steps to Reproduce---
(Note: Sample is from a customer's project, so will be added as a private attachment after posting this description.)

1) Set breakpoints within the MyEntry.cs file within the PCL in the sample app.
2) Run the app.
3) Breakpoints not hit; but are unresolved.

---Build Information---
=== Xamarin Studio ===

Version 5.5 (build 198)
Installation UUID: 8ef63a7c-1b18-40de-a334-7f78777fcb55
	Mono 3.10.0 ((detached/ac51002)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 310000016

=== Apple Developer Tools ===

Xcode 6.0.1 (6528)
Build 6A317

=== Xamarin.iOS ===

Version: (Business Edition)
Hash: 973f8d4
Build date: 2014-09-17 17:40:20-0400

=== Xamarin.Android ===

Version: (Business Edition)
Android SDK: /Users/kentgreen/Library/Developer/Xamarin/android-sdk-macosx
	Supported Android versions:
		2.1   (API level 7)
		2.2   (API level 8)
		2.3   (API level 10)
		3.1   (API level 12)
		4.0   (API level 14)
		4.0.3 (API level 15)
		4.1   (API level 16)
		4.2   (API level 17)
		4.3   (API level 18)
		4.4   (API level 19)
Java SDK: /usr
java version "1.6.0_65"
Java(TM) SE Runtime Environment (build 1.6.0_65-b14-466.1-11M4716)
Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-466.1, mixed mode)

=== Xamarin.Mac ===

Version: (Business Edition)

=== Build Information ===

Release ID: 505000198
Git revision: 7495942eb76d6b80c460ddd61f2b94cba1a97fa2
Build date: 2014-09-18 09:50:12-04
Xamarin addins: c571b625445d60f2c8b189b309a6ffc87386caed

=== Operating System ===

Mac OS X 10.9.4
Darwin Kents-MacBook-Pro.local 13.3.0 Darwin Kernel Version 13.3.0
    Tue Jun  3 21:27:35 PDT 2014
    root:xnu-2422.110.17~1/RELEASE_X86_64 x86_64
Comment 4 Dominic N [MSFT] 2014-10-01 11:55:45 UTC
Received the following additional information from the priority customer who reported this case:

He indicates that everything works well if you develop on Xamarin Studio on Windows and then on the Mac, but that there are issues moving from Visual Studio to Xamarin Studio on the Mac.

In Xamarin Studio on Windows, he can create an Android project, move it over to the Mac and add an iOS project in Xamarin Studio there. This results in working bindings for devices.

Projects created in Visual Studio 2013 in Windows do not seem to be compatible with Xamarin Studio on the Mac. To reproduce this, create a blank project in Visual Studio 2013 and try to load it on the Mac. It seems there is an issue in the solution bindings (project files and sln files).

Customer's version information will be included in a subsequent private post.
Comment 6 Jeffrey Stedfast 2014-10-01 12:45:55 UTC
Reassigning to the VS team since the problem seems to be that the VS addin is breaking something.
Comment 7 Brendan Zagaeski (Xamarin Team, assistant) 2014-10-01 13:17:32 UTC
I think the wording of comment 4 might be confusing this issue. The original description comment 0 was on Xamarin Studio on Mac. Both I and Kent were able to reproduce the problem on Xamarin Studio on Mac, but _not_ in Visual Studio on Windows.

If there is an issue in Visual Studio, then it's a different bug.

So that said, would this still be an issue in the VS addin?
Comment 8 Brendan Zagaeski (Xamarin Team, assistant) 2014-10-01 13:28:55 UTC
Oh, wait. I think I understand. If the template project in VS has a funny setting in it, it could be causing an issue during the build in Xamarin Studio on Mac so that debug symbols aren't created as expected, or something like that.
Comment 9 Jeffrey Stedfast 2014-10-01 14:18:47 UTC
yep, exactly.
Comment 10 Andrew 2014-10-01 14:20:48 UTC
I created a new Portable Mobile Solution in VS.  Blank.  default settings and files.  when to open it in XS on the MAC and it would not recognize the ipad connected.  would not build properly.  this was an new solution.  I am spending the day resolving issues between windows and mac :(
Comment 11 Andrew 2014-10-01 17:57:40 UTC
It was something in the project or solution files that caused all the problems with the breakpoints and locking up the solution in the MAC.  We have almost completed the rebuild of the project and the errors have disappeared.  I have no idea what caused it and probably never know.  The project and solution files were very corrupt.
Comment 14 Jose Gallardo 2016-12-27 21:49:01 UTC
Updating the target milestone. We've already fixed our PCL templates as part of C9, and we'll double check if there is anything missing from our side regarding this issue.

Comment 15 Joaquin Jares 2017-05-29 14:15:51 UTC
Templates have completely changed and this bug doesn't repro anymore. Marking as fixed for verification.