I just got killed by a corrupt APK when I deployed to production. It took me three versions to get the APK build to build one that was not corrupt (I had to completely remove the project from the disk and recheck it out and rebuild it).
What made matters worse is that it now takes Google hours to deploy, so even when I discovered a corrupt build people would be downloading the bad version for hours while the new version made it way through the system. In this case, it made really pissed off consumers because it was a keyboard that suddenly stopped working and they couldn't even switch to the default keyboard without getting an FC. The crazy thing was that I didn't change the code at all between the three deployments (except to verify that the error was bogus), so I know it was a corrupt APK. Has anyone else experienced this kind of issue, and am I going to be dealing with it regularly now? -- 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 --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
