Inside your DialogFragment, call Fragment.setRetainInstance(boolean) with the value true. You don’t need to save the fragment manually, the framework already takes care of all of this. Calling this will prevent your fragment from being destroyed on rotation and your network requests will be unaffected. You may have to add this code to stop your dialog … Read more
First of all, you should read my blog post for more information (it talks about why this exception happens and what you can do to prevent it). Calling commitAllowingStateLoss() is more of a hack than a fix. State loss is bad and should be avoided at all costs. At the time that onActivityResult() is called, … Read more
ianhanniballake is right. You can get all the functionality of Activity from FragmentActivity. In fact, FragmentActivity has more functionality. Using FragmentActivity you can easily build tab and swap format. For each tab you can use different Fragment (Fragments are reusable). So for any FragmentActivity you can reuse the same Fragment. Still you can use Activity … Read more
Have you added ACTION_MAIN intent filter to your main activity? If you don’t add this, then android won’t know which activity to launch as the main activity. ex: <intent-filter> <action android:name=”android.intent.action.MAIN”/> <action android:name=”com.package.name.MyActivity”/> <category android:name=”android.intent.category.LAUNCHER” /> </intent-filter>
What you’re doing is correct. Fragments don’t have access to the ActionBar APIs, so you have to call getActivity. Unless your Fragment is a static inner class, in which case you should create a WeakReference to the parent and call Activity.getActionBar from there. To set the title for your ActionBar, while using a custom layout, … Read more
mFragmentFavorite in your code is a FragmentActivity which is not the same thing as a Fragment. That’s why you’re getting the type mismatch. Also, you should never call new on an Activity as that is not the proper way to start one. If you want to start a new instance of mFragmentFavorite, you can do … Read more
KISS Answer: Simple use FragmentStatePagerAdapter instead of FragmentPagerAdapter. I got the answer.. Firstly I thought to delete this question as I am doing a very silly mistake but this answer will help someone who is facing the same problem that Instead of FragmentPagerAdapter, use FragmentStatePagerAdapter. As @BlackHatSamurai mentioned in the comment: The reason this works … Read more
A Fragment is a section of an Activity, which has: its own lifecycle receives its own input events can be added or removed while the Activity is running. A Fragment must always be embedded in an Activity. Fragments are not part of the API prior to HoneyComb (3.0). If you want to use Fragments in … Read more
You must write onActivityResult() in your FirstActivity.Java as follows @Override public void onActivityResult(int requestCode, int resultCode, Intent data) { super.onActivityResult(requestCode, resultCode, data); } So this will call your fragment’s onActivityResult() Edit: the solution is to replace getActivity().startActivityForResult(i, 1); with startActivityForResult(i, 1);
You can directly call getParentFragmentManager() to get the fragment manager. Note that getFragmentManager() also works but has been marked as deprecated.