1
I developed an app 2 years ago and we have updated at Google Play always signing with a jks certificate and encrypting with Proguard. This application has been updated in some versions.
Even nay using "smart updates" that Android allows, in certain situations and some devices, the application is "pseudo-updated" on the user’s phone.
I made a publication of tests removing Proguard and this problem did not occur. But it’s rare to occur and I’m having trouble reproducing this defect to try to cause the problem more often.
I read about the delta algorithm to reduce unnecessary download on smartUpdates but does not mention anything related to Proguard precisely because it "shuffles" and the block difference comparison gets stuck, published here http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=6563072.
But it did not help effectively to solve the problem, the article only explains "how" smart updates are performed. Even disabled, I’m having some problems.
Unfortunately it is difficult to detect if it is really the user’s device problem, because other cases happened. If it is the Google Play version of the user’s device, if it is Proguard etc. A difficult defect to play.
Someone has been through a similar situation and knows a solution?
A hug to all!