Lots of users are getting Package File Invalid Error (Google Play)

Solar2D Android
#1

We recently did an updated release to our Android app, and all of a sudden we are getting tons of user complaints about Package File is Invalid Error. And the error has tanked our download number!

All the information we found online talks about it as a Google problem. Has anyone else seen this?

http://www.androidpolice.com/2013/08/13/play-store-team-acknowledges-pervasive-package-file-invalid-error-when-installing-or-updating-apps-no-fix-yet/

http://gizmostorm.com/how-to-fix-package-file-is-invalid-error-on-google-play-store/

That said, we also have 2 other theories for contributing factors:

  • This new apk is 1.5 MB bigger than our last one, and pushed our app size to a tag over 30MB, which some online posts  seem to indicate can cause problems with downloads on some devices?

  • We also keep wondering if it had to do with the Corona build we are using 2013.1181, which is about 1.3MB bigger than our previous build, so clearly there are some new added libraries.

Is anyone else seeing this? Is there anything we can do on our end to fix this? It is hitting us really hard!

#2

https://support.google.com/googleplay/answer/3300875

There is not work around at this time.

#3

@dchan Thanks for the link. I came across that post as well after my post above… Really hope they get on top of this asap!!

#4

So things got so bad yesterday that we went ahead and 1) compacted down more of our image assets, and 2) tried rebuilding with Corona build#2013.1137. And amazingly, the problem went away!

So, clearly what we do can trigger the issue on Google’s end. What’s not clear to me though, is whether the trigger is something in build 2013.1181, or is it the size of the app (which went down to roughly 28MB).

If anyone else is having similar issues, please share!

#5

Just to follow up. It looks like Google fixed the issue.

http://www.engadget.com/2013/08/13/google-play-package-file-invalid-error-acknowledged/

We haven’t gone back to try it. But we’ll let folks know if we run into this issue again when we do future releases.

#6

https://support.google.com/googleplay/answer/3300875

There is not work around at this time.

#7

@dchan Thanks for the link. I came across that post as well after my post above… Really hope they get on top of this asap!!

#8

So things got so bad yesterday that we went ahead and 1) compacted down more of our image assets, and 2) tried rebuilding with Corona build#2013.1137. And amazingly, the problem went away!

So, clearly what we do can trigger the issue on Google’s end. What’s not clear to me though, is whether the trigger is something in build 2013.1181, or is it the size of the app (which went down to roughly 28MB).

If anyone else is having similar issues, please share!

#9

Just to follow up. It looks like Google fixed the issue.

http://www.engadget.com/2013/08/13/google-play-package-file-invalid-error-acknowledged/

We haven’t gone back to try it. But we’ll let folks know if we run into this issue again when we do future releases.