您好互联网的人,
我遵循MAUI出版物
我通过关注此流程
我得到的结果是:
您上传了以调试模式签名的APK或Android App Bundle。您需要在发布模式下签署APK或Android App Bundle。了解有关签名的更多信息。 Android应用程序捆绑包没有签名。
我该怎么做才能正确?
Hello internet 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?
发布评论
评论(5)
检查您是否没有忘记
/p:androidKeystore = true
如果您是从命令行构建的!我的构建即使在MSBUILD后发行时也会被调试键签名更新。
我用于构建的命令:
这在
MSBUILD版本17.5.0-preview-23061-01+040E2A90E
中效果很好。 AAB用指定的密钥签名。但是使用
MSBUILD版本17.5.1+F6FDCF537
我的版本构建突然开始使用调试键签名。分析详细日志后,我发现androidkeystore
必须设置为true
,以便考虑您的自定义密钥。我不知道该参数是新添加的还是越野车且以前没有考虑的。添加
AndroidKeystore
参数后,签名是正确的。Check if you did not forget the
/p:AndroidKeyStore=True
if you are building from command line!My builds started being signed by the debug key even in release after a MSBuild update.
The command I used for building:
This worked great in
MSBuild version 17.5.0-preview-23061-01+040e2a90e
. The aab was signed with the specified key.But with
MSBuild version 17.5.1+f6fdcf537
my release builds suddenly started being signed with the debug key. After analysing the verbose logs I found out thatAndroidKeyStore
must be set totrue
for your custom key to be considered. I don't know whether this parameter was newly added or whether it was buggy and not considered before.After I added the
AndroidKeyStore
parameter the signature was correct.我遇到了完全相同的问题。
无论我是通过释放模式,命令行还是从我的Azure CI管道上签名,Google Play都不会让我上传签名的Android App Bundle。
顺便说一句,如果您想从Azure Build Pipeline生成签名的.AAB,我建议以下内容:
https://www.andreasnesheim.no/setting-up-ci-ci-ci-for-for-your-net-net-net-net-net-net-net-net-maui-android-app -in-in-azure-devops/
然后,您可以将签名的.aab文物连接到发行管道,该管道通过执行以下操作,将其推向Google Play:
好吧,至少这就是我要做的。据我了解,您首先需要从Google Play创建手动发布,以便您的发行管线能够找到部署应用程序的位置。这就是为什么我遇到上述问题的原因。
对此的任何未来更新将不胜感激!
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!
可能,您需要在发布模式下编译
发布模式汇编
Probably, you need to compile in Release mode
release mode compilation
大家好,当我发现问题时,我遇到了同样的错误,并且接近放弃。
仔细检查任何错别字。
我的问题是,我在.csproj中写了“ AndroidSignedKeystore”,而不是“ AndroidSigningKeystore”。
您不会遇到任何汇编错误或其他任何内容,因此值得检查是否存在相同的错误。
Hello everyone I had the same error and was close to giving up, when I found the problem.
DOUBLE CHECK FOR ANY TYPOS.
My problem was, that I wrote "AndroidSignedKeyStore" instead of "AndroidSigningKeyStore" in .csproj.
You wont get any compilation errors or anything, so its worth checking if you have the same error.
在您的CSPROJ中,请确保目标框架与您的属性组条件匹配。
条件需要匹配以使签名密钥(在属性组中)应用
in your csproj make sure that the target framework matches your PropertyGroup condition.
the condition needs to match to have the signing key (in the property group) applied