Bug 10915 - ConfigChanges enum: Bitwise operation on enum which is not marked by [Flags] attribute
Summary: ConfigChanges enum: Bitwise operation on enum which is not marked by [Flags] ...
Alias: None
Product: Android
Classification: Xamarin
Component: BCL Class Libraries ()
Version: 4.8.x
Hardware: PC Windows
: Highest normal
Target Milestone: ---
Assignee: Radek Doulik
Depends on:
Reported: 2013-03-05 12:00 UTC by Kirk Woll
Modified: 2014-03-27 11:38 UTC (History)
4 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 Kirk Woll 2013-03-05 12:00:08 UTC
The enum Android.Content.PM.ConfigChanges is clearly intended to be used as a composable set of flags (hence the fact they increase by a power of two).  However, this enum is not marked with the [Flags] attribute, thus eliciting the error message:  

Bitwise operation on enum which is not marked by [Flags] attribute

I suspect this message is coming from ReSharper, but in any case, the enum should have that attribute added.
Comment 1 Miguel de Icaza [MSFT] 2013-05-22 15:15:17 UTC
Assigning to Atsushi.

Atsushi, this is one of the few enums that do not have the "Flags" on their name, but is a Flags.
Comment 2 Radek Doulik 2013-06-11 09:38:14 UTC
It is fixed in master and will be available in the next alpha release.
Comment 3 Udham Singh 2014-03-27 11:38:29 UTC
I have checked this issue on following builds:

Windows 8.1
Xamarin Studio : 4.2.3 (build 60)
Xamarin.Android: 4.13.0 (Business Edition)

Screencast: http://screencast.com/t/fyfO2x1bW

Now this issue is working fine, Hence I am closing this issue.