Yes, it's pretty hard to reproduce this locally. Typical scenario will be opening the activity, Home press, killing the app process, restoring the activity via long Home press. I guess for users this happens also if android kills process for memory or by other reason.
Adding android.view.View$BaseSavedState derived classes to the list of proguard exceptions resolved it completely (never seen it in the crash dumps from users since then). On Nov 11, 4:11 am, Zsolt Vasvari <[email protected]> wrote: > Ok thanks. But why does this seem to happen infrequently? > > I cannot duplicate it at all when running the same obfuscated app on > my Nexus One phone. > > On Nov 10, 4:02 pm, maxmpz <[email protected]> wrote: > > > > > > > > > This one can be caused by obfuscating the CREATOR field used for > > saving/loading widget state. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en

