I need help regarding working on fragment inside fragment, actually I
am facing a problem on pressing back button. Application Main screen
has buttons and pressing on each button view replace with new
fragment(and that fragment contain inside another fragment),
dynamically adding/replacing fragment is working fine, by pressing
button1 fragment replaced, same happens when pressing button, but if
I press the button again, got an exception:

    &quot;Duplicate id 0x7f05000a, tag null, or parent id 0x7f050009 with
    another fragment for com........ fragmentname&quot;

 means fragment or inner fragments are already added and I am trying
to add them again, anybody has idea how to work with fragment inside
fragment and moving back and forth without any problem, thanks for the
support.

MainActivity, where fragments are dynamical added and
replaced.

```java
public class FragmentInsideFragmentTestActivity extends Activity {

    private Button button1;
    private Button button2;
    private Button button3;
    private Button button4;


    /** Called when the activity is first created. */
    @Override
    public void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        setContentView(R.layout.main);

        button1 =(Button) this.findViewById(R.id.button1);
        button1.setOnClickListener(new View.OnClickListener() {
           public void onClick(View view) {
               onButtonClick(view);
            }
        });

        button2 =(Button) this.findViewById(R.id.button2);
        button2.setOnClickListener(new View.OnClickListener() {
            public void onClick(View view) {
                onButtonClick(view);
            }
        });

        button3 =(Button) this.findViewById(R.id.button3);
        button3.setOnClickListener(new View.OnClickListener() {
            public void onClick(View view) {
               onButtonClick(view);
            }
        });

        button4 =(Button) this.findViewById(R.id.button4);
        button4.setOnClickListener(new View.OnClickListener() {
           public void onClick(View view) {
               onButtonClick(view);
           }
        });
    }

    public void onButtonClick(View v) {
        Fragment fg;

        switch (v.getId()) {
           case R.id.button1:
                   fg=FirstFragment.newInstance();
                   replaceFragment(fg);
                   break;
           case R.id.button2:
                   fg=SecondFragment.newInstance();
                   replaceFragment(fg);
                   break;
           case R.id.button3:
                   fg=FirstFragment.newInstance();
                   replaceFragment(fg);
                   break;
           case R.id.button4:
                   fg=SecondFragment.newInstance();
                   replaceFragment(fg);
                   break;
        }
    }

    private void replaceFragment(Fragment newFragment) {
       FragmentTransaction trasection = getFragmentManager().beginTransaction();

        if(!newFragment.isAdded()) {
            try {
                //FragmentTransaction trasection =
                getFragmentManager().beginTransaction();
                trasection.replace(R.id.linearLayout2, newFragment);
                trasection.addToBackStack(null);
                trasection.commit();
            } catch (Exception e) {
                // TODO: handle exception
                // AppConstants.printLog(e.getMessage());
            } else {
                trasection.show(newFragment);
            }
        }
    }
```

Here is Layout: main.xml

```xml
&lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot;?&gt;
&lt;LinearLayout
    xmlns:android=&quot;http://schemas.android.com/apk/res/android&quot;
    android:layout_width=&quot;fill_parent&quot;
    android:layout_height=&quot;fill_parent&quot;
    android:orientation=&quot;vertical&quot;&gt;

    &lt;LinearLayout
        android:id=&quot;@+id/linearLayout1&quot;
        android:layout_width=&quot;match_parent&quot;
        android:layout_height=&quot;wrap_content&quot;
        android:orientation=&quot;horizontal&quot;&gt;

        &lt;Button
            android:id=&quot;@+id/button1&quot;
            android:layout_width=&quot;wrap_content&quot;
            android:layout_height=&quot;wrap_content&quot;
            android:text=&quot;Button1&quot; /&gt;

        &lt;Button
            android:id=&quot;@+id/button2&quot;
            android:text=&quot;Button2&quot;
            android:layout_width=&quot;wrap_content&quot;
            android:layout_height=&quot;wrap_content&quot; /&gt;

        &lt;Button
            android:id=&quot;@+id/button3&quot;
            android:text=&quot;Button3&quot;
            android:layout_width=&quot;wrap_content&quot;
            android:layout_height=&quot;wrap_content&quot; /&gt;

        &lt;Button
            android:id=&quot;@+id/button4&quot;
            android:text=&quot;Button4&quot;
            android:layout_width=&quot;wrap_content&quot;
            android:layout_height=&quot;wrap_content&quot; /&gt;
    &lt;/LinearLayout&gt;

    &lt;LinearLayout
        android:id=&quot;@+id/linearLayout2&quot;
        android:layout_width=&quot;match_parent&quot;
        android:layout_height=&quot;wrap_content&quot;
        android:orientation=&quot;horizontal&quot; /&gt;
&lt;/LinearLayout&gt;
```

Hope I tried to clear my problem.

Fragment Inside Fragment

I&#39;m wondering if this is actually a bug in the Android API:

I have a setup like so:

    ┌----┬---------┐
    |    |         |
    |  1 |    2    |
    |    |┌-------┐|
    |    ||       ||
    |    ||   3   ||
    └----┴┴-------┴┘

 1. Is a menu which loads fragment #2 (A search screen) in the right pane.
 2. Is a search screen which contains fragment #3, which is a result list.
 3. The result list is used in several places (including as a functioning high level fragment in it&#39;s own right).

This functionality works perfectly well on a phone (Where 1 &amp; 2 and 3 are `ActivityFragment`s). 

However, when I used this code:

		FragmentTransaction transaction = getSupportFragmentManager().beginTransaction();		
		Fragment frag = new FragmentNumber2();
		if(toLoad != null) frag.setArguments(toLoad);
		transaction.replace(R.id.rightPane, frag);      
		transaction.commit();

Where `R.id.leftPane` and `R.id.rightPane` are `&lt;fragment&gt;`s in a horizontal linear layout.

It is my understanding that the above code removes the fragment which is resident and then replaces it with a new fragment. Brilliant... Obviously that isn&#39;t what happens because when this code runs the second time you get the following exception:

    07-27 15:22:55.940: ERROR/AndroidRuntime(8105): Caused by: java.lang.IllegalArgumentException: Binary XML file line #57: Duplicate id 0x7f080024, tag null, or parent id 0x0 with another fragment for FragmentNumber3

This is caused because the the container for FragmentNumber3 has been duplicated and it no longer has a unique ID. The initial Fragment hasn&#39;t been destroyed (?) before the new one is added (in my mind that means it hasn&#39;t been *replaced*).

Can someone tell me if this is possible ([this answer](https://stackoverflow.com/questions/5268361/fragments-in-action-bar-tab-fragments/5280000#5280000) suggests it isn&#39;t) or is it a bug?


Fragments within Fragments

I&#39;m writing an app for 4.0 and 4.1 tablets, for which **I do not want to use the support libraries** (if not needed) but the 4.x api only therefore.

So my target platform is very well defined as: &gt;= 4.0 and &lt;= 4.1

The app has a multi-pane layout (two fragments, one small on the left, one content fragment on the right) and an action bar with tabs.

Similar to this:

![enter image description here][1]

Clicking a tab on the action bar changes the &#39;outer&#39; fragment, and the inner fragment then is a fragment with two nested fragments (1. small left list fragment, 2. wide content fragment).

I am now wondering what&#39;s the best practice to replace fragments and especially nested fragments. 
The ViewPager is part of the support library, there&#39;s no native 4.x alternative for this class. Appear to be &#39;deprecated&#39; in my sense.
 - http://developer.android.com/reference/android/support/v4/view/ViewPager.html


Then I read the release notes for Android 4.2, regarding `ChildFragmentManager`, which would be a good fit, but I am targeting 4.0 and 4.1, so this can&#39;t be used either.

`ChildFragmentManager` is only available in 4.2

 - http://developer.android.com/about/versions/android-4.2.html#NestedFragments
 - http://developer.android.com/reference/android/app/Fragment.html#getChildFragmentManager()

Unfortunately, there are hardly any good examples out there that show best practices for fragments usages without the support library, even in the entire Android developer guides; and especially nothing regarding nested fragments.

**So I am wondering: is it simply not possible to write 4.1 apps with nested fragments without using the support library and everything that comes with it? (need to use FragmentActivity instead of Fragment, etc.?)**
Or what would be the best practice?


----------


The problem that I am currently having in the development is exactly this statement:

 - http://developer.android.com/about/versions/android-4.2.html#NestedFragments

&gt; The Android Support Library also now supports nested fragments, so you
&gt; can implement nested fragment designs on Android 1.6 and higher.
&gt; 
&gt; Note: You cannot inflate a layout into a fragment when that layout
&gt; includes a `&lt;fragment&gt;`. Nested fragments are only supported when added
&gt; to a fragment dynamically.

Because I put define the nested fragments in XML, which apparently causes an error like:

    Caused by: java.lang.IllegalArgumentException: Binary XML file line #15: Duplicate id 0x7f090009, tag frgCustomerList, or parent id 0x7f090008 with another fragment for de.xyz.is.android.fragment.CustomerListFragment_


At the moment, I conclude for myself: even on 4.1, when I don&#39;t even want to target the 2.x platform, nested fragments as shown in the screenshot are not possible without the support library.

(This might actually be more of a wiki entry than a question, but maybe somebody else has managed it before).

**Update:**

A helpful answer is at: https://stackoverflow.com/questions/6672066/fragment-inside-fragment/6672688#6672688

  [1]: http://i.stack.imgur.com/Ml3hl.png

Best practice for nested fragments in Android 4.0, 4.1 (&lt;4.2) without using the support library

With Android 4.2, the support library got support for nested fragments [see here][1]. I&#39;ve played around with it and found an interesting behaviour / bug regarding back stack and [getChildFragmentManager()][2]. When using getChildFragmentManager() and addToBackStack(String name), by pressing the back button the system does not run down the back stack to the previous fragment. 
On the other hand, when using [getFragmentManager()][3] and addToBackStack(String name), by pressing the back button the system returns to the previous fragment. 

For me, this behaviour is unexpected. By pressing the back button on my device, I&#39;m expecting that the last added fragment to the back stack will be popped, even if the fragment was added to the back stack in the children&#39;s fragment manager.

Is this behaviour correct? Is this behaviour a bug? Is there a work around for this issue?




sample code with getChildFragmentManager():
===========================================



    public class FragmentceptionActivity extends FragmentActivity {

	@Override
	protected void onCreate(Bundle arg0) {
		super.onCreate(arg0);

		final FrameLayout wrapper1 = new FrameLayout(this);
		wrapper1.setLayoutParams(new FrameLayout.LayoutParams(
				FrameLayout.LayoutParams.MATCH_PARENT,
				FrameLayout.LayoutParams.MATCH_PARENT));
		wrapper1.setId(1);

		final FrameLayout.LayoutParams params = new FrameLayout.LayoutParams(
				FrameLayout.LayoutParams.MATCH_PARENT,
				FrameLayout.LayoutParams.WRAP_CONTENT);
		params.topMargin = 0;

		final TextView text = new TextView(this);
		text.setLayoutParams(params);
		text.setText(&quot;fragment 1&quot;);
		wrapper1.addView(text);

		setContentView(wrapper1);

		getSupportFragmentManager().beginTransaction().addToBackStack(null)
				.add(1, new Fragment1()).commit();
	}

	public class Fragment1 extends Fragment {
		@Override
		public View onCreateView(LayoutInflater inflater, ViewGroup container,
				Bundle savedInstanceState) {
			final FrameLayout wrapper2 = new FrameLayout(getActivity());
			wrapper2.setLayoutParams(new FrameLayout.LayoutParams(
					FrameLayout.LayoutParams.MATCH_PARENT,
					FrameLayout.LayoutParams.MATCH_PARENT));
			wrapper2.setId(2);

			final FrameLayout.LayoutParams params = new FrameLayout.LayoutParams(
					FrameLayout.LayoutParams.MATCH_PARENT,
					FrameLayout.LayoutParams.WRAP_CONTENT);
			params.topMargin = 100;

			final TextView text = new TextView(getActivity());
			text.setLayoutParams(params);
			text.setText(&quot;fragment 2&quot;);
			wrapper2.addView(text);

			return wrapper2;
		}

		@Override
		public void onViewCreated(View view, Bundle savedInstanceState) {
			super.onViewCreated(view, savedInstanceState);

			getFragmentManager().beginTransaction().addToBackStack(null)
					.add(2, new Fragment2()).commit();
		}
	}

	public class Fragment2 extends Fragment {
		@Override
		public View onCreateView(LayoutInflater inflater, ViewGroup container,
				Bundle savedInstanceState) {
			final FrameLayout wrapper3 = new FrameLayout(getActivity());
			wrapper3.setLayoutParams(new FrameLayout.LayoutParams(
					FrameLayout.LayoutParams.MATCH_PARENT,
					FrameLayout.LayoutParams.MATCH_PARENT));
			wrapper3.setId(3);

			final FrameLayout.LayoutParams params = new FrameLayout.LayoutParams(
					FrameLayout.LayoutParams.MATCH_PARENT,
					FrameLayout.LayoutParams.WRAP_CONTENT);
			params.topMargin = 200;

			final TextView text = new TextView(getActivity());
			text.setLayoutParams(params);
			text.setText(&quot;fragment 3&quot;);
			wrapper3.addView(text);

			return wrapper3;
		}

		@Override
		public void onViewCreated(View view, Bundle savedInstanceState) {
			super.onViewCreated(view, savedInstanceState);

			getChildFragmentManager().beginTransaction().addToBackStack(null)
					.add(3, new Fragment3()).commit();
		}
	}

	public class Fragment3 extends Fragment {
		@Override
		public View onCreateView(LayoutInflater inflater, ViewGroup container,
				Bundle savedInstanceState) {
			final FrameLayout wrapper4 = new FrameLayout(getActivity());
			wrapper4.setLayoutParams(new FrameLayout.LayoutParams(
					FrameLayout.LayoutParams.MATCH_PARENT,
					FrameLayout.LayoutParams.MATCH_PARENT));
			wrapper4.setId(4);

			final FrameLayout.LayoutParams params = new FrameLayout.LayoutParams(
					FrameLayout.LayoutParams.MATCH_PARENT,
					FrameLayout.LayoutParams.WRAP_CONTENT);
			params.topMargin = 300;

			final TextView text = new TextView(getActivity());
			text.setLayoutParams(params);
			text.setText(&quot;fragment 4&quot;);
			wrapper4.addView(text);

			return wrapper4;
		}

		@Override
		public void onViewCreated(View view, Bundle savedInstanceState) {
			super.onViewCreated(view, savedInstanceState);

			getChildFragmentManager().beginTransaction().addToBackStack(null)
					.add(4, new Fragment4()).commit();
		}
	}

	public class Fragment4 extends Fragment {
		@Override
		public View onCreateView(LayoutInflater inflater, ViewGroup container,
				Bundle savedInstanceState) {
			final FrameLayout wrapper5 = new FrameLayout(getActivity());
			wrapper5.setLayoutParams(new FrameLayout.LayoutParams(
					FrameLayout.LayoutParams.MATCH_PARENT,
					FrameLayout.LayoutParams.MATCH_PARENT));
			wrapper5.setId(5);

			final FrameLayout.LayoutParams params = new FrameLayout.LayoutParams(
					FrameLayout.LayoutParams.MATCH_PARENT,
					FrameLayout.LayoutParams.WRAP_CONTENT);
			params.topMargin = 400;

			final TextView text = new TextView(getActivity());
			text.setLayoutParams(params);
			text.setText(&quot;fragment 5&quot;);
			wrapper5.addView(text);

			return wrapper5;
		}

		@Override
		public void onViewCreated(View view, Bundle savedInstanceState) {
			super.onViewCreated(view, savedInstanceState);
		}
	}

    }


sample code with getFragmentManager():
======================================


    public class FragmentceptionActivity extends FragmentActivity {

	@Override
	protected void onCreate(Bundle arg0) {
		super.onCreate(arg0);

		final FrameLayout wrapper1 = new FrameLayout(this);
		wrapper1.setLayoutParams(new FrameLayout.LayoutParams(
				FrameLayout.LayoutParams.MATCH_PARENT,
				FrameLayout.LayoutParams.MATCH_PARENT));
		wrapper1.setId(1);

		final FrameLayout.LayoutParams params = new FrameLayout.LayoutParams(
				FrameLayout.LayoutParams.MATCH_PARENT,
				FrameLayout.LayoutParams.WRAP_CONTENT);
		params.topMargin = 0;

		final TextView text = new TextView(this);
		text.setLayoutParams(params);
		text.setText(&quot;fragment 1&quot;);
		wrapper1.addView(text);

		setContentView(wrapper1);

		getSupportFragmentManager().beginTransaction().addToBackStack(null)
				.add(1, new Fragment1()).commit();
	}

	public class Fragment1 extends Fragment {
		@Override
		public View onCreateView(LayoutInflater inflater, ViewGroup container,
				Bundle savedInstanceState) {
			final FrameLayout wrapper2 = new FrameLayout(getActivity());
			wrapper2.setLayoutParams(new FrameLayout.LayoutParams(
					FrameLayout.LayoutParams.MATCH_PARENT,
					FrameLayout.LayoutParams.MATCH_PARENT));
			wrapper2.setId(2);

			final FrameLayout.LayoutParams params = new FrameLayout.LayoutParams(
					FrameLayout.LayoutParams.MATCH_PARENT,
					FrameLayout.LayoutParams.WRAP_CONTENT);
			params.topMargin = 100;

			final TextView text = new TextView(getActivity());
			text.setLayoutParams(params);
			text.setText(&quot;fragment 2&quot;);
			wrapper2.addView(text);

			return wrapper2;
		}

		@Override
		public void onViewCreated(View view, Bundle savedInstanceState) {
			super.onViewCreated(view, savedInstanceState);

			getFragmentManager().beginTransaction().addToBackStack(null)
					.add(2, new Fragment2()).commit();
		}
	}

	public class Fragment2 extends Fragment {
		@Override
		public View onCreateView(LayoutInflater inflater, ViewGroup container,
				Bundle savedInstanceState) {
			final FrameLayout wrapper3 = new FrameLayout(getActivity());
			wrapper3.setLayoutParams(new FrameLayout.LayoutParams(
					FrameLayout.LayoutParams.MATCH_PARENT,
					FrameLayout.LayoutParams.MATCH_PARENT));
			wrapper3.setId(3);

			final FrameLayout.LayoutParams params = new FrameLayout.LayoutParams(
					FrameLayout.LayoutParams.MATCH_PARENT,
					FrameLayout.LayoutParams.WRAP_CONTENT);
			params.topMargin = 200;

			final TextView text = new TextView(getActivity());
			text.setLayoutParams(params);
			text.setText(&quot;fragment 3&quot;);
			wrapper3.addView(text);

			return wrapper3;
		}

		@Override
		public void onViewCreated(View view, Bundle savedInstanceState) {
			super.onViewCreated(view, savedInstanceState);

			getFragmentManager().beginTransaction().addToBackStack(null)
					.add(3, new Fragment3()).commit();
		}
	}

	public class Fragment3 extends Fragment {
		@Override
		public View onCreateView(LayoutInflater inflater, ViewGroup container,
				Bundle savedInstanceState) {
			final FrameLayout wrapper4 = new FrameLayout(getActivity());
			wrapper4.setLayoutParams(new FrameLayout.LayoutParams(
					FrameLayout.LayoutParams.MATCH_PARENT,
					FrameLayout.LayoutParams.MATCH_PARENT));
			wrapper4.setId(4);

			final FrameLayout.LayoutParams params = new FrameLayout.LayoutParams(
					FrameLayout.LayoutParams.MATCH_PARENT,
					FrameLayout.LayoutParams.WRAP_CONTENT);
			params.topMargin = 300;

			final TextView text = new TextView(getActivity());
			text.setLayoutParams(params);
			text.setText(&quot;fragment 4&quot;);
			wrapper4.addView(text);

			return wrapper4;
		}

		@Override
		public void onViewCreated(View view, Bundle savedInstanceState) {
			super.onViewCreated(view, savedInstanceState);

			getFragmentManager().beginTransaction().addToBackStack(null)
					.add(4, new Fragment4()).commit();
		}
	}

	public class Fragment4 extends Fragment {
		@Override
		public View onCreateView(LayoutInflater inflater, ViewGroup container,
				Bundle savedInstanceState) {
			final FrameLayout wrapper5 = new FrameLayout(getActivity());
			wrapper5.setLayoutParams(new FrameLayout.LayoutParams(
					FrameLayout.LayoutParams.MATCH_PARENT,
					FrameLayout.LayoutParams.MATCH_PARENT));
			wrapper5.setId(5);

			final FrameLayout.LayoutParams params = new FrameLayout.LayoutParams(
					FrameLayout.LayoutParams.MATCH_PARENT,
					FrameLayout.LayoutParams.WRAP_CONTENT);
			params.topMargin = 400;

			final TextView text = new TextView(getActivity());
			text.setLayoutParams(params);
			text.setText(&quot;fragment 5&quot;);
			wrapper5.addView(text);

			return wrapper5;
		}

		@Override
		public void onViewCreated(View view, Bundle savedInstanceState) {
			super.onViewCreated(view, savedInstanceState);
		}
	}

    }



  [1]: http://developer.android.com/about/versions/android-4.2.html#NestedFragments
  [2]: https://developer.android.com/reference/android/support/v4/app/Fragment.html#getChildFragmentManager%28%29
  [3]: https://developer.android.com/reference/android/support/v4/app/Fragment.html#getFragmentManager%28%29

Android 4.2: back stack behaviour with nested fragments

I have an application that consists of using ActionBarSherlock in tab mode.I have 5 tabs and the content of each tab is handled using fragments. For tab2 though, I have a fragment the xml file of which holds a ViewPager element which in turn has some fragment pages. When I initially start the application the application, I am able to switch between tabs no problem but when I press on tab2 for the second time I get the error mentioned above. The main activity is as follows:
    
    public class MainActivity extends SherlockFragmentActivity
    {
    	@Override
    	protected void onCreate(Bundle savedInstanceState) 
    	{
    		super.onCreate(savedInstanceState);
    		setContentView(R.layout.activity_main);
    		
    		ActionBar actionBar = getSupportActionBar();
    		
    		ActionBar.Tab tab1 = actionBar.newTab().setText(&quot;Tab1&quot;);
    		ActionBar.Tab tab3 = actionBar.newTab().setText(&quot;Tab3&quot;);
    		ActionBar.Tab tab2 = actionBar.newTab().setText(&quot;Tab2&quot;);
    		ActionBar.Tab tab4 = actionBar.newTab().setText(&quot;Tab4&quot;);
    		ActionBar.Tab tab5 = actionBar.newTab().setText(&quot;Tab5&quot;);
    		
    		Fragment fragment1 = new Tab1();
    		Fragment fragment3 = new Tab3();
    		Fragment fragment2 = new Tab2();
    		Fragment fragment5 = new Tab5();
    		Fragment fragment4 = new Tab4();
    		
    		tab1.setTabListener(new MyTabListener(fragment1));
    		tab3.setTabListener(new MyTabListener(fragment3));
    		tab2.setTabListener(new MyTabListener(fragment2));
    		tab5.setTabListener(new MyTabListener(fragment5));
    		tab4.setTabListener(new MyTabListener(fragment4));
    		
    		actionBar.addTab(tab1);
    		actionBar.addTab(tab2);
    		actionBar.addTab(tab3);
    		actionBar.addTab(tab4);
    		actionBar.addTab(tab5);	
    		
    		actionBar.setNavigationMode(ActionBar.NAVIGATION_MODE_TABS);
    	}
    	
    	class MyTabListener implements ActionBar.TabListener
    	{
    		Fragment fragment;
    		
    		public MyTabListener(Fragment fragment)
    		{
    			this.fragment = fragment;
    		}
    		
    		@Override
    		public void onTabSelected(com.actionbarsherlock.app.ActionBar.Tab tab,FragmentTransaction ft) 
    		{
    			ft.replace(R.id.fragment_container,fragment);
    		}
    
    		@Override
    		public void onTabUnselected(com.actionbarsherlock.app.ActionBar.Tab tab,FragmentTransaction ft) 
    		{
    			
    		}
    
    		@Override
    		public void onTabReselected(com.actionbarsherlock.app.ActionBar.Tab tab,FragmentTransaction ft) 
    		{
    			
    		}
    	}
    }

The fragment class without the ViewPager is as follows:
    
    public class Tab1 extends Fragment 
    {
    	@Override
    	public View onCreateView(LayoutInflater inflater, ViewGroup container,Bundle savedInstanceState)
    	{
    		return inflater.inflate(R.layout.activity_tab1, container, false);
    	}
    }

The fragment class with the ViewPager is as follows:

    public class Tab2 extends Fragment 
    {
    	ViewPager mViewPager;
    	private MyFragmentPagerAdapter mMyFragmentPagerAdapter;  
    	private static int NUMBER_OF_PAGES = 5;
    	
    	@Override
    	public View onCreateView(LayoutInflater inflater, ViewGroup container,Bundle savedInstanceState)
    	{
    		View view =  inflater.inflate(R.layout.activity_tab2, container, false); 
    		return view;
    	}
    	
    	@Override
        public void onViewCreated(View view,Bundle savedInstanceState)
    	{
    		super.onViewCreated(view, savedInstanceState);
    		mViewPager = (ViewPager) view.findViewById(R.id.viewpager);
            mMyFragmentPagerAdapter = new MyFragmentPagerAdapter(getChildFragmentManager());  
            mViewPager.setAdapter(mMyFragmentPagerAdapter);  
    	}
    	
    	private static class MyFragmentPagerAdapter extends FragmentPagerAdapter 
    	{    
            public MyFragmentPagerAdapter(FragmentManager fm) 
            {  
                 super(fm);  
            }  
    
    		@Override  
            public Fragment getItem(int index) 
            {  
                 return PageFragment.newInstance(&quot;My Message &quot; + index);
            }  
    
            @Override  
            public int getCount() 
            {  
                 return NUMBER_OF_PAGES;  
            }  
       }
    }

From what I&#39;ve read in different places (and please correct me if I&#39;m wrong), this happens because the fragment manager on the second pass tries to reuse the fragments from the activity which doesn&#39;t exist anymore thus giving the error.But I&#39;m not sure why this happens over here since I&#39;m not using  fragment activity. According to logcat the error is in the Tab2 class, onViewCreated method on the line that says mViewPager.setAdapter(mMyFragmentPagerAdapter). Any help is greatly appreciated...Thanks.

    03-04 12:01:05.468: E/AndroidRuntime(2474): FATAL EXCEPTION: main
    03-04 12:01:05.468: E/AndroidRuntime(2474): java.lang.IllegalStateException: Activity has been destroyed
    03-04 12:01:05.468: E/AndroidRuntime(2474): 	at android.support.v4.app.FragmentManagerImpl.enqueueAction(FragmentManager.java:1342)
    03-04 12:01:05.468: E/AndroidRuntime(2474): 	at android.support.v4.app.BackStackRecord.commitInternal(BackStackRecord.java:595)
    03-04 12:01:05.468: E/AndroidRuntime(2474): 	at android.support.v4.app.BackStackRecord.commitAllowingStateLoss(BackStackRecord.java:578)
    03-04 12:01:05.468: E/AndroidRuntime(2474): 	at android.support.v4.app.FragmentPagerAdapter.finishUpdate(FragmentPagerAdapter.java:139)
    03-04 12:01:05.468: E/AndroidRuntime(2474): 	at android.support.v4.view.ViewPager.populate(ViewPager.java:1011)
    03-04 12:01:05.468: E/AndroidRuntime(2474): 	at android.support.v4.view.ViewPager.populate(ViewPager.java:880)
    03-04 12:01:05.468: E/AndroidRuntime(2474): 	at android.support.v4.view.ViewPager.setAdapter(ViewPager.java:433)
    03-04 12:01:05.468: E/AndroidRuntime(2474): 	at com.example.tabs.Tab2.onViewCreated(Tab2.java:31)
    03-04 12:01:05.468: E/AndroidRuntime(2474): 	at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:925)
    03-04 12:01:05.468: E/AndroidRuntime(2474): 	at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1088)
    03-04 12:01:05.468: E/AndroidRuntime(2474): 	at android.support.v4.app.BackStackRecord.run(BackStackRecord.java:682)
    03-04 12:01:05.468: E/AndroidRuntime(2474): 	at android.support.v4.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1444)
    03-04 12:01:05.468: E/AndroidRuntime(2474): 	at android.support.v4.app.FragmentManagerImpl$1.run(FragmentManager.java:429)
    03-04 12:01:05.468: E/AndroidRuntime(2474): 	at android.os.Handler.handleCallback(Handler.java:587)
    03-04 12:01:05.468: E/AndroidRuntime(2474): 	at android.os.Handler.dispatchMessage(Handler.java:92)
    03-04 12:01:05.468: E/AndroidRuntime(2474): 	at android.os.Looper.loop(Looper.java:123)
    03-04 12:01:05.468: E/AndroidRuntime(2474): 	at android.app.ActivityThread.main(ActivityThread.java:3687)
    03-04 12:01:05.468: E/AndroidRuntime(2474): 	at java.lang.reflect.Method.invokeNative(Native Method)
    03-04 12:01:05.468: E/AndroidRuntime(2474): 	at java.lang.reflect.Method.invoke(Method.java:507)
    03-04 12:01:05.468: E/AndroidRuntime(2474): 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:842)
    03-04 12:01:05.468: E/AndroidRuntime(2474): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:600)
    03-04 12:01:05.468: E/AndroidRuntime(2474): 	at dalvik.system.NativeStart.main(Native Method)



Getting the error &quot;Java.lang.IllegalStateException Activity has been destroyed&quot; when using tabs with ViewPager

I have a fragment interface with tabs along the bottom which open different fragments in the main view.

I have one particular fragment which is a list of items.  If the user selects one of the items in this list, another fragment opens which contains a viewpager which scrolls horizontally between all of the items in the list in the previous fragment.  This works great.

The viewpager uses a FragmentPagerAdapter to display the items.

The problem comes when the user selects an item in the list, views it, then hits the button on the tab bar to go back to the list, then selects another item.  The second time an item is selected, a blank screen appears instead of the viewpager.  I receive no errors in my LogCat when this happens.

Why is the viewpager only appearing the first time?

`FragmentPagerAdapter:`

    public class ViewPagerAdapter extends FragmentPagerAdapter {
		Cursor mCursor;

		public ViewPagerAdapter(FragmentManager fm, Cursor c) {
			super(fm);
			mCursor = c;
		}

		public void changeCursor(Cursor c) {
			mCursor = c;
			this.notifyDataSetChanged();
		}

		@Override
		public int getCount() {
			if (mCursor == null) return 0;
			else return mCursor.getCount();
		}

		@Override
		public Fragment getItem(int position) {
			mCursor.moveToPosition(position);
			return TeamCardFragment.newInstance(mCursor, position);
		}
	}

`PagerFragment:`

    @Override
	public View onCreateView(LayoutInflater inflater, ViewGroup container, Bundle savedInstanceState) {
		Bundle bundle = getArguments();
		mCursorPosition = bundle.getInt(TeamCardCommon.BUNDLE_KEY_CURSOR_POSITION);
		
		View mView = inflater.inflate(R.layout.team_card_master, container, false);
		mViewPager = (ViewPager)mView.findViewById(R.id.team_card_master_view_pager);

		mAdapter = new ViewPagerAdapter(getFragmentManager(), cursor);
		new setAdapterTask().execute();

		return mView;
	}

    private class setAdapterTask extends AsyncTask&lt;Void, Void, Void&gt; {
		protected Void doInBackground(Void... params) {
			return null;
		}

		@Override
		protected void onPostExecute(Void result) {
			mViewPager.setAdapter(mAdapter);
			mViewPager.setCurrentItem(mCursorPosition);
		}
	}

Fragment in ViewPager using FragmentPagerAdapter is blank the second time it is viewed

Here&#39;s the scenario: Activity contains fragment `A`, which in turn uses `getChildFragmentManager()` to add fragments `A1` and `A2` in its `onCreate` like so:

    getChildFragmentManager()
      .beginTransaction()
      .replace(R.id.fragmentOneHolder, new FragmentA1())
      .replace(R.id.fragmentTwoHolder, new FragmentA2())
      .commit()


So far, so good, everything is running as expected.

We then run the following transaction in the Activity: 

    getSupportFragmentManager()
      .beginTransaction()
      .setCustomAnimations(anim1, anim2, anim1, anim2)
      .replace(R.id.fragmentHolder, new FragmentB())
      .addToBackStack(null)
      .commit()

During the transition, the `enter` animations for fragment `B` runs correctly but **fragments A1 and A2 disappear entirely**. When we revert the transaction with the Back button, they initialize properly and display normally during the `popEnter` animation.

In my brief testing, it got weirder - if I set the animations for the child fragments (see below), the `exit` animation runs intermittently when we add fragment `B`

    getChildFragmentManager()
      .beginTransaction()
      .setCustomAnimations(enter, exit)
      .replace(R.id.fragmentOneHolder, new FragmentA1())
      .replace(R.id.fragmentTwoHolder, new FragmentA2())
      .commit()

The effect I want to achieve is simple - I want the `exit` (or should it be `popExit`?) animation on fragment `A` (anim2) to run, animating the whole container, including its nested children. 

Is there any way to achieve that?

**Edit**: Please find a test case [here][1]

**Edit2**: Thanks to @StevenByle for pushing me to keep trying with the static animations. Apparently you can set animations on a per-op basis (not global to the whole transaction), which means the children can have an indefinite static animation set, while their parent can have a different animation and the whole thing can be committed in one transaction. See the discussion below and the [updated test case project][1].

  [1]: https://github.com/BurntBrunch/NestedFragmentsAnimationsTest

Nested fragments disappear during transition animation

I have been using the new [nested fragment][1] API that Android includes in the support library.

The problem that I am facing with nested fragments is that, if a nested fragment (that is, a fragment that has been added to another fragment via the `FragmentManager`returned by `getChildFragmentManager()`) calls `startActivityForResult()`, the nested fragment&#39;s `onActivityResult()` method is not called. However, both the parent fragment&#39;s `onActivityResult()` and activity&#39;s `onActivityResult()` do get called.

I don&#39;t know if I am missing something about nested fragments, but I did not expect the described behavior. Below is the code that reproduces this problem. I would very much appreciate if someone can point me in the right direction and explain to me what I am doing wrong:

&lt;!-- language: lang-java --&gt;

    package com.example.nestedfragmentactivityresult;
    
    import android.media.RingtoneManager;
    import android.os.Bundle;
    import android.content.Intent;
    import android.support.v4.app.Fragment;
    import android.support.v4.app.FragmentActivity;
    import android.view.LayoutInflater;
    import android.view.View;
    import android.view.ViewGroup;
    import android.widget.Button;
    import android.widget.Toast;
    
    public class MainActivity extends FragmentActivity
    {
        public void onCreate(Bundle savedInstanceState)
        {
            super.onCreate(savedInstanceState);
            this.getSupportFragmentManager()
                .beginTransaction()
                .add(android.R.id.content, new ContainerFragment())
                .commit();
        }
    
        public void onActivityResult(int requestCode, int resultCode, Intent data)
        {
            super.onActivityResult(requestCode, resultCode, data);

            // This is called
            Toast.makeText(getApplication(),
                &quot;Consumed by activity&quot;,
                Toast.LENGTH_SHORT).show();
        }
    
        public static class ContainerFragment extends Fragment
        {
            public final View onCreateView(LayoutInflater inflater,
                                           ViewGroup container,
                                           Bundle savedInstanceState)
            {
                View result = inflater.inflate(R.layout.test_nested_fragment_container,
                    container,
                    false);
    
                return result;
            }
    
            public void onActivityCreated(Bundle savedInstanceState)
            {
                super.onActivityCreated(savedInstanceState);
                getChildFragmentManager().beginTransaction()
                    .add(R.id.content, new NestedFragment())
                    .commit();
            }
    
            public void onActivityResult(int requestCode,
                                         int resultCode,
                                         Intent data)
            {
                super.onActivityResult(requestCode, resultCode, data);

                // This is called
                Toast.makeText(getActivity(),
                    &quot;Consumed by parent fragment&quot;,
                    Toast.LENGTH_SHORT).show();
            }
        }
    
        public static class NestedFragment extends Fragment
        {
            public final View onCreateView(LayoutInflater inflater,
                                           ViewGroup container,
                                           Bundle savedInstanceState)
            {
                Button button = new Button(getActivity());
                button.setText(&quot;Click me!&quot;);
                button.setOnClickListener(new View.OnClickListener()
                {
                    public void onClick(View v)
                    {
                        Intent intent = new Intent(RingtoneManager.ACTION_RINGTONE_PICKER);
                        startActivityForResult(intent, 0);
                    }
                });
    
                return button;
            }
    
            public void onActivityResult(int requestCode,
                                         int resultCode,
                                         Intent data)
            {
                super.onActivityResult(requestCode, resultCode, data);

                // This is NOT called
                Toast.makeText(getActivity(),
                    &quot;Consumed by nested fragment&quot;,
                    Toast.LENGTH_SHORT).show();
            }
        }
    }

test_nested_fragment_container.xml is:

&lt;!-- language: lang-xml --&gt;

	&lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot;?&gt;
	&lt;FrameLayout xmlns:android=&quot;http://schemas.android.com/apk/res/android&quot;
	    android:id=&quot;@+id/content&quot;
	    android:layout_width=&quot;match_parent&quot;
	    android:layout_height=&quot;match_parent&quot; &gt;
	
	&lt;/FrameLayout&gt;


  [1]: http://developer.android.com/about/versions/android-4.2.html#NestedFragments

onActivityResult() not called in new nested fragment API

I have a `Fragment` `FR1` that contains several `Nested` `Fragments`; `FRa`, `FRb`, `FRc`. These `Nested` `Fragments` are changed by pressing `Buttons` on `FR1`&#39;s layout. Each of the `Nested` `Fragments` have several input fields within them; which include things like `EditTexts`, `NumberPickers`, and `Spinners`. When my user goes through and fills in all the values for the `Nested` `Fragments`, `FR1` (the parent fragment) has a submit button.

How can I then, retrieve my values from my `Nested` `Fragments` and bring them into `FR1`.

1. All `Views` are declared and programmatically handled within each `Nested` `Fragment`.
2. The parent `Fragment`, `FR1` handles the transaction of the `Nested` `Fragments`.

I hope this question is clear enough and I am not sure if code is necessary to post but if someone feels otherwise I can do so.

**EDIT 1:**

Here is how I add my `Nested` `Fragments`:

    tempRangeButton.setOnClickListener(new View.OnClickListener() {

			@Override
			public void onClick(View v) {
				
				getChildFragmentManager().beginTransaction()
						.add(R.id.settings_fragment_tertiary_nest, tempFrag)
						.commit();

			}
		});

		scheduleButton.setOnClickListener(new View.OnClickListener() {

			@Override
			public void onClick(View v) {
					
				getChildFragmentManager().beginTransaction()
						.add(R.id.settings_fragment_tertiary_nest, scheduleFrag)
						.commit();
			}
		});

		alertsButton.setOnClickListener(new View.OnClickListener() {

			@Override
			public void onClick(View v) {
					
				getChildFragmentManager().beginTransaction()
						.add(R.id.settings_fragment_tertiary_nest, alertsFrag)
						.commit();

			}
		});

		submitProfile.setOnClickListener(new View.OnClickListener() {

			@Override
			public void onClick(View v) {
				constructNewProfile();
			}
		});


where my `constructNewProfile()` method needs the values from my `Nested` `Fragments`.


    public Fragment tempFrag = fragment_profile_settings_temperature
			.newInstance();
    public Fragment scheduleFrag= fragment_profile_settings_schedules
    			.newInstance();
    public Fragment alertsFrag = fragment_profile_settings_alerts
			.newInstance();

The above refers to the fields of the parent fragment; and how they are initially instantiated.


Sending data from nested fragments to parent fragment

I have a fragment which contains a ViewPager.  The ViewPager is associated with an adapter that contains a set of fragments.

Upon loading the parent fragment, I am met with an `IllegalStateException` with the message: `java.lang.IllegalStateException: Recursive entry to executePendingTransactions`.

Some research has led me to the conclusion that the system is unable display fragments within another fragment, HOWEVER there seems to be some indication that it is possible to do exactly this with the use of a ViewPager ([A bug in ViewPager using it with other fragment][1]).

In fact, if I add a button to my parent fragment which calls `mPager.setAdapter(mAdapter)` on my ViewPager when pressed, the ViewPager successfully loads.  This is not ideal.

The issue then must be related to the fragment lifecycle.  My question therefore, is this:
Has anybody else found a way around this issue, and if so, how?

Is there some way to delay settings the adapter on the ViewPager until after the fragment transaction?

Here is my parent fragment code:

    	@Override
	public View onCreateView(LayoutInflater inflater, ViewGroup container, Bundle savedInstanceState) {
		
		mView = inflater.inflate(R.layout.team_card_master, container, false);
		mViewPager = (ViewPager)mView.findViewById(R.id.team_card_master_view_pager);
		
		final Button button = (Button)mView.findViewById(R.id.load_viewpager_button);
		button.setOnClickListener(new OnClickListener() {
			@Override
			public void onClick(View v) {
				mViewPager.setAdapter(mAdapter);
				button.setVisibility(View.GONE);
			}
		});
		
		mAdapter = new ViewPagerAdapter(getFragmentManager());
     //		mViewPager.setAdapter(mAdapter);
		
		return mView;
	}


And the adapter:

	public class ViewPagerAdapter extends FragmentPagerAdapter {
		public ViewPagerAdapter(FragmentManager fm) {
			super(fm);
		}
		
		@Override
		public int getCount() {
			if (mCursor == null) return 0;
			else return mCursor.getCount();
		}
		
		@Override
		public Fragment getItem(int position) {
			Bundle b = createBundle(position, mCursor);
			return TeamCardFragment.newInstance(b);
		}
	}

  [1]: https://stackoverflow.com/questions/7241153/a-bug-in-viewpager-using-it-with-other-fragment/7654881#7654881

Display fragment viewpager within a fragment

I have a `ViewPager` with three `Fragments`, each one shows a `List` (or `Grid`).

In the new `Android API level 17` (Jelly Bean 4.2), one of the features is [Nested Fragments][1]. The new functionality description says: 

&gt; if you use ViewPager to create fragments that swipe left and right and
&gt; consume a majority of the screen space, you can now insert fragments
&gt; into each fragment page.

So, if I understand right, now I can create a `ViewPager` with `Fragments` (with a button inside for example) inside, and when user press the button show another `Fragment` without loose the `ViewPager` using this new feature.

I&#39;ve expended my morning trying to implement this several different ways, but I can&#180;t get it working... Can somebody add a simple example of how to implement this?

PS: I&#39;m only interested in doing at this way, with `getChildFragmentManager` to learn how works.


  [1]: http://developer.android.com/about/versions/android-4.2.html#NestedFragments

How to add a Fragment inside a ViewPager using Nested Fragment (Android 4.2)

I need to place a ViewPager inside of a fragment, but I have two fragments, Fragment 1 is my MENU, and Fragment 2 I want to use as a ViewPagerIndicator. 

But a fragment can&#39;t have another fragment...  what do I need to do for that?


![enter image description here][1]


  [1]: http://i.stack.imgur.com/V4JSh.png

How to set a ViewPager inside a Fragment

I&#39;m trying to make an app that has a `ViewPager` in a Fragment that is part of a `TabHost`. Everything works out fine. I have my tabbar, I can switch tabs. When I switch to the tab with the `ViewPager`, all is shown correctly.

However, as soon as I leave this tab with the `ViewPager` and return this tab, my content is not shown. If I scroll to the side twice I do see my next image and if I go back two times I also see the images are loaded (probably the `offscreenloaded`).

See that my `TabFragment` is being reinstantiated when I return to it but the fragments in the `ViewPager` aren&#39;t.

    @Override
	public void onActivityCreated(Bundle savedInstanceState) {

		mProjectText = (TextView) getView().findViewById(R.id.projectText);
		mProjectText.setText(mActiveProject.getInspirationText());
		
		mAdapter = new AlbumAdapter(getFragmentManager(), mActiveProject.getInspiration());
		
        mPager = (ViewPager)getView().findViewById(R.id.pager);
        mPager.setAdapter(mAdapter);

		super.onActivityCreated(savedInstanceState);
	}

    public class AlbumAdapter extends FragmentStatePagerAdapter {

	private ArrayList&lt;ProjectContent&gt; mItems;
	
	public AlbumAdapter(FragmentManager fm, ArrayList&lt;ProjectContent&gt; items) {
		super(fm);
		this.mItems = items;
	}

	@Override
	public Fragment getItem(int position) {
		return AlbumContentFragment.newInstance(mItems.get(position));
	}

	@Override
	public int getCount() {
		return mItems.size();
	}
	
	@Override
	public int getItemPosition(Object object) {
		return POSITION_NONE;
	}}

[![The mockup for the app][1]][1]


  [1]: http://i.stack.imgur.com/4BArG.jpg

All Android Nested-Fragment Solutions on Gang of Coders

Total of 13 Android Nested-Fragment Solutions