To Bundle or .apk? Android app

LMiles 21 Reputation points
2020-12-03T14:29:57.057+00:00

Hello,

I'm going through the throws of releasing first build to the Google Play Store.

Up to now I've always built to .apk and deployed to test devices. The .apk is signed with my own .snk and .keystore
The app is also obfuscated. All runs on multiple android devices, no issues.

Google also have the "Bundle" option where they handle .apk signing etc. They also claim it is the better option.

QUESTION: Is it better to use the Bundle option and leave signing to the Google Play or to submit an .apk with the relevant .snk and keystore files?
I've not tried, so I assume that is what will be needed, albeit the apk is already signed in local build.

QUESTION: If I chose to submit a "Bundle", does anyone know how that may be affected by the prior obfuscation of the assemblies?

What else is there to consider in relation to this?

Thanks

Developer technologies | .NET | Xamarin

Locked Question. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

{count} votes

2 answers

Sort by: Most helpful
  1. Graham McKechnie 446 Reputation points
    2023-08-13T00:39:55.59+00:00

    You don't have a choice on Google Play, you must upload a bundle i.e. an aab, as they will not accept an apk. I can't remember when they outed apks, but it is probably at least a couple of years ago.

    When you deploy a release build to your device for testing, the deploy process creates an aab signed with your signing key and then deploys the correct apk for the device you are deploying to. Turn on Xamarin Diagnostics and you will see the log in the output window of the build process.

    If you have an obfuscated release build, then if it runs on your device, then obviously it is ok.

    If you are building a net7-android release, then you will see in your projects bin/release/net7.0-android folder both the Signed.aab and the Signed.apk which was deployed to your device.

    If you are building a Xamarin.Android release build then you will only see a Signed.aab. To see the size of the apk which was deployed to your device you would need to use Android Studio's Analyse APK tool to load your aab which will then display the size of your apk, or alternatively, Google Play will display its size after it is unloaded.

    When you upload to Google Play, it will accept your signing key, but will then issue a new upload key for you to use on subsequent uploads.

    If you want to check the obfuscation, you can use a tool like dotPeek from JetBrians.

    0 comments No comments
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    19 deleted comments

    Comments have been turned off. Learn more