Should we be using setTargetFragment()? I thought Fragments should not be communicating with each other

The android developer tutorials recommend me using the host activities of fragments to pass around data and whatnot, so why is there a set/get target fragment method?

My application thus far contains a host activity, and a fragment, which has a button that launches a DialogFragment, in which there is a button that launches ANOTHER DialogFragment. Using setTargetFragment/getTargetFragment has made this whole ordeal somewhat confusing though, so I am thinking of reimplementing to let my main activity handle methods through my main fragment’s custom interface.

  • Crop Image with face detection in android
  • How to get the file path from URI?
  • How to take google maps snapshot without actually displaying the map
  • How to make a grid layout of CardViews with variable height?
  • Eclipse LogCat shows only the first letter from each message
  • How to display my location on Google Maps for Android API v2
  • Is this the right way of thinking? Or is there no harm in using setTargetFragment? Can anyone provide good and bad examples of using it?

    Related posts:

    How to set custom ActionBar color / style?
    Android Studio: Unregistered VCS root detected
    Android: Is there a way to get the size of a RemoteViews object?
    How to draw a circle with animation in android with circle size based on a value
    Rotate animation android
    Android: simple time counter
  • Add github library as dependency to Android-Studio project
  • menu inflating calls multiple times at fragment's onCreateOptionsMenu
  • Android-Is it possible to add a clickable link into a string resource
  • Android Unknown Command 'crunch'
  • Will Xamarin Android execute OnCreateView when the IntPtr constructor is called?
  • ProGuard didnt compile with Joda Time used in Windows
  • 2 Solutions collect form web for “Should we be using setTargetFragment()? I thought Fragments should not be communicating with each other”

    I don’t think there is implicit harm in using setTargetFragment, however, I would only use it in very specific circumstances. For example, if the target fragment is only going to ever be used by the fragment (taking into account object reuse and designing your classes to be reusable when possible) and even then, sparingly.

    By using them too much, you will end up with what you’re seeing – confusing code that is hard to follow and maintain. On the outset, by marshaling everything through your activity you maintain a “flat” hierarchy that is simple to follow and maintain.

    I think the decision to use setTargetFragment or not is a coding-style/philosophical one that, with wisdom and experience, it “feels” right or wrong. Maybe on your case, by evidence that you are questioning your older code, you are gaining that wisdom 🙂

    Also, you may end up with exception of no target fragment found in fragment manager. This happens if after rotation (or other config change) your target fragment will not be readded to the fragment manager by the time when caller fragment will be adding.

    Imagine you have some sort of Confirmation fragment which you add from MainFragment as so:

    ConfirmationFragment frag = new ConfirmationFragment();
    frag.setTargetFragment(this, 0);
    getFragmentManager().beginFragmentTransaction().add(, frag).commit(); 

    Now on some confirmation button click you invoke a method from MainFragment by calling:


    This is pretty and simple, but if you will rotate the screen and for some reason ConfirmationFragment will be added to FragmentManager before MainFragment, exception will be thrown, stating that target fragment is not found in the fragment manager

    Android Babe is a Google Android Fan, All about Android Phones, Android Wear, Android Dev and Android Games Apps and so on.