How can I access getSupportFragmentManager() in a fragment?

Question

I have a FragmentActivity and I want to use a map fragment within it. I'm having a problem getting the support fragment manager to access it.

 if (googleMap == null) {
            googleMap = ((SupportMapFragment) getSupportFragmentManager()
                    .findFragmentById(R.id.map1)).getMap();

            // check if map is created successfully or not
            if (googleMap == null) {
                Toast.makeText(getApplicationContext(),
                        "Sorry! unable to create maps", Toast.LENGTH_SHORT)
                        .show();
            }
        }

            // create marker
            MarkerOptions marker = new MarkerOptions().position(
                    new LatLng(latitude, longitude)).title("Hello Maps ");

            CameraPosition cameraPosition = new CameraPosition.Builder()
                    .target(new LatLng(latitude, longitude)).zoom(15).build();

            googleMap.animateCamera(CameraUpdateFactory
                    .newCameraPosition(cameraPosition));

            // adding marker
            googleMap.addMarker(marker);

score 349 · Accepted Answer · edited Dec 16 '21 at 15:06

349

You can directly call

getParentFragmentManager()

to get the fragment manager. Note that getFragmentManager() also works but has been marked as deprecated.

edited Dec 16 '21 at 15:06

Anonymous

4,617
9
48
61

answered Nov 27 '13 at 08:51

Eldhose M Babu

14,382
8
39
44

4

when i click first time it work but after that going on some other fragment again i click on this it shows blank page.. – DjP Nov 27 '13 at 09:41
11

This is an overhead. See my answer below... getFragmentManager() is really all you need. – Mark Jul 17 '14 at 13:27
4

You don't need global mContext variable here, just use getActivity() wherever in your code you need it. Please edit your answer so you don't misguide people in wrong direction. – Varundroid Dec 10 '14 at 03:28
@Varundroid : Please keep in mind that there are chances where getActivity() can return null. For example, if the fragment is detached and if inside the fragment, if we call getActivity() it will return null. So if we are going for any async operations, its better to take it in a variable and use it. – Eldhose M Babu Dec 10 '14 at 06:19
No It won't, if you call it after certain method. Even you don't call getActivity, you can still get FragmentManager by just calling getFragmentManager() method of Fragment. You can do async operations only when Fragment is attached as AsyncTask relies on Activity life cycle but if you want to do something in background and outside of Activity lifecycle then better use Service. In that case ones you started the service, you don't need to control it. What you recommending to people is a bad practice. You should not have a global variable until or unless you REALLY need it. – Varundroid Dec 10 '14 at 09:28
@Varundroid Its all because of your lack of knowledge. First of all Async operations doesn't mean you need to use an Async task, it can be a thread. Second thing, Async task doen't relies on activity, what it is depended on is the UI thread to post the results back; to make it understandable for you, just try to create and use Async task inside your service, it will work (Don't tell service is activity.. :P). If I need some async operations to be performed, how can I use Service Sir? Perhaps you should understand the service uses the same UI thread and so it wont be async anymore. – Eldhose M Babu Dec 10 '14 at 09:42
@Varundroid Now the actual use of this is, for example, if you are calling a webservice from fragment, and if the user navigates away from fragment in between the service call to another fragment and when the service completes and if you try to open or show a dialog in your first fragment using getActivity(), it will result in nullpointer, you can try this example. – Eldhose M Babu Dec 10 '14 at 09:44
@Varundroid If you dealt with large projects involving frequent fragment transactions without stoping the user for background async operations, probably you will understand what I'm saying. Goodluck with your method and happy coding and keep this null pointer in mind. – Eldhose M Babu Dec 10 '14 at 09:49
Yes i have worked on big projects with more than 30 fragments in it and I am talking from my experience. I don't do hacks or avoid best practices to just avoid NullPointerException, I fix them. Happy coding to you as well. Cheers!! – Varundroid Dec 10 '14 at 23:29
@Varundroid Do you think creating a reference variable is a hack? Big project doesnt mean it should contains many fragments. What I meant is their transaction complexities and frequencies in async manner wrt broadcasts, events etc. Happy coding...sorry.....happy fixing.... – Eldhose M Babu Dec 11 '14 at 09:02
No its not but you are avoiding best practices here. If you don't believe me just send an email with this code to any Google developer and see what they have to say about it. Cheers!! – Varundroid Dec 11 '14 at 09:26
@Varundroid I'll believe you if you provide proofs to justify your comment. I've made my justification for why I used this. And I'm sure no one will mark this as a hack since I'm just using a reference variable to hold the context and am also pretty sure that it will not result in any memory leak since its life time will be that of the fragments. So please define "Avoiding best practice". – Eldhose M Babu Dec 12 '14 at 09:00
Best practices teaches us, don't use global variable, until or unless you REALLY need one. Let me explain you why your answer is wrong. First if you need a FragmentManager, you can simply call getFragmentManager() anytime. Don't believe me, test it by yourself. You don't even need a Context variable for that, forget about global variable. Secondly, getActivity() only returns null in case of where Fragment is detached and the function you using is onActivityAttached(). There is no chances on earth getActivity() will return null after this method. Don't believe me test it by yourself. – Varundroid Dec 13 '14 at 13:11
3

@Varundroid. I agree to the fact that we can call getFragmentManager() anytime. If you can send me your email Id, I can send u sample code to prove that there are chances on earth for getActivity() to return null. – Eldhose M Babu Dec 15 '14 at 07:16
@EldhoseMBabu how can method getSupportFragementManager be called without a class's, reference name? – abhimanyuaryan Aug 14 '15 at 19:26
1

@androidplusios.design You need to call getFragmentManager() and not getSupportFragementManager inside your fragment. getFragmentManager() is an instance function of Fragment class and so u can call it inside a Fragment and it will take the containing Fragment class's current instance reference. – Eldhose M Babu Aug 17 '15 at 05:51
Really helpful in implementing fragment inside a fragment. Saved my day. Thanks alot. – Prashant Paliwal Mar 03 '18 at 20:12
This now also works : requireActivity().getSupportFragmentManager() – Waged May 01 '20 at 23:00

Mark · Answer 2 · 2014-07-17T13:28:23.487

85

All you need to do is using

getFragmentManager()

method on your fragment. It will give you the support fragment manager, when you used it while adding this fragment.

Fragment Documentation

edited Jul 17 '14 at 13:28

answered Nov 27 '13 at 09:00

Mark

5,466
3
23
24

9

This should be the accepted answer, it is not advised to keep a reference to the parent activity as suggested by the first answer. – Yoann Hercouet Oct 18 '14 at 12:20
1

@Mark this is a perfect answer and should be the accepted answer. – Varundroid Dec 12 '14 at 00:30
3

This will return android.app.Fragment. In some cases, you need android.support.app.v4.Fragment so it will not work all the time. – Dũng Trần Trung Jan 25 '15 at 02:41
1

how to fix this? i think i need the support.app.v4.Fragment one – Dennis Lukas Jun 28 '16 at 11:22
5

This will return the appropriate FragmentManager. If in an android.support.app.v4.Fragment, it will return the same thing as the getSupportFragmentManager() method in Activity would. The reason the method is called simply getFragmentManager() in this case is because it is not ambigious, unlike in the case of Activity. – blunden Jan 06 '17 at 20:26

Varundroid · Answer 3 · 2015-02-19T23:44:19.237

56

Simply get it like this -

getFragmentManager() // This will also give you the SupportFragmentManager or FragmentManager based on which Fragment class you have extended - android.support.v4.app.Fragment OR android.app.Fragment.

OR

getActivity().getSupportFragmentManager();

in your Fragment's onActivityCreated() method and any method that is being called after onActivityCreated().

edited Feb 19 '15 at 23:44

answered Jul 04 '14 at 02:48

Varundroid

9,135
14
63
93

This is what I use, although I'm quite new to Android development and I'm not sure if it's the correct way of doing things. – Papipo Feb 19 '15 at 15:37
@codecaster you can get the FragmentManager using getFragmentManager() method of Fragment itself as well. I have edited my answer. – Varundroid Feb 19 '15 at 23:42
1

I have a project here that did weird things until I swapped getFragmentManager() for getActivity.getSupportFragmentManager(). – Papipo Feb 20 '15 at 07:51
Hmmm strange. Never ran into an issue like this so far but none of the above solutions is bad so you can use whatever works for you. – Varundroid Feb 20 '15 at 11:40
2

I've looked deep into the classes from all the way. Seems this is the best solution who uses android.support.v4.app.Fragment – DearDhruv Jul 30 '16 at 11:33

score 21 · Answer 4 · answered Sep 21 '17 at 08:26

21

Kotlin users try this answer

(activity as AppCompatActivity).supportFragmentManager

answered Sep 21 '17 at 08:26

Ranjithkumar

16,071
12
120
159

3

Good thing you have put this here, otherwise it would drive me crazy Ty – MePo Oct 05 '17 at 11:13

bsautner · Answer 5 · 2017-12-09T17:04:12.433

16

if you have this problem and are on api level 21+ do this:

   map = ((SupportMapFragment) getChildFragmentManager().findFragmentById(R.id.map))
                    .getMap();

this will get the map when used inside of a fragment.

edited Dec 09 '17 at 17:04

answered Feb 16 '16 at 19:50

bsautner

4,479
1
36
50

1

I tried all of the suggested code fixes above, but couldn't get any of them to work. getChildFragmentManager() did the trick! Thx. – John Ward Nov 03 '16 at 21:02
how about api level below 21? Api level 19 for example? – Aliton Oliveira Nov 29 '19 at 18:04

score 15 · Answer 6 · edited Dec 29 '22 at 13:54

15

in java you can replace with

getChildFragmentManager()

in kotlin,

childFragmentManager

edited Dec 29 '22 at 13:54

General Grievance

4,555
31
31
45

answered Feb 28 '20 at 07:45

Vanya Rachel

1,329
1
18
20

score 14 · Answer 7 · answered Jun 01 '20 at 18:39

14

The simple new way of doing it in kotlin

requireActivity().supportFragmentManager

answered Jun 01 '20 at 18:39

Reza

845
13
18

score 9 · Answer 8 · answered Feb 01 '21 at 16:43

getFragmentManager() has been deprecated in favor of getParentFragmentManager() to make it clear that you want to access the fragment manager of the parent instead of any child fragments.

Simply use getParentFragmentManager() in Java or parentFragmentManager in Kotlin.

score 7 · Answer 9 · answered Jul 04 '16 at 16:07

7

My Parent Activity extends AppCompatActivity so I had to cast my context to AppCompatActivity instead of just Activity.

eg.

FragmentAddProduct fragmentAddProduct = FragmentAddProduct.newInstance();
FragmentTransaction fragmentTransaction = ((AppCompatActivity)mcontext).getSupportFragmentManager().beginTransaction();

answered Jul 04 '16 at 16:07

Akinola Olayinka

841
7
11

2

`((AppCompatActivity) mContext)` part was **EXACTLY** what i was looking for. Thank you! – sHOLE Aug 23 '17 at 08:39

score 6 · Answer 10 · answered Jan 30 '15 at 02:55

You can use getActivity().getSupportFragmentManager() anytime you want to getSupportFragmentManager.

hierarchy is Activity -> fragment. fragment is not capable of directly calling getSupportFragmentManger but Activity can . Thus, you can use getActivity to call the current activity which the fragment is in and get getSupportFragmentManager()

score 4 · Answer 11 · answered May 25 '19 at 09:22

4

((AppCompatActivity) getActivity()).getSupportFragmentManager()

answered May 25 '19 at 09:22

Diako Hasani

1,384
13
14

score 3 · Answer 12 · answered May 27 '17 at 17:28

3

do this in your fragment

getActivity().getSupportFragmentManager()

answered May 27 '17 at 17:28

philip mudenyo

714
8
8

score 3 · Answer 13 · answered Apr 27 '18 at 18:17

3

getActivity().getFragmentManager() This worked or me.

Also take a look at here.

answered Apr 27 '18 at 18:17

Aravindh Gopi

2,083
28
36

score 3 · Answer 14 · answered Aug 08 '22 at 05:28

3

if you are using fragment manager in the activity

getSupportFragmentManager()

supportFragmentManager

if you are using fragment manager in the fragment

childFragmentManager

answered Aug 08 '22 at 05:28

Anshul Nema

281
3
3

score 2 · Answer 15 · answered Mar 07 '18 at 22:43

2

The following code does the trick for me

 SupportMapFragment mapFragment = ((SupportMapFragment) getChildFragmentManager().findFragmentById(R.id.map));
    mapFragment.getMapAsync(this);

answered Mar 07 '18 at 22:43

olajide

972
1
13
26

score 2 · Answer 16 · answered Jul 19 '19 at 10:02

2

You can use childFragmentManager inside Fragments.

answered Jul 19 '19 at 10:02

Kishan Solanki

13,761
4
85
82

score 1 · Answer 17 · edited Dec 29 '16 at 10:50

1

You can simply access like

Context mContext;

public View onCreateView(LayoutInflater inflater,
                             @Nullable ViewGroup container, @Nullable Bundle savedInstanceState) {

mContext = getActivity();

}

and then use

FragmentManager fm = ((FragmentActivity) mContext)
                        .getSupportFragmentManager();

edited Dec 29 '16 at 10:50

HebeleHododo

3,620
1
29
38

answered Dec 29 '16 at 10:47

Ashwini.patil

102
4

score 1 · Answer 18 · answered Jan 09 '20 at 00:13

Some Kotlin code to use supportFragmentManager inside a Fragment.

  override fun onCreateView(
      inflater: LayoutInflater,
      container: ViewGroup?,
      savedInstanceState: Bundle?

  ): View? {

    super.onCreateView(inflater, container, savedInstanceState)
    val rootView = inflater.inflate(R.layout.fragment_home, container, false)

    // ....

    if (rootView.home_play_btn != null) {

      rootView.home_play_btn.setOnClickListener {
        val fragment: BaseFragment = ListFragment.newInstance()
        val fragManager: FragmentManager = (activity as AppCompatActivity).supportFragmentManager
        fragManager.beginTransaction()
            .replace(R.id.content_home_frame, fragment, TAG).commit()

      }

score 1 · Answer 19 · answered Dec 16 '21 at 08:20

Best way to get fragmentManager inside of a fragment is to call the new method

getParentFragmentManager()

or use the property access syntax in kotlin files

parentFragmentManager

this specifies the fragmentManager that is to be loaded (choosing between child and parent fragments )

score 0 · Answer 20 · answered Jul 17 '14 at 09:07

0

Try this:

private SectionsPagerAdapter mSectionsPagerAdapter = new SectionsPagerAdapter(getActivity().getSupportFragmentManager());

answered Jul 17 '14 at 09:07

Maddy Sharma

4,870
2
34
40

What is your requirement, I think your requirement is to define a pager inside another pager with the help of fragments inside fragments..! i.e. you need to swipe a layout inside a swippable layout? – Maddy Sharma Jul 17 '14 at 12:17
1

the reason @V.J. asked you to expand your answer is because a line of code is not a good quality answer. Many people other than the original asker of the question will see your answer and may want to use it to solve their own problem. It would be helpful to those users if you actually explained what the original problem was with the question, why it didn't work, and why you solution does work. – psubsee2003 Jul 17 '14 at 13:19

score 0 · Answer 21 · edited Aug 15 '17 at 06:38

0

getSupportFragmentManager() used when you are in activity and want to get a fragment but in the fragment you can access

getSupportFragmentManager()

by use another method called getFragmentMangaer() works the same like getSupportFragmentManager() and you can use it like you used to:

fragmentTransaction =getFragmentManager().beginTransaction();

edited Aug 15 '17 at 06:38

u32i64

2,384
3
22
36

answered Aug 15 '17 at 05:06

moahmed ayed

636
7
10

uul · Answer 22 · 2022-07-05T08:50:46.573

I use this code and it's work:

val profileFragment = ProfileFragment()
val fragmentManager = parentFragmentManager
fragmentManager.beginTransaction().apply {
                            replace(R.id.fragment_main, profileFragment, ProfileFragment::class.java.simpleName)
                            addToBackStack(null)
                            commit()

the R.id.fragment_main is the main layout that you used. if you used main activity, then you can give id for the layout.

How can I access getSupportFragmentManager() in a fragment?

22 Answers22

Linked

Related