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
When I try to upload my Android App Bundle to the Google Play Console, I get this generic error message saying "Couldn't upload. Try again.".
I've already tried:
making sure my versionName and versionCode are unique among all uploaded artifacts
making sure that the .aab/.apk is signed with the proper key
re-uploading the .AAB file
re-uploading the .APK file
checking status of google services to make sure that there isn't a mass outage
asking my senior Android dev what's up
How do I resolve this error and upload my .AAB or .APK?
Google Chrome
Use a new Incognito window to upload the .aab or .apk (as mentioned in the comments).
Alternatively, clear the website data:
going to: developer console (F12) > Application > Storage > Clear site data
Screenshot
press F5 to refresh the page
uploading the .apk/.aab again
Safari
Open Preferences >
Privacy > Manage Website Data > Remove All > Done
Here's what worked for me:
After getting the error on play console. Now use 'Add from Library' option instead of 'Upload', and you will find your appbundle that failed to upload there, select it and proceed with further steps.
This problem comes out due to multiple gmail logins on same browser, if the developer account is not the default logged in account. You can solve this by signing out all gmail accounts and login in the specific gmail account.
For my case clearing data, using Incognito or changing browser did not work. So, finally I uploaded an APK file (all previous versions were AAB files) and surprisingly Google Play console accepted it!
Give a chance to APK file if the above answers are not helping you.
Do you have gmail with another account, opened in other tab? If so, sign out from both accounts, then sign in to Google Play console again.
I could simply solve the problem by usinng Firefox instead of Chrome. Nothing else helped. With Chrome the problem remained even after applying all the suggestions above. Chrome 56, OS Ubuntu 16.04
If your zip align is not successful or verification failed at the end of the zip align process, this error is likely to occur. Please analyze whether zip align was successful. Also, you can try uploading both in .apk and .aab format. You are more likely to get a more detailed error hinting a possible cause.
If you're using Unity
I was trying to upload a Unity project. Clearing browser cache, loging out of accounts, trying different browsers, zip align etc. didn't help for me. What did, was to either:
a. Upload an .apk instead of an app bundle.
For some reason, this works completely fine, but app bundles fail every time.
Sadly, apks be unavailable for new apps starting from August 2021 :(
b. Upgrade to a newer version of Unity
Versions that did not work:
2019.4.20
Versions that worked:
2020.3.3
Play Console's error message is not especially helpful, so it's difficult to say exactly what the problem was or what fixed it, but hopefully this will help someone else using Unity.
I haven't tested any Unity versions except those listed above. If you have and also have the necessary stackoverflow rights, feel free to update my list with your own findings.
On Safari:
Preferences -> Privacy -> Manage Website Data -> Google (remove that) did it for me! ;-)
After that error happened to me, I click "Add From Library" and my uploaded app bundle showed up there, and am able to select it.
No need to logout/login or clear the cache/cookies.
After All of trying above, I have just Change the browser from Chrome To "Opera" - and its uploaded very fast. It seems that opera is very fast than chrome.
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.
We are building an update Android apk using Corona SDK - with the Target App Store set to "Samsung".
We are definitely using the same keystore file that we used to sign the original build. I've used it plenty of times, and it's the only one I have for this app so it's definitely the right one. When uploading updates to Google Play it has worked fine, it's just not working on the Samsung store for some reason
We keep getting this error message:
"The signing key is invalid. Please check the signing key of the binary"
I can only presume this refers to the keystore used to sign the application, searching for the problem didn't turn up much, other that someone who had asked the same question on the samsung forums and never got a reply.
Is there something else we could have missed?
It turned out that the error was not at our end, it was being caused be a fault on the store itself.
We had to delete the app and upload it again as a new application, at Samsung's suggestion.
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).