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 or GitHub 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 21255 [details]
Contains IDE logs also gist of application output is attached in comment
-Unable to hit breakpoint in PCL VesselService.cs file given in Android.Debugging project in sample "CrossPlatformDebugging"
Verified on both Sierra and El capitan with the Build version given below
=== Visual Studio for Mac Preview ===
Version Preview 6 (7.0 build 2710)
Installation UUID: a676468e-a063-44dc-9eb6-9787862f31d7
Mono 18.104.22.168 (2017-02/dda961c) (64-bit)
GTK+ 2.24.23 (Raleigh theme)
Package version: 500000042
=== NuGet ===
=== Xamarin.Profiler ===
'/Applications/Xamarin Profiler.app' not found
=== Apple Developer Tools ===
Xcode 8.0 (11246)
=== Xamarin.Android ===
Version: 22.214.171.124 (Visual Studio Enterprise)
Android SDK: /Users/globallogic/Library/Developer/Xamarin/android-sdk-macosx
Supported Android versions:
4.4 (API level 19)
4.4.87 (API level 20)
6.0 (API level 23)
7.1 (API level 25)
SDK Tools Version: 25.2.5
SDK Platform Tools Version: 25.0.4
SDK Build Tools Version: 25.0.1
Java SDK: /usr
java version "1.8.0_101"
Java(TM) SE Runtime Environment (build 1.8.0_101-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.101-b13, mixed mode)
Android Designer EPL code available here:
=== Xamarin.iOS ===
Version: 10.10.0.0 (Visual Studio Enterprise)
Build date: 2017-04-04 16:48:23-0400
=== Xamarin.Mac ===
Version: 126.96.36.199 (Visual Studio Enterprise)
=== .NET Core ===
Runtime: Not installed
SDK: Not installed
MSBuild SDKs: /Library/Frameworks/Mono.framework/Versions/5.0.0/lib/mono/msbuild/15.0/bin/Sdks
=== Xamarin Inspector ===
Build date: Thu, 16 Feb 2017 18:57:39 GMT
=== Build Information ===
Release ID: 700002710
Git revision: 85d6914d5975d868f89503b940a9a5d1f433963c
Build date: 2017-04-04 20:45:31-04
Xamarin addins: 393161ecace6de5aa9d85ce62b4a26b26c594c07
Build lane: monodevelop-lion-d15-2
=== Operating System ===
Mac OS X 10.11.6
Darwin NAG1-DMAC-N07193 15.6.0 Darwin Kernel Version 15.6.0
Thu Jun 23 18:25:34 PDT 2016
Steps to reproduce
1)Open Project QualityAssurance/Manual/CrossPlatformDebugging/CrossPlatformDebugging.sln
2) Open the project properties on Android.Debugging, uncheck to disable 'Bundle assemblies into native code'
3) Delete bin and obj folders from
4) Set Breakpoint in PCLCustomerSample>Services in VesselService.cs file on line 38
5) Deploy to Android Device (Google Nexus 7)
6) Determine if breakpoint is hit on line 38
7) Stop debugging session
8) Delete bin and obj folders from
9) Set Breakpoint in XamFormsTestAp in VesselService.cs file on line 73
10) Deploy to Android Device (Google Nexus 7)
11) Click Vessel 1 in App on phone
12) Determine if breakpoint is hit on line 73
Observation - Breakpoint is not getting Hit on Line number 38 and 73. Unable to hit breakpoint in VesselService.cs file given in Android.Debugging project
Stack trace attached contains logs
I think problem is on XA side because doing `adb shell ls /storage/emulated/0/Android/data/com.companyname.android.debugging/files/.__override__/` shows that Portable .pdb is not copied... Disabling "Fast Assembly Deployment" fixed it for me... My wild guess is... problem is in https://github.com/xamarin/androidtools/blob/ff1b3d6f2351fa925b46289beb0efcd6b935299a/Xamarin.AndroidTools/Sessions/AndroidDeploySession.cs#L482
@David: What XA version are you using? Is it d15-2/Xamarin.Android 7.3.0?
My current understanding is that Xamarin Studio uses/will use Xamarin.Android's `Install` target -- which brings it inline with Visual Studio, and reduces duplicate code (yay!) -- and thus that `AndroidDeploySession` is not the entire picture.
The `Install` target uses the `<InstallPackageAssemblies/>` task, which explicitly checks for `.pdb` files for installation:
Additionally, when I use monodroid/master's `Install` target, the `.pdb` file *is* installed:
> $ xbuild /t:Install /v:diag Android.Debugging.csproj
> $ adb shell ls -l /storage/emulated/0/Android/data/com.companyname.android.debugging/files/.__override__ | grep pdb
> -rw-rw---- 1 u0_a211 sdcard_rw 6872 2017-04-10 11:18 Android.Debugging.pdb
> -rw-rw---- 1 u0_a211 sdcard_rw 5436 2017-04-10 11:18 XamFormsTestApp.Data.pdb
This is also using system mono 4.9.3:
> $ mono --version
> Mono JIT compiler version 4.9.3 (2017-02/c52c4bd Mon Mar 6 18:14:39 EST 2017)
Note: I was *not* able to build+install Android.Debugging.csproj using Xamarin Studio 6.3 (build 858); it reported an error in the `<ResolveAssemblyReference/>` task.
Neither Peter Collins nor I am able to repro this issue.
I am still able to reproduce this issue on the latest VSFM build (2770).
I am not able to hit the Breakpoint explicitly on last three cases mentioned on Android debugging project. Just to be explain it in details. under Android Debugging projects we have around 25 cases which need to be validated for breakpoints. Out of this 25 sample test cases the last three cases where failing for breakpoint.
Below is the github link for sample project consisting of fail 3 sample cases.
Note: On Previous XS build for MAC (i.e before 2710), above breakpoints were getting hit for the same github sample
Cloning the repositories on to different path fixed the issue. Hence marking this issue as Resolved fixed.
I'm going to update as NOT_REPRODUCIBLE I think, as that more accurately describes the investigation. The affected sample has been uploaded to slack, but I still was unable to manage a reproduction on both a Nexus 5x and Oneplus One.
The only _potentially_ relevant differences in this test case were:
* Fastdev was disabled
* Shared runtime was disabled
* The Debug property group was missing an `AndroidSupportedAbis` declaration. However to my best of my knowledge the armeabi-v7a value will be used as a default in this case either way.