报错信息：
2018-11-08 10:50:18.155 21051-21051/? E/CrashReport: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.test/com.test.ui.activity.HomeActivity}: java.lang.IllegalArgumentException: Wrong state class, expecting View State but received class android.support.design.widget.CoordinatorLayout$SavedState instead. This usually happens when two views of different type have the same id in the same hierarchy. This view's id is id/title_layout. Make sure other views do not use the same id. at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3194) at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3302) at android.app.ActivityThread.-wrap12(Unknown Source:0) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1891) at android.os.Handler.dispatchMessage(Handler.java:108) at android.os.Looper.loop(Looper.java:166) at android.app.ActivityThread.main(ActivityThread.java:7425) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:245) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:921) Caused by: java.lang.IllegalArgumentException: Wrong state class, expecting View State but received class android.support.design.widget.CoordinatorLayout$SavedState instead. This usually happens when two views of different type have the same id in the same hierarchy. This view's id is id/title_layout. Make sure other views do not use the same id. at android.view.View.onRestoreInstanceState(View.java:17844) at android.view.View.dispatchRestoreInstanceState(View.java:17819) at android.view.ViewGroup.dispatchRestoreInstanceState(ViewGroup.java:3773) at android.view.ViewGroup.dispatchRestoreInstanceState(ViewGroup.java:3781) at android.view.View.restoreHierarchyState(View.java:17797) at android.support.v4.app.Fragment.restoreViewState(Fragment.java:494) at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1486) at android.support.v4.app.FragmentManagerImpl.moveFragmentToExpectedState(FragmentManager.java:1784) at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1852) at android.support.v4.app.FragmentManagerImpl.dispatchStateChange(FragmentManager.java:3269) at android.support.v4.app.FragmentManagerImpl.dispatchActivityCreated(FragmentManager.java:3229) at android.support.v4.app.FragmentController.dispatchActivityCreated(FragmentController.java:201) at android.support.v4.app.FragmentActivity.onStart(FragmentActivity.java:620) at android.support.v7.app.AppCompatActivity.onStart(AppCompatActivity.java:178) at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1339) at android.app.Activity.performStart(Activity.java:7392) at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3157) at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3302) at android.app.ActivityThread.-wrap12(Unknown Source:0) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1891) at android.os.Handler.dispatchMessage(Handler.java:108) at android.os.Looper.loop(Looper.java:166) at android.app.ActivityThread.main(ActivityThread.java:7425) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:245) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:921)问题原因：
布局文件中有两个控件的id是一样的。（对于普通控件，如果id一样，IDE是会提示的，但是对于include文件时，却未做提示，真奇怪。）
activity在创建时，存在相同的id不报错，但是走onRestoreInstanceState流程时，是从之前保存的序列话信息里恢复布局，出现重复id时就报错了。 经过反复测试，只有两个控件是layout类型且layout类型不同而id相同时才会有问题。
开发准则：
开发时，同一布局文件中，不能出现id重复。
安卓开发技术分享:https://blog.csdn.net/yinxing2008/article/details/84555061
