On 07/04/2013 03:50 PM, Brian Conrad wrote:
Yesterday I uploaded an update to an app. Today I get a couple
reports of crashes. One provided the stack trace and that crash is
possible only if they got a truncated download. I don't know if any of
you have perused an apk but the executable and resources are at the
end. I've seen crash reports before from users who provided the stack
trace that indicated that the app couldn't find a resource or in one
case the Google Maps library dex. File integrity checks have been
around since x-modem but there appears to be no such thing when
downloading with Play.
And often after suggesting uninstalling and reinstalling the app
worked for those who had the crash. Today I suggested two reports
that they do that but it is still crashing. Here's another thing: we
can't download our own apks to do a bit check even length check on the
download. I can understand why they maybe won't do that but they
could provide 1) the full byte count of the upload and 2) MD5 and SHA1
checksums to see if they match the files we upload. That should be
easy to provide. With only two reports I don't yet want to revert the
apk in question as it might just be a quirk of their devices (as if
devices don't have quirks nowadays). And these reports are from India
which has crappy telecom data support.
Anyway I've posted a feedback on this to Play and providing this here
because if you notice they now say to post Play problems on this group.
- Brian
Just a follow-up after researching the APK structure which is of course
a ZIP file and doing some tests, a truncated and corrupted APK will not
even install. Truncated it throws an EOCD error and corrupted (only two
bytes changed) also throws an install error since there is a CRC
checksum in the file. Obviously an APK does need to load properly for
the console to get all the manifest information.
The problem seems to come from a couple users with the Samsung Galaxy II
7" tablet with a 600x1024 display. However an emulator configured that
way runs the app okay. These people probably have a virus or a device
malfunction. Some users with similar crashes on prior versions found
that the app ran fine after they did a factory reset so something else
was indeed causing a problem.
- Brian
--
You received this message because you are subscribed to the Google Groups "Android
Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/android-discuss.
For more options, visit https://groups.google.com/groups/opt_out.
