I just published a new app to the Google Play. The problem is that I can't install it in any device because whenever I try to download it, I receive a "Package file is invalid" error.
I tried to clean the Google Play cache and data but it didn't work. I also tried to download it in several different devices and wifi networks. Still I get the error.
I was wondering what could be possible reasons for this error.
When I opened the logcat after trying to download the app from Google Play, I see the following error:
Signature check failed, aboring installation.
What could be causing this? Do I have to use a License Key within my app? Because I didn't do that. I just followed the signing tutorial and used the Android Studio to generate the signed APK.
The Google Play web servers are serving corrupted package files for lots of apps, this weekend. (Lots of people on Twitter are grumbling about it.) While many different error conditions can lead to the "Package file is invalid" and "Signature check failed" error messages, your issue is almost certainly this problem at Google that they'll (hopefully) fix in the next day or two.
I did some investigation into this issue, and found that the corruption was present in the data stream when packet sniffing at my router, before it even reached my devices.
Related
I'm trying to upload an apk for distribution on firebase but I get this error instead:
"There's been an error processing your distribution. Ensure you're uploading a valid IPA or APK and try again. Additional information about this error: Invalid APK file."
I'm indeed trying to upload an apk (which by the way, works fine on device). I thought the issue could be related to the android keystore, but that seems okay too. Can't find much more info on this online. Any suggestions?
There could be various reasons for this type of issue and you can try the below methods to solve the problem.
Try to upload apk via a google chrome OR any other browser. Reason for saying this is sometime problem is your session invalid. Using any different browser such as firefox,IE etc. would create new session and allow to upload apk.
Sometimes it happens due to low internet speed speed but it's rare.
It could be happened with the application icon. You must need to be set in the AndroidManifest.xml file
You can contact to firebase support team if above doesn't work. Link
Suddenly from 3 days, I am not able to use Google Internal App sharing. Loading App sharing page fails with error "unexpected error". Is there anyone else who faced this issue? and have some workaround?
Note:
I am aware that I should raise this issue in Google support, but they are taking too much time to respond. Meanwhile, I am just searching for workarounds or possible reasons for it.
I have tried all possible solutions which are already there on the Web, like incognito mode, clearing cache, etc.
In my network those who already have play store accounts are also getting the same issue.
The API gateway still seems to work. I was able to upload a test apk/aab via fastlane.
It's an easy setup. Then use the upload_to_play_store_internal_app_sharing command to upload the apk/aab
Question :
We have posted one app for Hong Kong Market and when users try to download the app it always gives an error named as "Package file is invalid". So for testing we did enable the app for India but here we are getting the same error. Please help us out
"Replay from Google support"
Thank you for your patience while we've investigated this issue.
It appears that installations are failing due to your app's incompatibility with some devices that are running Gingerbread or Froyo. This issue has been discussed at length in multiple developer forums. To find out how to make your app work better with older devices with smaller buffers, please check developer discussions by searching 'dexopt failed gingerbread froyo' on forums listed at http://developer.android.com/support.html. Here you can find links to developer support forums and IRC chat communities where developers help each other solve development-related issues.
Unfortunately our team does not have the capacity to offer development advice on per-app basis. However, if you find that installs are still failing on Gingerbread or Froyo after implementing the changes we mentioned, please let us know, and we'll investigate further.
Thank you for your understanding. If you have any further questions, please let us know.
Send one more reply on same but not get anything right now
Question :
I am still getting an error after downloading the application from play store. I have also checked with manifest file here is my SDK setting.
android:minSdkVersion="11"
android:targetSdkVersion="18"
It's downloaded successfully from there but at the time of installing the app we getting again the same error " Package file is invalid ".
This is happened first time but when I try second time to install on same device at that time we are getting different error "Unknown error code during application install -24".
You will need to clear your Google Play's data and cache. To do this:
Go your device's Settings menu.
Go to Applications (may also be labeled Application Manager).
Tab over to All Applications.
Open the Google Play Store app.
Tap on Clear Data and Clear Cache.
Relaunch Google Play and install or update the our app again.
Reference Link
I have attempted to upload an app via the Google Play Developer Console for the last two days, but the apk uploads until "99% complete" in firefox or until "processing" in chrome and the is stuck.
This is not my first app. I have uploaded and published two others without incident.
I have attempted the upload with following with all the same result:
*Firefox 28.0 (Ubuntu 13.10)
*Firefox 28.0 Incognito (Ubuntu 13.10)
*Chromium Version 33.0.1750.152 (Ubuntu 13.10)
*Chromium Version 33.0.1750.152 (Ubuntu 13.10) Incognito
*Chrome mobile 33.0.1750.166 on Galaxy Nexus Android 4.2.1 phone
*Chrome (Windows 8)
Logs start out fine:
POST https://play.google.com/apps/publish/upload [HTTP/1.1 200 OK 537ms] POST https://clients2.google.com/uploadstats [HTTP/1.1 200 OK 1402ms] POST https://clients2.google.com/uploadstats [HTTP/1.1 200 OK 1457ms] POST https://play.google.com/apps/publish/upload
then it hits 99% complete and these errors start posting:
POST https://play.google.com/apps/publish/upload [HTTP/1.1 503 Service Unavailable 3816ms] POST https://play.google.com/apps/publish/upload [HTTP/1.1 503 Service Unavailable 739ms] POST https://play.google.com/apps/publish/upload [HTTP/1.1 503 Service Unavailable 668ms] POST https://play.google.com/apps/publish/upload
I also tried advancing the version in the AndroidManifest.xml.
As a test I added the apk in question to the Amazon Appstore. No difficulties. The apk uploaded seamlessly. Google Play Store issue?
Also tried adding a new application in the developer console and then uploading the apk.
Also tried starting from scratch and rebuilding the app in Eclipse and then attempted to upload the new apk. No luck
I have been emailing with Google Help. 8 days ago they asked for the apk in question and HAR file generated when the upload gets stuck. I sent both. They replied they were looking into the issue. A few days later this question came alive with others experiencing the same issues! I emailed again that I was still encountering issues.
Then on March 19th they responded and asked for:
A screenshot of the error message.
The APK you're attempting to upload
The browser versions you were able to test with and OS type that you are using.
Information from the browser's error console or http logs.
What steps did you take to reproduce this issue?
Any other suggestions?
There is a bug in Android that affects every version of it. A developer found out about it yesterday. By malforming an apk file you can corrupt system memory and systems freezes completely. He then uploaded this malformed apk to Goople Play from different countries causing Google Play Developer Console to freeze all over the world! It was fixed for about an hour but then the developer reuploaded the apk and Google Play is down again. I think it will be fixed soon, but anyway it can lead to huge financial damages to many companies around the world.
http://ibrahimbalic.com/2014/android-os-memory-corruption-bug/
So the answer is we just have to wait...
It's a temporary problem, common to many users, due to google developer console website problem.
After tring many times at different hours you will finally upload your app.
This is my experience.
Here the link to the problem report: https://code.google.com/p/android/issues/detail?id=67226
Here the link to report the problem directly to Google requesting support: https://support.google.com/googleplay/android-developer/contact/publishing?extra.IssueType=submitting
It was a problem on Google's end, and they were aware of it; there was a message on their support site (which now appears to have been taken down) and in the Developer Console alerts:
Errors uploading to the Google Play Developer Console:
We're currently aware of an issue impacting some developers attempting
to upload APKs or Images to the Google Play Developer Console. We're
working hard on a fix, and will provide an update once the issue is
resolved.
Google states it now appears to be fixed:
UPDATE - 2014.03.17 4:00PM PT:
This issue is now resolved. Please contact us if you see any issues
uploading APKs or Images.
I have been able to publish APKs and also received numerous app updates since this message was posted, so it does appear that this specific problem appears to be resolved now.
My specific issue was identified by the Google Support team:
Our specialists have found that the APK was getting stuck during the
step where we verify the icon and the certificates.
Comparing the aapt dump to your app's manifest, there are some
inconsistencies with the icon location. You would want to start
troubleshooting there. If after fixing the icon you still encounter
upload issues, double check your certificates and your signing
procedure.
The issue was entirely mine as a new and inexperienced developer.
Upon replacing the icon and redoing the key in Eclipse, the .apk in question uploaded without incident and is now published.
The Google Team also made the following suggestion for those searching for help:
For more information on running aapt, please see the “Testing the features required by your application” section of the following article: http://developer.android.com/guide/topics/manifest/uses-feature-element.html.
I have a draft apk, unpublished, up on the android market store and I've recently made a some fixes and minor enhancements. Every time, I try to 'replace' the current version, I get a terse message of "The server could not process your apk. Try again." towards the very end of download process.
At first, I thought it might be flaky internet connections or such. But now, I'm suspecting it may be something is wrong in my apk file.
I have the exact same manifest file, used the same build and sign process. File is just under 6MBs. I've tried doing this using both chrome and firefox.
Suggestions?
I had the same problem last week. Just waited a few hours, and tried again.
It seems replacing an unpublished apk is still broken. Removing and then uploading the apk works, but in the process it also removes in-app products associated with the application and you have to create them all over again each time. Not cool when you're doing all this to understand and test in-app billing (and you don't want to trust Google's in-app billing documentation as far as I know).