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.
Steps to reproduce:
1. Open or create android application.
2. Go to View->Debug Window->Watch.
3. Click on value field.
Actual Result: Getting "System.Reflection.TargetInvocationException" when user click on value field under watch window.
Expected Result: No exception should displayed when user click on value under Watch window.
All Mac and Windows
X.S 4.1.8(build 8)
we are seeing same behavior with Stable X.S 4.0.10(build 7), X.S 4.0.9(build 12) and Stable Xamarin.Android 4.6.8, We are not sure weather this was working fine with previous builds or not
This issue does not exist with Stable XS 4.0.8(build 2)+ Mono 2.10.12 on both Mac and Windows environment.
However, we are getting same issue with XS 4.0.9(Stable) on both Mac and Windows environment.
fixed in git master
This looks like we want to get it into 4.1.8 / 4.0.next_from_master - if so that might need a backport. Moving to XS product.
We are getting same issue with Following builds:
XS 4.0.13(build 28)
Mono 3.2.3 ((no/8d3b4b7)
Watching variables still works when the debugger is connected, and it seems like not a regression from 4.0.9, so we won't block the 4.0.13 beta for this.
Also, while it looks bad, dismissing the errors and adding the watches during debugging is a workaround. We may not even block for stable.
This bug was targeted for a past milestone, moving to the next active milestone.
closing since we're long past 4.1.8
This issue is working fine and hence closing this issue.
Version 5.9.4 (build 5)