I have at least 75 users with this problem, and I have a factory reset G1 that also gets this problem. After download and during the install process the installer reports "Package file is invalid". I can't install from web since chrome doesn't support it and the most updated factory web does not either.
This began after we migrated to using Android Studio (likely not to blame, but a lot of packages changed using Gradle so its like finding a needle in a haystack.) We made this move to support multi-dexing since it was the only way to update our Google Play NDK SDKs to the latest to try and solve a crashing problem calling IsAuthorized on the Play Games SDK. This has been going on for months 1,000s crashes a week, but I digress. These attempts to modernize our build and update SDKs has led us into a corner with regards to targeting as far back as API level 10. And before anyone says "just ditch it" stop. We aren't gonna ditch a 5%+ of our users over this (yet). Much of our long lived popularity is due to backwards support of older hardware. It's like free advertising. So we value it dearly. Back on point. I suspect some jar/package got used that has a feature that 2.3 does not support anymore and on install something is being detected. I want to know how to find that library so I can determine if I can live without it or not and kick hundreds of users to the curb. We want to support 2.3 but something in the APK wont let it be installed. I am really hoping there is a tool, or something someone can run to find the offending bits and who's bits they are. Something in the APK is causing the install to fail. I have a sneaky suspicion that is the case anyway. I'd like to get to the bottom of it once and for all and make a decision without spending any more time tearing out SDK's with live and breath on to figure out which one(s) is to blame. Anyway, I am looking forward to hearing thoughts on this. So far nothing short of a complete tear down and isolation of code has worked. I saved the hardest/most lame brute force strategy for last... I see this has plagued lots of big apps Twitter, WhatsApp, Facebook... I've reached out to their support teams for help. This is not a bandwidth issue, its not a cache clearing issue (this has never helped a single one of my 2.3 customers and I stopped having them try factory resets after the 10th, that was an epic waste of everyones time.) Thanks for hearing my rant! ;) -- 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]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/android-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/android-developers/db2a9c74-cb6b-48f7-b5a7-348ba8112839%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
