Android的 - onAttach（上下文）不要求API 23上下文、onAttach、Android、API

由网友(不痛不痒不在乎)分享简介：我已经更新了SDK来为片段的最新版本（API 23）和 onAttach（活动）方法pcated德$ P $。因此，而不是使用该方法，现在，我使用 onAttach（上下文）但是这一个生命周期中不叫。该活动是 AppCompatActivity 从V7一个实例，该片段是片段类的一个实例（ android.app.Fra...

我已经更新了SDK来为片段的最新版本（API 23）和 onAttach（活动）方法pcated德$ P $。因此，而不是使用该方法，现在，我使用 onAttach（上下文）但是这一个生命周期中不叫。该活动是 AppCompatActivity 从V7一个实例，该片段是片段类的一个实例（ android.app.Fragment ）。

I've updated the SDK to the latest version (API 23) and the onAttach(Activity) method for fragment is deprecated. So instead of using that method, now I'm using onAttach(Context) but this one is not called during the lifecycle. The activity is an instance of AppCompatActivity from v7 and the fragment is an instance of class Fragment (android.app.Fragment).

任何想法如何获得 onAttach 在API 23的工作？

Any ideas how to get the onAttach working in API 23?

解决方案

我发现一些答案，可以帮助您了解和解决此问题：正如我提到我使用的是活动的支持V7（AppCompatActivity）和android.app片段之前。有关片段显示使用方法getFragmentManager上的活动我得到的片段经理，所以片段经理FragmentManager从android.app一个实例 - >这里的问题如果您用API 23设备上的应用程序（我已经在AS模拟器运行它），你会发现onAttach（上下文）方法将被调用。在此过程中用于示出一个片段由FragmentManager，在特定时刻的onAttach（..）方法被调用。使用getFragmentManager（），你会得到片段管理器实例可以用于以该设备上运行（例如API 22，23）的Android版本。如果该应用程序与API℃的设备上运行; 23 onAttach（上下文）的方法不可用，片段的经理不知道，在API 23有一个方法onAttach（上下文），所以这就是为什么它不叫了API＆LT; 23 - >在对这类问题的解决方案是使用从支持库FragmentManager。

I found some answers that can help you to understand and fix this problem: As I mentioned before I’m using the activity from support v7 (AppCompatActivity) and the fragment from android.app. For showing fragments I get the fragment manager using the method getFragmentManager on the activity, so the fragment manager is an instance of FragmentManager from android.app -> and here is the problem If you run the application on a device with API 23 (I’ve run it on the AS Emulator), you’ll see that the onAttach(Context) method will be called. During the process for showing a fragment by the FragmentManager, at a specific moment the onAttach(..) method is called. Using the getFragmentManager() you’ll get an instance of the fragment manager available for the Android version which is running on that device (for example API 22, 23). In case the application is running on a device with API < 23 the onAttach(Context) method is not available, the fragment manager doesn’t know that in API 23 there is a method onAttach(Context), so that’s why it is not called for the API < 23 -> the solution for this kind of problems is using the FragmentManager from support libraries.

解决方案：

使用getSupportFragmentManager（）会强迫你使用一个片段的支持库。因此，第一个解决方案是与支持LIB（）的片段，用getSupportFragmentManager更换所有的碎片。

Using getSupportFragmentManager() will force you to use a Fragment from the support lib. So the first solution is to replace all fragments with the fragment from support lib and using getSupportFragmentManager().

，我已经实现了解决办法是处理2的可能性的（1.应用程序与API℃的设备上运行; 23，应用程序与API的设备上运行> = 23）。

Solution that I've already implemented is to handle 2 possibilities (1. the app is running on a device with API < 23, the app is running on a device with API >= 23).

不久，我在实现我从这次项目中的所有片段的基类和我说这code有：

Shortly, in my implementation I have a base class for all fragments from the project and I added this code there:

/*
 * onAttach(Context) is not called on pre API 23 versions of Android and onAttach(Activity) is deprecated
 * Use onAttachToContext instead
 */
@TargetApi(23)
@Override
public void onAttach(Context context) {
    super.onAttach(context);
    onAttachToContext(context);
}

/*
 * Deprecated on API 23
 * Use onAttachToContext instead
 */
@SuppressWarnings("deprecation")
@Override
public void onAttach(Activity activity) {
    super.onAttach(activity);
    if (Build.VERSION.SDK_INT < Build.VERSION_CODES.M) {
        onAttachToContext(activity);
    }
}

/*
 * Called when the fragment attaches to the context
 */
protected void onAttachToContext(Context context) {
}

现在我只是覆盖在哪里，我需要这一切碎片onAttachToContext（上下文）方法。

Now I simply override the onAttachToContext(Context) method on all fragments where I need this.

Android的 - onAttach（上下文）不要求API 23上下文、onAttach、Android、API

推荐答案