ClassNotFoundException when unmarshalling SavedState [37133281]

Infeasible

Bug

[AOSP] assigned

NeedsInfo

Status Update

No update yet.

Description

wo...@gmail.com

created issue #1

Jan 18, 2017 06:32PM

This ticket is a duplicate (sorry for doing this on purpose) of

https://code.google.com/p/android/issues/detail?id=196430.

The referenced issue is closed because the bug was fixed in an older release. However the bug reappears in the support library 25.x again and there are a lot of comments that are asking for opening the ticket.

But apparently no maintainer is reading closed tickets so I'm opening this to pull the attention there.

Comments

ar...@google.com <ar...@google.com> #2Jan 19, 2017 08:51AM

Assigned to ar...@google.com.

I should add, I never explicitly set setReorderingAllowed to true. The documentation states

The default is false for applications targeting version versions prior to O and true for applications targeting O and later.

I'm not sure how pertinent this is with the support library fragments.Compile SDK and Target SDK versions are both 27.

wo...@gmail.com <wo...@gmail.com> #3Jan 19, 2017 08:54AM

I can confirm that 27.1.0 has this bug. Downgrading to 27.0.2 worked for us (we came from 27.0.2).
It seems to be related to the fade transition, since setting the transition through the setTransition method of the FragmentTransaction results in the same behaviour.

ar...@google.com <ar...@google.com> #4Jan 31, 2017 06:43AM

I can confirm this too for 27.1.0. Any workaround for this?

ar...@google.com <ar...@google.com> #5Feb 6, 2017 10:40AM

Seeing the same issue here with '.setTransition(FragmentTransaction.TRANSIT_FRAGMENT_FADE)' on Google Pixel 8.1.0. Attached a video comparing before and after.

My current workaround is to use a different transition such as TRANSIT_FRAGMENT_OPEN. It looks similar enough for me.

ha...@gmail.com <ha...@gmail.com> #6Feb 6, 2017 02:29PM

I also confirm this. Helps only return on 27.0.2

ar...@gmail.com <ar...@gmail.com> #7Feb 6, 2017 04:28PM

I can confirm this bug. Reverting to 27.0.2 helped.

kv...@gmail.com <kv...@gmail.com> #8Feb 7, 2017 03:31PM

same here. reverte is the only workaround atm

deleted

Restricted

0 B

ha...@gmail.com <ha...@gmail.com> #9Feb 7, 2017 03:41PM

I have the same issue. I had enter animation as fade_in and exit animation as fade_out. For me temporary solution is change exit animation to 0, transaction now looks almost the same as with fade_out exit animation

[Deleted User] <[Deleted User]> #10Feb 7, 2017 03:51PM

Thank you for reporting this bug. I am able to reproduce it. It was caused when fixing another bug and this error wasn't caught during testing.

ar...@google.com <ar...@google.com> #11Feb 8, 2017 10:47AM

Same issue. I had to roll back version to fix it

ch...@beyls.net <ch...@beyls.net> #12Feb 21, 2017 06:32PM

Fix has been submitted and should be in the next public release.

ch...@beyls.net <ch...@beyls.net> #13Feb 21, 2017 06:39PM

This bug has been fixed in Support Library 27.1.1.

[Deleted User] <[Deleted User]> #14Mar 16, 2017 04:28PM

In the app that I am working on, this issue only occurs when pressing back (unwinding the transaction). The problem is still reproducible in 27.1.1. Does 27.1.1 fix the problem for others?

ch...@beyls.net <ch...@beyls.net> #15Mar 17, 2017 07:09PM

I submitted a pull request to fix this issue one month ago, but still no reaction from Google:

https://github.com/material-components/material-components-android/pull/31

ar...@google.com <ar...@google.com> #16Jun 13, 2017 04:51AM

Can you please provide a reproduction usecase without the app's(application given in

comment #6

) additional layers of abstraction responsible for parceling state.

ar...@google.com <ar...@google.com> #17Jun 19, 2017 06:30AM

Can you please provide the information requested in

comment #16

to investigate further.

ch...@beyls.net <ch...@beyls.net> #18Jun 20, 2017 03:02PM

I created a minimal sample project as reproduction usecase:

https://github.com/cbeyls/CoordinatorLayoutStateRestoration
I also provided the fix as pull request and a workaround class for developers, I don't think I can do more than that.

ch...@google.com <ch...@google.com> #19Jun 28, 2017 09:29AM

Note that we're dropping support for <v14 in 26.0.0 so unlikely to release a fix.

Thanks for the investigation though Christophe

ch...@beyls.net <ch...@beyls.net> #20Jun 28, 2017 11:08AM

I was hoping for a final 25.x bugfix release for older devices before their support is dropped. CoordinatorLayout never worked properly on API <13 devices since it was introduced in 2015.

ar...@google.com <ar...@google.com> #21Jul 12, 2017 05:02AM

Status: Won't Fix (Infeasible)

We no longer target support library for devices less than API 14. Since this bug is only reproducible for those devices, there is nothing we can do about it.
If you can create a minimal project that reproduces it on devices with API 14 and above, we can reopen the bug and fix it.