I have built a app in android studio and would now like to publish it however I am very confused with the process for this. From Android studio I have generated a signed APK file which can be seen in the image below.
I see however that Google play console wants the files in the .AAB file type. How do I generate this/ what is it. The upload console can be seen below.
This is my first app upload so my questions may make no sense, please let me know in the comments below if there is anything I need to change or additional information required.
Any additional help with publishing apps on google play store will be greatly appreciated.
.AAB refers to "Android App Bundle", select Android App Bundle instead of APK after you clicked Generated Signed Bundle / APK, the rest of the procedure is more or less the same. You may refer to the official documentation for more information
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.
There are lot of online gotchas and SO questions on this topic and I pretty much read through lots of them, but this error still persists.
What have I done so far:
Created both debug and release signing config
Created Web and 2x Android credentials in Google Developer console
Ensured that Android credentials in GDC have appropriate SHA-1 hashes and correct package name
SDK uses ClientID of Web credentials
The app is still in development phase and hasn't been published to Play Store. Few days ago, we changed both package name and and ApplicationID. I made sure that have package name change mirrored to my credentials in GDC.
I am positive that login was ok until few days ago (possible linked to package name change).
Can you please suggest any other troubleshooting steps?
I solved the issue couple of days ago and I would like to offer a retrospective to anyone else who might stumble upon this.
Disclaimer: If I had read the docs more carefully, I would have spotted the issue.
What I knew:
Both Facebook and Google sign-in worked from emulator
Both worked when I launched app on a device via USB
Both worked when I deployed locally build APK to a phone
Still, none worked when app was downloaded by Internal tester group from Play store.
I tried generating hash via keytool both for my release and debug key, but that did not seem to click.
Finally, after days of debugging, I have found what was wrong: Forget about your local (debug/release) keys and use the one that Play Store provided. You will find this one in Release Management section.
For Google sign-in:
In your Google Developer Console, create a new credential where you will input a SHA-1 from Play Store
For Facebook sign-in:
Get the SHA-1 and convert it to Base64. I used this tool: http://tomeko.net/online_tools/hex_to_base64.php. Then, input the base64 payload into your Facebook application.
Hope someone will find this at least a bit useful.
I am doing some modification in an existing apk that i got from my client to modify. I have decompiled application using apktool, changed some resources (like some strings from strings.xml) and recompiled/built it again using same tool. Then I signed using one_click_signer tool that I found somewhere of the google.
But when I install it on my device then google maps does not work anymore as it was working with original apk on the same device.
I have searched a lot about this but did not got any solution.
I reviewed this link and many more and come to conclusion that I need to sign the apk with same key that was in original apk.
So can anyone please tell me:
how can I sign the apk again with the same key and make map work?
or is there any other way to make maps work properly?
Solution That I found and worked for me:
Thanx for
#apmartin1991's answer . .
I created a google api console project and got got the generated key.
then I replaced that key in android-manifest.xml file and resigned the application.
It worked.
You will need to contact your client to get the .keystore file so you can sign it with the same key OR you can sign it with your own key and allow your key to be used with google maps, You can do this from the Google API console.
However if your clients app is on the appstore and you want to update that you MUST use the same key or it will be impossible to update it.
You need .keystore file to use the same key. If you dont have .keystore file you need to generate a new one and register a new key in google maps console.
You have all the official instructions here.
we are trying to use google play's apk expansion file since our package is too big. After following the instruction in http://developer.android.com/guide/google/play/expansion-files.html and follow some posts in stackoverflow. we managed to have our code running.
But unfortunately, we are keep getting STATE_FAILED_FETCHING_URL. is there anything wrong? should we set anything before we start?
we have already put the apk and expansion file through the developer console.
any suggestion? thanks a lot.
[UPDATE]
I found the reason is because I haven't added the google account to test account, and not working with the apk signed with the same keystore as I uploaded to publish account. But after I succeeded once, it is ok to work with the apk signed by default debug keystore in eclipse. Besides, I forgot to click the Activate link to make my draft become active.