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.
PackageManager.MatchDefaultOnly used to exist, but is now gone, seemed to have been there before 4.0.1.
Looks like in 1.6 - 2.3, it's:
In 3.1 and 4.0, it's:
Atsushi, can you look into why this is?
Its back to PackageInfoFlags.MatchDefaultOnly in 4.0.1! My code compiled before the 4.0.1 update ;-)
And it doesn't compile the following statement anymore as it's not "int" compatible:
That is due to missing int-to-enum mapping on android.content.pm.PackageManager.queryIntentActivities() 2nd. parameter.
We have a corresponding fix in our almost-complete enum change updates, but it would not be available until the next upgrade. So far, please explicitly cast it to int: myActivity.PackageManager.QueryIntentActivities(externalIntent, (int) PackageInfoFlags.MatchDefaultOnly).
(Closing as fixed as we have fix internally.)
Looks like this is happening again in 4.12.2 (or maybe before). No enums there, just string constants in PackageManager.
Nevermind, those constants are packed in PackageInfoFlags enum. Duh.