NullPointer when calling Fragment method from activity

edit:

Even though the original answer got pretty close to answering properly, I wanted to edit to bring some knowledge to the case.

The Fragment stack works (under a certain point of view) very similarly to the activity. As fragments are also automatically destroyed and re-created by the framework and have their state saved via the Bundles that get passed around the callbacks (savedInstanceState).

So what's happening is that even though, the activity is being re-created and a new Adapter being called, when supplying Fragments to the ViewPager the adapter first calls findFragmentByTag to the FragmentManager so that the saved states can be re-created, and it only calls public Fragment getItem(int position) if there's none.

So the fragments that you see on the screen are not the objects that were created during AppSectionsPagerAdapter constructor. Those fragments were never used.

Remember that, even though it sounds odd at first sight, that is a very desirable feature. For example: imagine there's an EditText on the fragment and the user filled it with some text. When the fragments gets destroyed, that value will be saved on the Bundle, and when restored the value is still there.

original answer:

"Can't understand why are these objects different." because that's how the framework operates. Fragments are objects that can be destroyed/re-created by the Framework.

99% chances of what is happening is:

• MainActivity.onCreate.onStart.onResume
• MainSectionFragment.onCreateView.onResume
• then it goes to Settings:
• MainSectionFragment.onPause.onDestroyView <<< destroys the view
• MainActivity.onPause.onStop
• when you back from the settings
• MainActivity.onStart.onResume <<< it doesn't call onCreate, it was never destroyed.
• the framework re-creates your fragment automatically
• MainSectionFragment(new instance).onCreateView.onResume
• you click on the refresh button
• MainActivity call the old MainSectionFragment. The MainSectionFragment that the view was already destroyed.

The most direct (and cleaner) way to fix your code will be to make the Fragment handle the menu, simply simple put this in the fragment code, and remove the menu stuff from the activity:

onCreate(Bundle savedInstance){
   setHasOptionsMenu(true);
}

onOptionsItemSelected(MenuItem item){
   if(item.getItemId() == R.id.refresh){
      .. do your stuff here
      return true;
   } else return super.refresh(item);
}

If for some reason that you did not explain you really really must handle the menu in the activity there're other options:

For example: you could send a LocalBroadcast from the activity and have the fragment register/unregister a BroadcastReceiver during onResume/onPause

Or another nice trick: the FragmentPagerAdater uses the following method to create fragment TAG for the FragmentManager:

private static String makeFragmentName(int viewId, long id) {
   return "android:switcher:" + viewId + ":" + id;
}

so then you can add this to your activity and call:

 (MainSectionFragment)getSupportFragmentManager().
     findFragmentByTag(
         makeFragmentName(R.id.pager, mAppSectionsPagerAdapter.getItemId(0)))
           .fetchList();