I am new to publishing to google play, but everywhere I looked says that you just click build then upload the apk file you get to google play. But the file I am receiving is an .aab file with no APK file to be found. I messed with my settings but cannot figure out why this is happening.
Thing I have tried:
1. Updating Unity
2. Change keystore file
I am not too familiar with unity, so I don't want to mess with too many settings with the risk of messing up the application further
when you generate Signed Bundle or APK for release, if you select Android App Bundle you can get .aab (bundle file).
if you want to get .APK you have to select APK.
in this screen.
Related
Hello All,
I have gone through the android blog and found that there is two ways for creating the APK file in android:
1. Android App Bundle (.aab)
2. Signed Apk (.apk).
I have gone through the details and found that the size of both the files are different the .aab file size is low compare to .apk file.
Now my question is that my app is live and I use to upload the .apk file for the new update, So can I upload the .aab file this time as new update.
will it work?
Yes, it will work with .aab file.
When I am publishing .aab (Android App Bundle) extension file in google play console then it showing me error i.e. Upload failed
Your Android App Bundle is signed with the wrong key. Ensure that your app bundle is signed with the correct signing key and try again
I search regarding this topic solution and I get also bt didnt work for me. like : 1. clean, rebuild and again generate signed bundle.
2. change the location for generate signed bundle.
3. delete the generated file when created at the generate signed bundle time.
and many more. But didnt work anything.
I've developed an application in Android Studio and now I'd like to generate the apk.
I followed some tutorials where I went in Build -> Generate Single Budle ... and a ".jks" file is generated.
Is this file that I should copy to my mobile phone? If so, how?(a message appears saying that the file is not supported).
Everything is very simple.
Build -> Generate Signed Bundle / APK -> Set APK
Use your key or create new *this key is your digital signage
After Successful build you can find your APK file inside the project folder itself.
(path: project_folder/app/release/apk-release.apk)
Put attention to digital signature! If you are publishing your APP in Google Play store, then you should keep that file safely. If you lose your key,then you can't submit any updates to your App. Even nunky from Google can't to do anything. Keep it in a safe place.
I generated a signed APK file with Android Studio and I analyzed it to check if Proguard works correctly (and it works). I would like to upload to the Play Store a bundle file. If I click on Build, Generate Signed Bundle/APK and I select "Android App Bundle" instead of Apk, should Proguard work automatically or are there any rules that I have to change?
It should work automatically without changing anything. The same dex file is generated for APKs and for Android App Bundles.
i want to upload my app in google play market, but i am confused,
which .apk file should i use to upload, 1) Build-->signed apk-- ........
and 2)select projects from to left corner in android studio-->app-->outputs--> .apk file
One more thing , when i am creating signed .apk from build menu-> signed apk
after filling all the details...
android studio... shows an error....it does not recognize raw folder and its audio file
what i do , to remove this error
please suggest me.........
You should choose former, the signed .apk to upload to Google, the other one is for the debugging purposes.
here, this one. -> http://i.imgur.com/c18ps4Y.png
Also, I would suggest you to clean, rebuild project once before generating signed .apk, although its done on build.
Also, kindly provide the exact error you are getting while building the signed apk.