I get some wierd ACRA reports every now and then. For example, I get a layout inflater exception for the very first field in the first layout file being rendered. It complains of a missing layout_width or layout_height attribute. They can't possibly be missing but I can't explain it other than to say it was a corrupted download or install. Each user I ask to simply uninstall and reinstall and they tell me that fixed it.
Yes, I would have thought the Market did some kind of sha/crc check, but the errors I'm getting show it's either not foolproof or not always working. Of course, it could be that the download was perfectly fine, but when the resources were extracted from the apk, at that point there was a blip somewhere and something wasn't extracted or written correctly..? HTH On Dec 3, 9:38 pm, strazzere <[email protected]> wrote: > I don't know? But I can assure you the market check after download and > after install. Possibly something after that. > > Is there any pattern in the bug reports? Same device, same rom, etc? > > I'm sure _something_ is wrong, I'm not doubting you on that. Just > saying your gripe about the market not checking apks is probably not > right :) > > Tim > > On Dec 2, 3:52 pm, Brian Conrad <[email protected]> wrote: > > > > > > > > > Then why would a few of my users get versions that are corrupted and > > downloading again solves the problem? > > > On 12/02/2011 02:26 PM, strazzere wrote: > > > > Unsure what your problem actually is, but I can assure you that the > > > Market does actually do this. > > > > Upon download request the give the Market an sha of the application -- > > > once done download it will check this. If this succeeds it will pass > > > the apk on to the package manager, which will then verify the > > > signature of the apk also :) > > > > Tim > > > > On Dec 2, 1:05 pm, Brian Conrad<[email protected]> wrote: > > >> Apparently the Market app does NO error checking for downloads. Once > > >> again I had a user complaining my app wasn't working correctly. I > > >> suggested he uninstall/reinstall and as a last resort he did so and that > > >> solved the problem. Apparently though the app was corrupted during > > >> download it still ran. I had another case where the custom font wasn't > > >> displaying and the uninstall/reinstall solved that for the user. How > > >> many of you are wasting time chasing down bugs which are really nothing > > >> more than a corrupted download? Seems to me when a user downloads they > > >> could first send the MD5sum then after the download see if it matches > > >> before installation. -- You received this message because you are subscribed to the Google Groups "Android Discuss" 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-discuss?hl=en.
