Bug 13554 - Getting "System.Reflection.TargetInvocationException" when user click on Value field in Watch window
Summary: Getting "System.Reflection.TargetInvocationException" when user click on Valu...
Status: VERIFIED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: 4.0.10
Hardware: All All
: Normal normal
Target Milestone: 4.2.x
Assignee: Jeffrey Stedfast
URL:
Depends on:
Blocks:
 
Reported: 2013-07-29 06:11 UTC by Nischal
Modified: 2015-06-30 01:19 UTC (History)
7 users (show)

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

Related Links:
Status:
VERIFIED FIXED

Description Nischal 2013-07-29 06:11:25 UTC
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.

Supplement info:
http://screencast.com/t/0CTgHmsP3A9a
https://gist.github.com/saurabh360/24c345427521057c24d4

Environment details:
All Mac and Windows
X.S 4.1.8(build 8)
Mono 3.2.1
Xamarin.Android 4.8.0-13

Regression Status:
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
Comment 1 Saurabh 2013-07-29 11:56:38 UTC
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.
Comment 2 Jeffrey Stedfast 2013-07-29 13:00:31 UTC
fixed in git master
Comment 3 PJ 2013-07-29 15:09:12 UTC
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.
Comment 4 Mohit Kheterpal 2013-09-17 07:21:15 UTC
We are getting same issue with Following builds:

XS 4.0.13(build 28)
Mono 3.2.3 ((no/8d3b4b7)
MT  7.0.0.9
Comment 5 PJ 2013-09-20 13:25:35 UTC
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.
Comment 6 PJ 2013-11-19 16:32:24 UTC
This bug was targeted for a past milestone, moving to the next active milestone.
Comment 7 Jeffrey Stedfast 2015-03-17 12:28:33 UTC
closing since we're long past 4.1.8
Comment 8 Prashant manu 2015-06-30 01:19:29 UTC
This issue is working fine and hence closing this issue.

Environment Info:
Xamarin Studio
Version 5.9.4 (build 5)