Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I wonder if it will work… In my app I have an object that I’m serializing to file, and then I obfuscate the code with the ProGuard and application goes to Market. Then I want to release new version of app. I do the same. The users run through the application update.
The question is – does the object, that was serialized with the first version of app, deserialize properly in the second one? And if yes – why?
I could find several mechanisms (serialPersistentFields, ObjectInputStream#readFields) that make it possible for customised serialisation to be dependent on field names – assuming the default mechanism isn’t already. The ProGuard documentation has some example configuration that shows how to make ProGuard ignore field names and all special methods and fields used by serialisation.