Bug 14112 - "Xamarin.Facebook" android sample gives build error with Target Framework 'Android 3.1(Honeycomb)' and above.
Summary: "Xamarin.Facebook" android sample gives build error with Target Framework 'An...
Status: RESOLVED NOT_ON_ROADMAP
Alias: None
Product: Android
Classification: Xamarin
Component: Samples ()
Version: 4.8.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Peter Collins
URL:
Depends on:
Blocks:
 
Reported: 2013-08-20 11:25 UTC by Saurabh
Modified: 2013-08-20 14:13 UTC (History)
0 users

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:
RESOLVED NOT_ON_ROADMAP

Description Saurabh 2013-08-20 11:25:16 UTC
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

Actual result:
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.

Expected result:
Application should build and deploy successfully with Target Framework 'Android 3.1(Honeycomb)' and above.

Supplement info:
Screencast: http://screencast.com/t/MSuRM6zTmGY
Build error: https://gist.github.com/AkhileshKumar01/e7bca83e3eeb6513f860

Environment details:
Mac Loin, ML and Mavericks
X.S 4.0.11(build 7)
Mono 3.2.2
X.Android 4.8.2-54

App info:
monodroid-sample-master- 5d63590ee1db0e221a45426f8bf8be3b7328535c

Regression status: This issue also exist with stable mono-android-4.8.0-13-2.
Comment 1 Peter Collins 2013-08-20 14:13:04 UTC
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.