Bug 4774 - Error/Warning count does not change even though issues are fixed
Summary: Error/Warning count does not change even though issues are fixed
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Android Add-in ()
Version: unspecified
Hardware: Macintosh Mac OS
: Low normal
Target Milestone: ---
Assignee: Greg Munn
: 2579 ()
Depends on:
Reported: 2012-04-30 15:43 UTC by Chris Hardy [MSFT]
Modified: 2016-07-18 20:29 UTC (History)
7 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 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:

Description Chris Hardy [MSFT] 2012-04-30 15:43:25 UTC
Sometimes you will get a package error which will increase the error count in a Mono for Android project, except that when the package error is resolved, the error count does not decrease even though the issue is fixed. So even though the project builds and runs, the error icons still show 1 or more errors which is confusing.

Cannot reproduce but it does randomly happen when working with Mono for Android projects.
Comment 1 Jonathan Pobst 2012-04-30 15:53:46 UTC
My gut says this has something to do with MonoDevelop xbuild integration, since Mono for Android is currently the ~only project type that we build with xbuild instead of MonoDevelop's internal build logic.
Comment 2 Richard Bennett 2012-04-30 16:01:52 UTC
This can be triggered by adding a .java file to a MonoDroid project, using the AndroidJavaSource build type. If the .java file has errors, this will always trigger the "undying error" behaviour. New errors on subsequent builds are added to the bottom of the error list, with old errors not removed...

.. i.e. if your .java source has one error, the error counter will increment by one every time you build the package.

Note that the java sources are not processed in a standard "build", but rather only when producing the .apk.
Comment 3 Mikayla Hutchinson [MSFT] 2012-04-30 16:30:54 UTC
Looks like a dup of bug 2579?
Comment 4 Chris Hardy [MSFT] 2012-04-30 16:37:59 UTC
Yeah, that seems to be the same issue, I'd mark that one as a dupe of this one as this has a lot more useful info, wouldn't be surprised if there's one or two others that are similar.
Comment 5 Mikayla Hutchinson [MSFT] 2012-04-30 17:39:02 UTC
*** Bug 2579 has been marked as a duplicate of this bug. ***
Comment 6 Mikayla Hutchinson [MSFT] 2012-04-30 17:40:01 UTC
The M4A addin is adding packaging errors directly to the error pad, it might be a bug in clearing those.
Comment 7 Jonathan Pobst 2012-04-30 17:41:15 UTC
Yes, given Richard's repro steps, I think you are correct.
Comment 8 Greg Munn 2016-07-18 20:29:54 UTC
I've tried to reproduce and haven't been able to and given it's age and lack of further comments I'm going to assume that it was fixed in the 4 years since,