Android Vitals报java.lang.IllegalArgumentException异常求助

我在Android Vitals中收到该通用错误，但日志未上报具体Activity。该错误仅发生在Android 11和Android 12设备上，异常堆栈如下：

Exception java.lang.IllegalArgumentException:
  at android.view.View.onRestoreInstanceState (View.java:20879)
  at android.view.View.dispatchRestoreInstanceState (View.java:20851)
  at android.view.ViewGroup.dispatchRestoreInstanceState (ViewGroup.java:4067)
  at android.view.View.restoreHierarchyState (View.java:20829)
  at androidx.fragment.app.Fragment.restoreViewState (Fragment.java:689)
  at androidx.fragment.app.Fragment.restoreViewState (Fragment.java:3151)
  at androidx.fragment.app.Fragment.performActivityCreated (Fragment.java:3142)
  at androidx.fragment.app.FragmentStateManager.activityCreated (FragmentStateManager.java:579)
  at androidx.fragment.app.FragmentStateManager.moveToExpectedState (FragmentStateManager.java:264)
  at androidx.fragment.app.FragmentStore.moveToExpectedState (FragmentStore.java:113)
  at androidx.fragment.app.FragmentManager.moveToState (FragmentManager.java:1433)
  at androidx.fragment.app.FragmentManager.dispatchStateChange (FragmentManager.java:2977)
  at androidx.fragment.app.FragmentManager.dispatchActivityCreated (FragmentManager.java:2895)
  at androidx.fragment.app.FragmentController.dispatchActivityCreated (FragmentController.java:263)
  at androidx.fragment.app.FragmentActivity.onStart (FragmentActivity.java:351)
  at androidx.appcompat.app.AppCompatActivity.onStart (AppCompatActivity.java:246)
  at android.app.Instrumentation.callActivityOnStart (Instrumentation.java:1435)
  at android.app.Activity.performStart (Activity.java:8097)
  at android.app.ActivityThread.handleStartActivity (ActivityThread.java:3571)
  at android.app.servertransaction.TransactionExecutor.performLifecycleSequence (TransactionExecutor.java:221)
  at android.app.servertransaction.TransactionExecutor.cycleToPath (TransactionExecutor.java:201)
  at android.app.servertransaction.TransactionExecutor.executeLifecycleState (TransactionExecutor.java:173)
  at android.app.servertransaction.TransactionExecutor.execute (TransactionExecutor.java:97)
  at android.app.ActivityThread$H.handleMessage (ActivityThread.java:2144)
  at android.os.Handler.dispatchMessage (Handler.java:106)
  at android.os.Looper.loop (Looper.java:240)
  at android.app.ActivityThread.main (ActivityThread.java:8000)
  at java.lang.reflect.Method.invoke (Method.java)
  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:603)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:947)

可能的错误原因 #

• View状态数据不兼容：View的onSaveInstanceState保存的状态数据，在onRestoreInstanceState时无法被正确解析。常见于自定义View重写状态保存/恢复方法时，数据格式不一致，或者状态数据被意外篡改。
• Fragment状态恢复冲突：从堆栈来看错误触发在Fragment恢复View状态的阶段，可能是Fragment被异常销毁重建时，View状态数据已损坏；或是嵌套Fragment场景下，不同Fragment的View ID重复，导致状态恢复时数据混淆。
• Android 11/12版本校验强化：这两个版本对View状态恢复的校验逻辑比旧版本更严格，比如对Parcelable数据的合法性检查更苛刻，旧版本能兼容的非法数据在这两个版本直接抛出异常。

排查建议 #

• 检查自定义View实现：逐一排查所有自定义View的onSaveInstanceState和onRestoreInstanceState方法，确保保存的Parcelable数据格式正确，恢复时没有类型转换错误。
• 验证View ID唯一性：确认所有布局（包括Fragment布局）中的View ID没有重复，重复ID会导致状态恢复时数据映射错误。
• 添加日志监控：在Fragment.onRestoreViewState或自定义View的恢复方法中添加日志，记录恢复的状态数据，复现问题时定位具体出错的View。
• 覆盖重建场景测试：重点测试App进入后台再恢复、系统内存不足导致Activity/Fragment重建的场景，这类场景是状态恢复错误的高发场景。

内容的提问来源于stack exchange，提问作者dma123