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.
Step to reproduce:
1. Open Xamarin.Facebook android sample in XS
2. Set its Target Framework to 'Android 3.1(Honeycomb)' or above (like: Android 4.0, Android 4.0.3)
3. Build or Run the application
Application gives build error with Target Framework 'Android 3.1(Honeycomb)' and above. However, with Target Framework Android 2.2 and Android 2.3 application build and deploy successfully.
Application should build and deploy successfully with Target Framework 'Android 3.1(Honeycomb)' and above.
Build error: https://gist.github.com/AkhileshKumar01/e7bca83e3eeb6513f860
Mac Loin, ML and Mavericks
X.S 4.0.11(build 7)
Regression status: This issue also exist with stable mono-android-4.8.0-13-2.
Bumping the Target Framework on this particular sample causes the FragmentManager usage to become ambiguous, as FragmentManager exists in both `Android.App.FragmentManager' and `Android.Support.V4.App.FragmentManager'. Since this sample is referencing the support4 version, and the Android.App version wasn't implemented until API 11, this sample will fail to build when increasing the target framework.
Unfortunately, changing the Target Framework for this specific sample is not a valid test-case.