我有一个带有接受多个参数的构造函数的Fragment
。我的应用程序在开发过程中运行良好,但在生产中,我的用户有时会看到这种崩溃:
android.support.v4.app.Fragment$InstantiationException: Unable to instantiate fragment
make sure class name exists, is public, and has an empty constructor that is public
我可以按照此错误消息的建议创建一个空构造函数,但这对我来说没有意义,因为从那时起,我必须调用一个单独的方法来完成设置Fragment
。
我很好奇为什么这种崩溃只会偶尔发生。也许我使用ViewPager
不正确?我自己实例化了所有的Fragment
,并将它们保存在Activity
中的列表中。我不使用FragmentManager
事务,因为我看到的ViewPager
示例不需要它,并且在开发过程中似乎一切正常。
是的,他们有。
无论如何,您不应该真正覆盖构造函数。您应该定义一个newInstance()
静态方法并通过参数(bundle)传递任何参数
例如:
public static final MyFragment newInstance(int title, String message) {
MyFragment f = new MyFragment();
Bundle bdl = new Bundle(2);
bdl.putInt(EXTRA_TITLE, title);
bdl.putString(EXTRA_MESSAGE, message);
f.setArguments(bdl);
return f;
}
当然,以这种方式抓住args:
@Override
public void onCreate(Bundle savedInstanceState) {
title = getArguments().getInt(EXTRA_TITLE);
message = getArguments().getString(EXTRA_MESSAGE);
//...
//etc
//...
}
然后您将从您的片段管理器中实例化,如下所示:
@Override
public void onCreate(Bundle savedInstanceState) {
if (savedInstanceState == null){
getSupportFragmentManager()
.beginTransaction()
.replace(R.id.content, MyFragment.newInstance(
R.string.alert_title,
"Oh no, an error occurred!")
)
.commit();
}
}
这样,如果分离并重新附加,则可以通过参数存储对象状态。很像附加到Intents的捆绑包。
原因-额外阅读
我想我会向想知道原因的人解释原因。
如果您检查:https://android.googlesource.com/platform/frameworks/base/ /master/core/java/android/app/Fragment.java
您将在Fragment
类中看到instantiate(…)
方法调用newInstance
方法:
public static Fragment instantiate(Context context, String fname, @Nullable Bundle args) {
try {
Class<?> clazz = sClassMap.get(fname);
if (clazz == null) {
// Class not found in the cache, see if it's real, and try to add it
clazz = context.getClassLoader().loadClass(fname);
if (!Fragment.class.isAssignableFrom(clazz)) {
throw new InstantiationException("Trying to instantiate a class " + fname
+ " that is not a Fragment", new ClassCastException());
}
sClassMap.put(fname, clazz);
}
Fragment f = (Fragment) clazz.getConstructor().newInstance();
if (args != null) {
args.setClassLoader(f.getClass().getClassLoader());
f.setArguments(args);
}
return f;
} catch (ClassNotFoundException e) {
throw new InstantiationException("Unable to instantiate fragment " + fname
+ ": make sure class name exists, is public, and has an"
+ " empty constructor that is public", e);
} catch (java.lang.InstantiationException e) {
throw new InstantiationException("Unable to instantiate fragment " + fname
+ ": make sure class name exists, is public, and has an"
+ " empty constructor that is public", e);
} catch (IllegalAccessException e) {
throw new InstantiationException("Unable to instantiate fragment " + fname
+ ": make sure class name exists, is public, and has an"
+ " empty constructor that is public", e);
} catch (NoSuchMethodException e) {
throw new InstantiationException("Unable to instantiate fragment " + fname
+ ": could not find Fragment constructor", e);
} catch (InvocationTargetException e) {
throw new InstantiationException("Unable to instantiate fragment " + fname
+ ": calling Fragment constructor caused an exception", e);
}
}
http://docs.oracle.com/javase/6/docs/api/java/lang/Class.html#newInstance()解释了为什么在实例化时它会检查访问器是public
并且该类加载器允许访问它。
总的来说,这是一个非常讨厌的方法,但它允许FragmentManger
杀死并重新创建带有状态的Fragments
。(Android子系统对Activity
做类似的事情)。
示例类
我被问到很多关于调用newInstance
的问题。不要将其与类方法混淆。整个类示例应该显示用法。
/**
* Created by chris on 21/11/2013
*/
public class StationInfoAccessibilityFragment extends BaseFragment implements JourneyProviderListener {
public static final StationInfoAccessibilityFragment newInstance(String crsCode) {
StationInfoAccessibilityFragment fragment = new StationInfoAccessibilityFragment();
final Bundle args = new Bundle(1);
args.putString(EXTRA_CRS_CODE, crsCode);
fragment.setArguments(args);
return fragment;
}
// Views
LinearLayout mLinearLayout;
/**
* Layout Inflater
*/
private LayoutInflater mInflater;
/**
* Station Crs Code
*/
private String mCrsCode;
@Override
public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
mCrsCode = getArguments().getString(EXTRA_CRS_CODE);
}
@Override
public View onCreateView(LayoutInflater inflater, ViewGroup container, Bundle savedInstanceState) {
mInflater = inflater;
return inflater.inflate(R.layout.fragment_station_accessibility, container, false);
}
@Override
public void onViewCreated(View view, Bundle savedInstanceState) {
super.onViewCreated(view, savedInstanceState);
mLinearLayout = (LinearLayout)view.findViewBy(R.id.station_info_accessibility_linear);
//Do stuff
}
@Override
public void onResume() {
super.onResume();
getActivity().getSupportActionBar().setTitle(R.string.station_info_access_mobility_title);
}
// Other methods etc...
}
正如https://stackoverflow.com/a/16064418/1319061的问题中所述,如果您正在创建Fragment的匿名子类,也会发生此错误,因为匿名类不能有构造函数。
不要创建Fragment的匿名子类:-)
是的,正如您所看到的,支持包也实例化了片段(当它们被销毁和重新打开时)。您的Fragment
子类需要一个公共空构造函数,因为这就是框架所调用的。