Using dialog fragments for android API version 10 or below - android

How to show a created dialog for API version 10? I have changed my MainActivity's extension to FragmentActivity and getFragmentManager() to getSupportFragmentManager().
But then in my code snippet-
DuplicateColMessage duplicate_dialog =new DuplicateColMessage();
message="Column "+refinedcol[index].toUpperCase()+" already has data";
duplicate_dialog.show(getSupportFragmentManager(), DROPBOX_SERVICE);
The duplicate_dialog.show() method complains about getSupportFragmentManager. How do I overcome this?

Related

get v4.app.FragmentManager from Flutter Plugin

i try to get FragmentManager in my android flutter plugin. In my case i need v4.app.FragmentManager.
but in PluginRegistry Registrar. i just get app.FragmentManager from Registrar.activity().fragmentManager
Since i use FlutterFragmentActivity which extend v4.app.FragmentActivity, you can see the code in here.
So i think it's possible to get v4.app.FragmentManager().
anyone have idea how to reach that ?
finally, i solve this problem with simple fact:
First, Registrar.activity is app.activity which is if you want to get fragment manager you only get app.FragmentManager. So we can't call getSupportFragmentManager() function to get v4.app.FragmentManager.
Second, FlutterActivity / FLutterFragmentActivity is extending v4.app.Activity / v4.app.FragmentActivity so we can use getSupportFragmentManager() in this case.
So simply in Flutter Android plugin I just declare Activity / FragmentActivity equals with what MainActivity extended like. After that I can use getSupportFragmentManager() to get v4.app.FragmentManager. the code like below :
v4.app.Activity act = (Activity)vRegistrar.activity();
v4.app.FragmentManager = act.getSupportFragmentManger();
Hope it's helpful. Thanks...

Why is Android O failing with "does not belong to this FragmentManager!"

I have migrated my application to Android O in Android Studio 3
Running on an Android O emulator all my dialogFragments now fail with :-
java.lang.IllegalStateException: Fragment MyDialogFragment{43ccf50 #2 MyDialogFragment} declared target fragment SettingsFragment{ceed549 #0 id=0x7f0f0142 android:switcher:2131689794:0} that does not belong to this FragmentManager!
at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1316)
at android.support.v4.app.FragmentManagerImpl.moveFragmentToExpectedState(FragmentManager.java:1624)
at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1689)
at android.support.v4.app.BackStackRecord.executeOps(BackStackRecord.java:794)
at android.support.v4.app.FragmentManagerImpl.executeOps(FragmentManager.java:2470)
at android.support.v4.app.FragmentManagerImpl.executeOpsTogether(FragmentManager.java:2260)
at android.support.v4.app.FragmentManagerImpl.optimizeAndExecuteOps(FragmentManager.java:2213)
at android.support.v4.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:2122)
at android.support.v4.app.FragmentManagerImpl$1.run(FragmentManager.java:746)
at android.os.Handler.handleCallback(Handler.java:769)
at android.os.Handler.dispatchMessage(Handler.java:98)
at android.os.Looper.loop(Looper.java:164)
at android.app.ActivityThread.main(ActivityThread.java:6535)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:240)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:767)
I have made no code changes whatsoever.
What has changed in Android O that previously working DialogFragments now fail display?
Android Studio 3.0 Canary 1
Build #AI-171.4010489, built on May 15, 2017
JRE: 1.8.0_112-release-b736 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Mac OS X 10.11.6
compileSdkVersion 'android-O'
buildToolsVersion "26.0.0-rc2"
AndroidManifest.xml
defaultConfig {
minSdkVersion 16
targetSdkVersion 'O'
}
compile 'com.android.support:appcompat-v7:26.0.0-beta1'
compile 'com.android.support:cardview-v7:26.0.0-beta1'
compile 'com.android.support:design:26.0.0-beta1'
compile 'com.android.support:percent:26.0.0-beta1'
dependencies {
classpath 'com.android.tools.build:gradle:3.0.0-alpha1'
}
For me this was not only an issue on Android O but also on older versions.
The oldest version I tested was API Level 16.
I was instantiating my fragments using this code:
MyFragment myFragment = MyFragment.newInstance();
myFragment.setTargetFragment(ParentFragment.this, 0);
myFragment.show(getActivity().getSupportFragmentManager(), null);
Where ParentFragment.this is a custom class extending android.support.v4.app.Fragment, MyFragment also extends this class and is a child fragment of the ParentFragment fragment (hence it's name).
I thought that I had to use a SupportFragmentManager (the getSupportFragmentManager() method) because I am using a fragment of the support package so I tried to call getActivity().getSupportFragmentManager() to get an activity reference that supported this method.
This does not seem to be the correct way though.
I changed those calls to:
MyFragment myFragment = MyFragment.newInstance();
myFragment.setTargetFragment(ParentFragment.this, 0);
myFragment.show(getFragmentManager(), null);
so the fragment decides on it's own which FragmentManager to use and the error is gone now.
Hope this helps someone.
I had the same problem, definitely an android bug. It happens when you are showing a fragment from another fragment using it as target. As workaround you can use:
if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O)
getActivity().getFragmentManager().beginTransaction().add(dialogFrag, "dialog").commit();
else
getChildFragmentManager().beginTransaction().add(dialogFrag,"dialog").commit();
I just faced the same issues in the project that I am currently working on when we moved to Android Studio 3 and upgraded the support library to version 26. All of a sudden, without changing the code, we got tons of this exception. In the end I found out the following:
Google added a new "sanity check" in the sources of the v4 Fragment Manager in January this year (not sure into what release that went) that refuses to add a fragment using a Fragment Manager, if it has a target fragment set and the target fragment cannot be found in the active fragments of the same Fragment Manager. The patch is described in detail here
Ealier versions seem to not have cared about that. Took me a few days to update all the areas in our code where fragments that were added using the Support Fragment Manager used the Child Fragment Manager for their subfragments with the parent fragment as target. Well, late penalty for writing bad code.
I had the same case as Markus Ressel but I was using getChildFragmentManager(). I replaced that with getFragmentManager() and it resolved the issue.
UPDATE: I've now been working with childFragmentManager and have some feedback.
When dealing with inner fragments that are hosted by a fragment (so a fragment within a fragment) use the childFragmentManager. This fragment manager differs from the activities getSupportFragmentManager. The two are not the same. It's a separation of concerns.
So I've made a rule that fragments hosting child fragments will always use the childFragmentManager and things not inside host fragments can use getSupportfragmentManager.
Recently, my app experienced the same issue when I targeted it for Android O. As a solution, use:
myDialogFragment.show(SettingsFragment.this.getFragmentManager(), TAG);
instead of:
myDialogFragment.show(getFragmentManager(), TAG);
// or
myDialogFragment.show(getSupportFragmentManager(), TAG);
// or
myDialogFragment.show(getChildFragmentManager(), TAG);
while working on an app, I encountered the same problem and I solved it by (in kotlin)
chooseRegionFragment.setTargetFragment(this#ParentFragment, REQUEST_CODE_CHOOSE_REGION)
chooseRegionFragment.show(this#ParentFragment.parentFragmentManager, TAG)
it translates to
chooseRegionFragment.setTargetFragment(ParentFragment.this, REQUEST_CODE_CHOOSE_REGION);
chooseRegionFragment.show(ParentFragment.this.getParentFragmentManager, TAG);
in java
my app work well until upgrade target version to 27 then i face same issue when call setTargetFragment (Fragment fragment,
int requestCode)
example:
chooseRegionFragment.setTargetFragment(ParentFragment.this, REQUEST_CODE_CHOOSE_REGION);
just change to:
chooseRegionFragment.setTargetFragment(getRootParentFragment(this), REQUEST_CODE_CHOOSE_REGION);
getRootParentFragment(this) this method will find root parent of fragments for you
/**
* find root parent of fragment
*/
public static Fragment getRootParentFragment(Fragment fragment) {
Fragment parent = fragment.getParentFragment();
if(parent == null)
return fragment;
else
return getRootParentFragment(parent);
}
Use below solution and you do not need to worry about which fragment managers you are dealing with,
Assuming that you must have used a BaseFragment.
First create an interface:
public interface OnRequestUpdateListener {
void onRequestUpdate(final int requestCode, final Intent data);
void setRequestFragment(final BaseFragment requestFragment, int requestCode);
BaseFragment getRequestFragment();
int getRequestCode();
}
Implement that interface in your BaseFragment
public class BaseFragment extends Fragment implements OnRequestUpdateListener {
private BaseFragment requestFragment;
private int requestCode;
#Override
public void onRequestUpdate(int requestCode, Intent data) {
// you can implement your logic the same way you do in onActivityResult
}
#Override
public void setRequestFragment(BaseFragment requestFragment, int requestCode) {
this.requestFragment = requestFragment;
this.requestCode = requestCode;
}
#Override
public BaseFragment getRequestFragment() {
return requestFragment;
}
#Override
public int getRequestCode() {
return requestCode;
}
}
Then, replace the setTargetFragment with setRequestFragment and replace getTargetFragment with getRequestFragment.
Here, you could also user onRequestUpdate in place of onActivityResult.
This is a custom solution without bothering about the which fragment manager you are using.
Using getFragmentManager() instead of getChildFragmentManager() would also work but it affects getParentFragment(). If you do not use a getChildFragmentManager() for nested fragment then you will not be able the get the parent fragment by using getParentFragment() in child/nested fragment.

Using actionbarsherlock with android-support-v4 (Version 23)

I'm developing an app with actionbarsherlock and the ABS project is currently using android-support-v4 library (Version 18). Now I want to extend my project to support Android 6.0 and in order to use some of the methods like
ContextCompat.checkSelfPermission(thisActivity, Manifest.permission.WRITE_CALENDAR)
or
ActivityCompat.shouldShowRequestPermissionRationale(thisActivity, Manifest.permission.READ_CONTACTS)
I require support library version 23. But ABS project is not compatible with this latest library and gives error like mAdded cannot be resolved or is not a field in Watson.java
Also, please don't suggest me to use AppCompatActivity instead of ABS as I tried it but getting stuck in a web of other mess as my project is quite big.
I'm facing the same problem. Here's my solution:
Clone ActionBarSherlock
No instance field mFragments of type Landroid/support/v4/app/FragmentManagerImpl;
// android.support.v4.app.FragmentActivity
// com.android.support:support-v4:22.+
final FragmentManagerImpl mFragments = new FragmentManagerImpl();
// com.android.support:support-v4:23.+
final FragmentController mFragments = FragmentController.createController(new HostCallbacks());
// android.support.v4.app.FragmentManager.FragmentManagerImpl
ArrayList<Fragment> mAdded;
So we need to get instance of FragmentManagerImpl to access mAdded field
// android.support.v4.app.FragmentActivity
public FragmentManager getSupportFragmentManager() {
return mFragments.getSupportFragmentManager();
}
// android.support.v4.app.FragmentController
public FragmentManager getSupportFragmentManager() {
return mHost.getFragmentManagerImpl();
}
Add the following method to the android.support.v4.app.Watson class
#Nullable
private List<Fragment> getAddedFragments() {
return ((FragmentManagerImpl) getSupportFragmentManager()).mAdded;
}
Add the following code to onCreatePanelMenu, onPreparePanel and onMenuItemSelected methods and replace mFragments.mAdded with fragments
List<Fragment> fragments = getAddedFragments();
FloatMath
Historically these methods were faster than the equivalent double-based
{java.lang.Math} methods. On versions of Android with a JIT they
became slower and have since been re-implemented to wrap calls to
{java.lang.Math}. {java.lang.Math} should be used in
preference.
All methods were removed from the public API in version 23.
#deprecated Use {java.lang.Math} instead.
Replace all of occurrences of FloatMath with Math in com.actionbarsherlock.internal.nineoldandroids.view.animation.AnimatorProxy

findFragmentById(R.id.map) returns null in Android L

While testing a location based app in Android 4.4 we were able to properly see and use map via Android maps v2
Since the time I upgraded to Android L it is not able to fetch MapFragment with the following code:
In MainActivity there's a FrameLayout in which I load ShowMapFragment.
In ShowMapFragment there is a MapFragment to display map.
Inside 'OnCreateView()' method
mapFragment = (MapFragment)getFragmentManager().findFragmentById(R.id.map);
map = mapFragment.getMap();
mapFragment is coming as null. Any help on this?
Got it. Posting this if anyone else faces the same issue. Basically we have to use getChildFragmentManager() instead of getFragmentManager() because the MapFragment is inside another fragemnt. See the answer by Rhisiart here.

How to avoid NoClassDefFoundError with different Android API versions

I'm developing an application for APIs from v10 to v17.
My activity implements OnDragListener which is available only from API v14.
public class MyActivity extends Activity implements View.OnDragListener {
....
}
So, when application is installed on device with API v10 it fails to load activity with java.lang.NoClassDefFoundError.
I understand that this won't work on API v10, that's OK. I'm handling this inside the activity.
I just want to know What is the practice to handle different API versions when it comes to features like this?
First of all you can check API levels and depending on that to execute or not your code. For example :
if(Build.VERSION.SDK_INT < Build.VERSION_CODES.HONEYCOMB){
// don't use it.
} else {
// use the new API :
// myView.setOnDragListener(...);
}
You should not implement interfaces from new API's in Activity if you want to support old android versions too. Instead of that use the approach above.
In your case you should not declare the activity to implement View.OnDragListener. Just do the logic in another class and instantiate it only when you need it (I suppose you add the listener only for API >= 14).

Categories

Resources