Cannot upload MAUI file to Playstore due to signing in released mode

Question

Hello inte.net people,

I followed the Maui publication documentation

I got the aab file by following this process

The results I got are:

You uploaded an APK or Android App Bundle that was signed in debug mode. You need to sign your APK or Android App Bundle in release mode. Find out more about signing. The Android App Bundle was not signed.

What can I do to get this right?

Answer 1

Tried the same using the documentation provided by microsoft. Still getting the same error. I have provided the configuration to be release still getting the issue the app is in debug mode.

Step: 1: keytool -genkey -v -keystore myapp.keystore -alias key -keyalg RSA -keysize 2048 -validity 10000

Step: 2:

<PropertyGroup Condition="$(TargetFramework.Contains('-android')) and '$(Configuration)' == 'Release'">
    <AndroidKeyStore>True</AndroidKeyStore>
    <AndroidSigningKeyStore>myapp.keystore</AndroidSigningKeyStore>
    <AndroidSigningKeyAlias>key</AndroidSigningKeyAlias>
    <AndroidSigningKeyPass>*******</AndroidSigningKeyPass>
    <AndroidSigningStorePass>*******</AndroidSigningStorePass>
</PropertyGroup>

Step: 3: dotnet publish -f:net6.0-android -c:Release

Answer 2

Probably, you need to compile in Release mode release mode compilation

Answer 3

I'm having exactly the same issue.

Whether I sign via running Visual Studio in Release mode, from the command line, or even from my Azure CI pipeline, Google Play won't let me upload the signed Android App Bundle.

By the way, if you're looking to generate a signed.aab from your Azure build pipeline, I recommend the following:

https://www.andreasnesheim.no/setting-up-ci-for-your.net-maui-android-app-in-azure-devops/

You can then hookup the signed.aab artifact to a release pipeline that pushes to Google Play by doing something like:

https://damienaicheh.github.io/azure/devops/2021/10/25/configure-azure-devops-google-play-en.html

Well, that is what I'm trying to do, at least. To my understanding, you first need to create a manual release from Google Play in order for your release pipeline to be able to find where to deploy your app. This is why I'm running into the issue above.

Any future updates on this would be greatly appreciated!