Hello everyone! I wanted to ask if someone can give me a link to read or an answer here that clarifies what would be the best option between .abb or .apk to submit to Google Play. Taking into account that it is tempting to sign the application directly with google in case any cloud or backup disk fails and all data is lost.
Thanks in advance
DoDi
.aab is the way to go if you keep in mind that our support for .aab files is fairly new. I think there were a few early reports about issues with .aab files and some people are sticking with .apk files for now, but for others they are working just fine.
We originally discouraged people from using Google App signing because frankly we knew little about it and giving up control over that process was hard, but in testing .aab files, I’ve gone through the process and it’s not that painful. They have a really good walk-through to get your keystore processed correctly.
.aab files will get rid of the “This app isn’t optimized” warning. They produce overall smaller files than a .apk with both 64-bit and 32-bit support in them.
Rob
once the .apk is up I have the option to change it to .abb?
Sorry if I ask too many questions, the process is new to me.
DoDi
@DoDi, I believe you would have to build a new version with a higher Version Code and then you can upload the .aab file. However, if you have a .aab file uploaded, I’m not 100% sure if you can go back to an .apk, but I think you can.
Rob