Bug 29825 - Fragment.Instantiate not working.
Summary: Fragment.Instantiate not working.
Alias: None
Product: Android
Classification: Xamarin
Component: Mono runtime / AOT Compiler ()
Version: 5.1
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Jonathan Pryor
Depends on:
Reported: 2015-05-07 06:57 UTC by Dharmender Sharma
Modified: 2017-09-14 18:44 UTC (History)
3 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 Dharmender Sharma 2015-05-07 06:57:49 UTC
I have a fragmentpageradapter and i am adding a fragment in page adapter using Fragment.Instantiate method.
My fragment is of Xamarin.Android.Support.V4.App.fragment type.

Its giving me error :"Unable to instantiate fragment com.*.FragmentContact$1: make sure class name exists, is public, and has an empty constructor that is public" .
Comment 1 Jonathan Pryor 2015-05-07 11:35:59 UTC
Please provide a complete repro. I don't know how to reproduce this issue.

Furthermore, the error message doesn't make sense: `FragmentContact$1` implies use of an anonymous inner class, and nothing in our toolchain generates anonymous inner classes.
Comment 2 Jon Douglas [MSFT] 2017-09-14 18:44:10 UTC
Because we have not received a reply to our request for more information we are closing this issue. If you are still encountering this issue, please reopen the ticket with the requested information. Thanks!