升级到支持库后,在偏移4752处解组未知类型代码6839391 [英] Unmarshalling unknown type code 6881391 at offset 4752 After Upgrading to Support Libraries 23.2.0

查看:115
本文介绍了升级到支持库后,在偏移4752处解组未知类型代码6839391的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我的应用程序在支持库23.1.1中运行良好.但是,升级到支持库23.2.0后,它开始崩溃.当我从某个活动导航回到主要活动时,就会发生崩溃(例如,我从主要活动的操作栏菜单中打开about活动,然后按返回按钮返回到主要活动,然后崩溃).

My app has been working well at Support Libraries 23.1.1. However, after upgrading to Support Libraries 23.2.0, it starts to crash. The crash happens when I navigate from an activity back to the main activity (for example, I open the about activity from main activity's actionbar menu, then press back button to go back to main activity, then it crashes).

崩溃日志在这里:

致命异常:主要过程:com.myapp.blah.blah,PID:22124 java.lang.RuntimeException:无法启动活动 ComponentInfo {com.myapp.blah.blah/com.myapp.blah.blah.ui.MainActivity}: java.lang.RuntimeException:包裹android.os.Parcel@41d10870: 在偏移量4752处解组未知类型代码6391391 android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2429) 在 android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2493) 在android.app.ActivityThread.access $ 800(ActivityThread.java:166)处 android.app.ActivityThread $ H.handleMessage(ActivityThread.java:1283) 在android.os.Handler.dispatchMessage(Handler.java:102)处 android.os.Looper.loop(Looper.java:136)在 android.app.ActivityThread.main(ActivityThread.java:5584)在 java.lang.reflect.Method.invokeNative(本机方法)位于 java.lang.reflect.Method.invoke(Method.java:515)在 com.android.internal.os.ZygoteInit $ MethodAndArgsCaller.run(ZygoteInit.java:1268) 在com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1084)处 dalvik.system.NativeStart.main(本机方法)由以下原因引起: java.lang.RuntimeException:包裹android.os.Parcel@41d10870: 在偏移量4752处解组未知类型代码6391391 android.os.Parcel.readValue(Parcel.java:2087)在 android.os.Parcel.readArrayMapInternal(Parcel.java:2321)在 android.os.Bundle.unparcel(Bundle.java:249)在 android.os.Bundle.getSparseParcelableArray(Bundle.java:1273)在 com.android.internal.policy.impl.PhoneWindow.restoreHierarchyState(PhoneWindow.java:1884) 在android.app.Activity.onRestoreInstanceState(Activity.java:989)处 android.app.Activity.performRestoreInstanceState(Activity.java:961)在 android.app.Instrumentation.callActivityOnRestoreInstanceState(Instrumentation.java:1145) 在 android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2407) 在 android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2493)? 在android.app.ActivityThread.access $ 800(ActivityThread.java:166)吗?在 android.app.ActivityThread $ H.handleMessage(ActivityThread.java:1283)? 在android.os.Handler.dispatchMessage(Handler.java:102)吗?在 android.os.Looper.loop(Looper.java:136)?在 android.app.ActivityThread.main(ActivityThread.java:5584)?在 java.lang.reflect.Method.invokeNative(本机方法)?在 java.lang.reflect.Method.invoke(Method.java:515)?在 com.android.internal.os.ZygoteInit $ MethodAndArgsCaller.run(ZygoteInit.java:1268)? 在com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1084)吗?在 dalvik.system.NativeStart.main(本机方法)?

FATAL EXCEPTION: main Process: com.myapp.blah.blah, PID: 22124 java.lang.RuntimeException: Unable to start activity ComponentInfo{com.myapp.blah.blah/com.myapp.blah.blah.ui.MainActivity}: java.lang.RuntimeException: Parcel android.os.Parcel@41d10870: Unmarshalling unknown type code 6881391 at offset 4752 at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2429) at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2493) at android.app.ActivityThread.access$800(ActivityThread.java:166) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1283) at android.os.Handler.dispatchMessage(Handler.java:102) at android.os.Looper.loop(Looper.java:136) at android.app.ActivityThread.main(ActivityThread.java:5584) at java.lang.reflect.Method.invokeNative(Native Method) at java.lang.reflect.Method.invoke(Method.java:515) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1268) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1084) at dalvik.system.NativeStart.main(Native Method) Caused by: java.lang.RuntimeException: Parcel android.os.Parcel@41d10870: Unmarshalling unknown type code 6881391 at offset 4752 at android.os.Parcel.readValue(Parcel.java:2087) at android.os.Parcel.readArrayMapInternal(Parcel.java:2321) at android.os.Bundle.unparcel(Bundle.java:249) at android.os.Bundle.getSparseParcelableArray(Bundle.java:1273) at com.android.internal.policy.impl.PhoneWindow.restoreHierarchyState(PhoneWindow.java:1884) at android.app.Activity.onRestoreInstanceState(Activity.java:989) at android.app.Activity.performRestoreInstanceState(Activity.java:961) at android.app.Instrumentation.callActivityOnRestoreInstanceState(Instrumentation.java:1145) at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2407) at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2493)? at android.app.ActivityThread.access$800(ActivityThread.java:166)? at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1283)? at android.os.Handler.dispatchMessage(Handler.java:102)? at android.os.Looper.loop(Looper.java:136)? at android.app.ActivityThread.main(ActivityThread.java:5584)? at java.lang.reflect.Method.invokeNative(Native Method)? at java.lang.reflect.Method.invoke(Method.java:515)? at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1268)? at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1084)? at dalvik.system.NativeStart.main(Native Method)?

仅当我将开发人员调试选项设置为请勿继续进行活动" 时,才会发生崩溃.如果关闭此选项,则不会发生崩溃.

The crash only happens if I set the developer debug option "do not keep activities" on. The crash does not happen if this option is off.

崩溃发生在不使用Proguard的调试模式下.

The crashes happens in debug mode where no Proguard is used.

我在活动之间不传递任何包裹/捆绑包,也不使用startActivityForResult().

I do not pass any parcels/bundles between the activities, and do not use startActivityForResult().

在Lollipop之前和之后的设备上都发生崩溃.

Crash happens on both pre and post Lollipop devices.

我发现了两个类似的帖子此处可能(或可能不)相关.

I found two similar posts here and here which might (or might not) be related.

推荐答案

将SearchView与ID资源一起使用时的解组异常 appcompat 23.2

Unmarshalling exception when using SearchView with an id resource in appcompat 23.2

它可以通过工具onSavedInstanceonRestore进行修复,但不要使用super.这种奇怪的行为

Hi, it can fix by implement onSavedInstance and onRestore but don't use super. This strange behavior

@Override
    protected void onSaveInstanceState(Bundle outState) {
     }

    @Override
    protected void onRestoreInstanceState(Bundle savedInstanceState) {

    }

这篇关于升级到支持库后,在偏移4752处解组未知类型代码6839391的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆