blocks|key|1975652|text|该错误提示您之前已经上传过APK或App+Bundle。上传到Play控制台的所有工件都应该使用相同的密钥库签名。因此，该错误意味着您为App+Bundle签名的密钥与您之前上传的密钥不同。您必须找到您以前使用过密钥库，或者通过联系Play+Console支持团队来重置密钥。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1975653|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The error suggests that you have uploaded an APK or an App Bundle previously. All the artifacts you upload to the Play Console should all be signed with the same keystore.
So the error means that you signed the App Bundle with a key that is different than the ones you have uploaded previously. You have to either find that keystore you used before or reset the key by contacting Play Console support team.

blocks|key|1975668|text|我用头在桌子上敲了大约两个小时。当我最终放弃并填写我的"reset+key“请求时，我意识到我目前一直在试图将它上传到错误的项目。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1975669|因此，第一步:确认您正在尝试上传到正确的项目。|1975670|entityMap^0|1N|5|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

I was banging my head on the table over this for about two hours. When I finally gave up and was filling out my "reset key" request, I realized that I was currently attempting to upload it to the wrong project the whole time.

So, step one: confirm that you're attempting to upload to the correct project.

blocks|key|1604732|text|只需重新构建项目并再次生成签名的apk，然后尝试！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1604733|在这上面浪费了我2天的时间，我有我的keystore密钥，但仍然显示错误，并请求google生成新的密钥。读取一些随机的堆栈溢出，它被写入以重新构建项目并再次尝试上载。它成功了！|1604734|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Just rebuild the project and generate signed apk once again and try !

Wasted my 2 days on this, had my keystore key but still showed error and request google for generating new key.... Read some random stackoverflow, where it was written to rebuild the project and try uploading once again.. IT WORKED !

blocks|key|1975718|text|我所做的是从git中排除我的android文件，然后当我更改分支并重新构建时，我的build.gradle文件被覆盖。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1975719|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

What I did was exclude my android files from git, then when I changed branch and rebuilt, my build.gradle file was overwritten.

blocks|key|4086228|text|我尝试在这里使用多个答案&在this+question中，但不知何故得到了这个错误，因为我的android/app/build.gradle和android/gradle.properties文件有一些问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4086229|您应该检查的两件事(除了这里的其他解决方案之外)是：|4086230|4086231|在android/gradle.properties和android/app/build.gradle中，请确保keystore变量完全匹配。在android中，你可能会有这样的东西：|ordered-list-item|4086232|+MYAPP_RELEASE_STORE_PASSWORD=<>+MYAPP_RELEASE_KEY_PASSWORD=<>|unordered-list-item|4086233|Make+MYAPP_RELEASE_STORE_FILE=<>+MYAPP_RELEASE_KEY_ALIAS=<>+MYAPP_RELEASE_STORE_PASSWORD=<>+android/app/build.gradle：android{+...文件{+release+{+if+(project.hasProperty('MYAPP_RELEASE_STORE_FILE'))+{+storeFile+signingConfigs+(MYAPP_RELEASE_STORE_FILE)+storePassword+MYAPP_RELEASE_STORE_PASSWORD+keyAlias+MYAPP_RELEASE_KEY_ALIAS+keyPassword+MYAPP_RELEASE_KEY_PASSWORD+}|4086234|4086235|4086236|​|4086237|4086238|In+android/app/build.gradle，确保在你的release+buildTypes中将signingConfig设置为signingConfigs.release：android+{+...buildTypes+{调试...版本{+signingConfig+signingConfigs.release+}|4086239|4086240|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/54314838/googleplay-wrong-signing-key-for-app-bundle^0|1A|O|1Z|P|E|D|0|0|0|0|1|P|R|O|1K|8|1|1|2K|O|1|0|0|0|0|3|O|X|7|15|A|1H|D|1X|M|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@$9|17|A|18|B|C]|$9|19|A|1A|B|C]]|D|@$9|1B|A|1C|1|1D]]|E|$]]|$1|F|3|G|5|6|7|1E|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|1F|8|@]|D|@]|E|$]]|$1|I|3|J|5|K|7|1G|8|@$9|1H|A|1I|B|C]|$9|1J|A|1K|B|C]|$9|1L|A|1M|B|C]]|D|@]|E|$]]|$1|L|3|M|5|N|7|1N|8|@]|D|@]|E|$]]|$1|O|3|P|5|N|7|1O|8|@$9|1P|A|1Q|B|C]]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|1R|8|@]|D|@]|E|$]]|$1|R|3|-4|5|6|7|1S|8|@]|D|@]|E|$]]|$1|S|3|T|5|6|7|1T|8|@]|D|@]|E|$]]|$1|U|3|-4|5|6|7|1U|8|@]|D|@]|E|$]]|$1|V|3|W|5|K|7|1V|8|@$9|1W|A|1X|B|C]|$9|1Y|A|1Z|B|C]|$9|20|A|21|B|C]|$9|22|A|23|B|C]|$9|24|A|25|B|C]]|D|@]|E|$]]|$1|X|3|-4|5|6|7|26|8|@]|D|@]|E|$]]|$1|Y|3|-4|5|6|7|27|8|@]|D|@]|E|$]]]|Z|$10|$5|11|12|13|E|$14|15]]]]

I tried using the multiple answers here &amp; in <a href="https://stackoverflow.com/questions/54314838/googleplay-wrong-signing-key-for-app-bundle">this question</a>, but somehow I was getting this error because I had some issues with my <code>android/app/build.gradle</code> and <code>android/gradle.properties</code> files.

Two things you should check (in addition to the other solutions here) are:

<ol>
<li>In <code>android/gradle.properties</code> and <code>android/app/build.gradle</code>, make sure your <code>keystore</code> variables match exactly.

<ul>
<li>In <code>android/gradle.properties</code>, you probably have something like this:

<pre><code>MYAPP_RELEASE_STORE_FILE=&lt;&gt;
MYAPP_RELEASE_KEY_ALIAS=&lt;&gt;
MYAPP_RELEASE_STORE_PASSWORD=&lt;&gt;
MYAPP_RELEASE_KEY_PASSWORD=&lt;&gt;
</code></pre></li>
<li>Make sure these variable names exactly match those in <code>android/app/build.gradle</code>:

<pre><code>android {
 ...
 signingConfigs {
 release {
 if (project.hasProperty('MYAPP_RELEASE_STORE_FILE')) {
 storeFile file(MYAPP_RELEASE_STORE_FILE)
 storePassword MYAPP_RELEASE_STORE_PASSWORD
 keyAlias MYAPP_RELEASE_KEY_ALIAS
 keyPassword MYAPP_RELEASE_KEY_PASSWORD
 }
 }
 }
}
</code></pre></li>
</ul></li>
<li>In <code>android/app/build.gradle</code>, make sure you set <code>signingConfig</code> to <code>signingConfigs.release</code> in your <code>release</code> <code>buildTypes</code>:

<pre><code>android {
 ...
 buildTypes {
 debug ...
 release {
 signingConfig signingConfigs.release
 }
 }
}
</code></pre></li>
</ol>

blocks|key|5504163|text|我正在使用expo构建我的应用程序包。在我的例子中，我必须：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|5504164|5504165|手动创建新的密钥库文件。|ordered-list-item|5504166|5504167|或者使用命令从谷歌Play控制台|5504168|下载您现有的密钥库expo+fetch:android:keystore|unordered-list-item|style|CODE|5504169|
|5504170|Download上传证书我的应用程序导入应用程序的上传证书到新创建的密钥库文件，给它一个密钥别名和密码。使用java+keytool很容易做到这一点。MacOS在路径中，因此发出keytool+-h以查看available.|5504171|5504172|run+expo+ba+-c的各种命令，采用手动路由，当系统询问时，我指定了我在步骤1中创建的密钥库文件。|5504173|5504174|entityMap|0|LINK|mutability|MUTABLE|url|https://expo.io/^0|5|4|0|0|0|0|0|0|9|R|0|0|2H|A|0|0|4|A|0|0^^$0|@$1|2|3|4|5|6|7|15|8|@]|9|@$A|16|B|17|1|18]]|C|$]]|$1|D|3|-4|5|6|7|19|8|@]|9|@]|C|$]]|$1|E|3|F|5|G|7|1A|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|1B|8|@]|9|@]|C|$]]|$1|I|3|J|5|6|7|1C|8|@]|9|@]|C|$]]|$1|K|3|L|5|M|7|1D|8|@$A|1E|B|1F|N|O]]|9|@]|C|$]]|$1|P|3|Q|5|6|7|1G|8|@]|9|@]|C|$]]|$1|R|3|S|5|M|7|1H|8|@$A|1I|B|1J|N|O]]|9|@]|C|$]]|$1|T|3|Q|5|6|7|1K|8|@]|9|@]|C|$]]|$1|U|3|V|5|M|7|1L|8|@$A|1M|B|1N|N|O]]|9|@]|C|$]]|$1|W|3|-4|5|6|7|1O|8|@]|9|@]|C|$]]|$1|X|3|-4|5|6|7|1P|8|@]|9|@]|C|$]]]|Y|$Z|$5|10|11|12|C|$13|14]]]]

I am using <a href="https://expo.io" rel="nofollow noreferrer">expo</a> to build my app bundle. In my case, I had to:

<ol>
<li>Manually create a new keystore file. 
Or download your existing keystore using command <code>expo fetch:android:keystore</code></li>
<li>Download the Upload certificate of my app from Google Play Console</li>
<li>Import the Upload certificate of the app into the newly created keystore file, giving it a key alias and a password. This is easily done using the java keytool. In MacOS is in the path so issue a <code>keytool -h</code> to see the various commands available.</li>
<li>run <code>expo ba -c</code> , took the manual route and when asked, I specified the keystore file I created in step 1.</li>
</ol>

blocks|key|5504192|text|React+Native+here！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5504193|在尝试从./gradlew+bundleRelease命令上传生成的.aab文件时，我得到了这个错误。我修复了这个问题，再次使用Android+Studio导出.aab文件。我相信这是上传你的第一个.aab文件到谷歌Play的方法。如果你不知道该怎么做：|offset|length|style|BOLD|5504194|在Android+Studio中：|5504195|5504196|打开你反应本机的项目Android文件夹|ordered-list-item|5504197|转到Build+->+Generate+Signed+Bundle+/APK|5504198|选择安卓应用捆绑包|5504199|输入您的密钥库详细信息(如果这是您第一次执行此操作，您必须选中可用于Google+Play应用签名的导出加密密钥复选框)，然后在android+|5504200|完成后单击Next<代码>H111，它会为您提供查找创建的文件的选项<代码>H212G213|5504201|现在，如果您上传此.aab文件，它应该会被接受。|5504202|entityMap^0|0|4|N|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@$D|11|E|12|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|13|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|14|8|@]|9|@]|A|$]]|$1|K|3|L|5|M|7|15|8|@]|9|@]|A|$]]|$1|N|3|O|5|M|7|16|8|@]|9|@]|A|$]]|$1|P|3|Q|5|M|7|17|8|@]|9|@]|A|$]]|$1|R|3|S|5|M|7|18|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|19|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1A|8|@]|9|@]|A|$]]|$1|X|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|Y|$]]

React Native here!

I got this error after trying to upload the generated .aab file from the ./gradlew bundleRelease command. I fixed it by exporting the .aab file by using Android Studio again. I believe that this is the way to upload your first .aab file to Google Play anyway. In case you don't know how:

In Android Studio:

<ol>
<li>Open you React Native's project android folder</li>
<li>Go to Build -> Generate Signed Bundle / APK</li>
<li>Select Android App Bundle</li>
<li>Enter your key-store details (if this is your first time doing this, you have to check the Export encrypted key checkbox, which you can use for Google Play App signing) and click Next</li>
<li>When Android Studio finishes it gives you the option to locate the file(s) created</li>
</ol>

Now if you upload this .aab file, it should be accepted.

blocks|key|1975902|text|我意识到当我上传apk时，它会给出更详细的错误。因此，可以尝试解决错误，然后尝试应用程序捆绑包。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1975903|希望能有所帮助。|1975904|entityMap^0|8|3|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

I realized that when I upload apk it gives more detailed error. so maybe try that solve errors and maybe then try app bundle.

hope it helps.

blocks|key|1604822|text|这是你已经从+Play请求了一个新的上传密钥，但仍然得到这个错误(应该也适用于本地安卓和Flutter+)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1604823|我也遇到过同样的问题。下面是如何解决这个问题的步骤：|1604824|1604825|我们丢失了用于对应用程序进行签名的上载密钥(初始密钥库文件，可能是.jks)。|ordered-list-item|1604826|我们创建了一个新的密钥库文件，并按照声明的here+in+the+docs将创建的证书导出为PEM格式。我们向Google+Play团队发送了重置密钥的请求，并附上了.pem文件。|1604827|当Google+Play团队重置密钥时，我们尝试使用在步骤2中创建的新.jks密钥库，但错误再次出现。|1604828|1604829|解决方案是清理您的项目，从头开始重建它，以重置所有缓存的构建。|1604830|在颤动的情况下(我们在使用颤动构建应用程序时出现了这个错误)。请确保您使用|1604831|flutter+clean|code-block|syntax|javascript|1604832|在模拟器或设备上构建应用程序。|1604833|然后运行：|1604834|flutter+build+appbundle+--release|1604835|这就是在我们的案例中它是如何解决的。|1604836|PS。这也应该对原生Android有所帮助。|1604837|entityMap|0|LINK|mutability|MUTABLE|url|https://support.google.com/googleplay/android-developer/answer/7384423^0|6|1C|0|0|0|0|L|G|0|0|0|0|0|V|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1H|8|@$9|1I|A|1J|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1K|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|1L|8|@]|D|@]|E|$]]|$1|I|3|J|5|K|7|1M|8|@]|D|@]|E|$]]|$1|L|3|M|5|K|7|1N|8|@]|D|@$9|1O|A|1P|1|1Q]]|E|$]]|$1|N|3|O|5|K|7|1R|8|@]|D|@]|E|$]]|$1|P|3|-4|5|6|7|1S|8|@]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1T|8|@$9|1U|A|1V|B|C]]|D|@]|E|$]]|$1|S|3|T|5|6|7|1W|8|@]|D|@]|E|$]]|$1|U|3|V|5|W|7|1X|8|@]|D|@]|E|$X|Y]]|$1|Z|3|10|5|6|7|1Y|8|@]|D|@]|E|$]]|$1|11|3|12|5|6|7|1Z|8|@]|D|@]|E|$]]|$1|13|3|14|5|W|7|20|8|@]|D|@]|E|$X|Y]]|$1|15|3|16|5|6|7|21|8|@]|D|@]|E|$]]|$1|17|3|18|5|6|7|22|8|@]|D|@]|E|$]]|$1|19|3|-4|5|6|7|23|8|@]|D|@]|E|$]]]|1A|$1B|$5|1C|1D|1E|E|$1F|1G]]]]

Read this is you have requested a new upload key from Google Play and still get this error (should work for both native Android and Flutter as well).
I had experienced the same problem. And here's out steps on how to resolve it:
<ol>
<li>We've lost the upload key (initial keystore file, probably .jks) that was used to sign the app.</li>
<li>We created a new keystore file and exported created certificate to PEM format as stated <a href="https://support.google.com/googleplay/android-developer/answer/7384423" rel="nofollow noreferrer">here in the docs</a>. We sent the request to the Google Play Team to reset our key, attached .pem file.</li>
<li>When Google Play team reset the key we've tried to use the new .jks keystore we had created in the step 2 and the error appears one more time.</li>
</ol>
The solution is to clean your project, rebuild it from scratch to reset all the cached builds.
In case of Flutter (we had this error building the app using Flutter). Make sure you use
<pre><code>flutter clean
</code></pre>
Build the application on simulator or device.
Then run:
<pre><code>flutter build appbundle --release
</code></pre>
This is how it was solved in our case.
PS. This should also help on native Android too.

blocks|key|4086454|text|在构建一个签名的Android+App+Bundle时，我也遇到了同样的错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4086455|为了在本地机器上进行调试，我在release+build类型中启用了debuggable。|offset|length|style|CODE|4086456|看起来，Playstore认可了一个调试版本，并简单地说它不是一个有效的Bundle。|4086457|build.gradle:|BOLD|4086458|buildTypes+{
+++++release+{
+++++++++minifyEnabled+true
+++++++++proguardFiles+getDefaultProguardFile('proguard-android-optimize.txt'),+'proguard-rules.pro'
+++++++++//debuggable+=+true++<-----+Works+like+expected+when+disabled
+++++}
}|code-block|syntax|javascript|4086459|entityMap^0|0|Y|A|0|0|0|D|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@$D|V|E|W|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|Y|8|@$D|Z|E|10|F|L]]|9|@]|A|$]]|$1|M|3|N|5|O|7|11|8|@]|9|@]|A|$P|Q]]|$1|R|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|S|$]]

I had the same error when building a signed Android App Bundle. 
For debug purposes on the local maschine, I enabled <code>debuggable</code> in the release build type. 
It seems, Playstore recognized an debug build and simply said it is not a valid Bundle. 

build.gradle:

<pre><code>buildTypes {
 release {
 minifyEnabled true
 proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
 //debuggable = true &lt;----- Works like expected when disabled
 }
}
</code></pre>

blocks|key|1608635|text|对于那些在没有手动生成keystore的情况下发布了apk，并且在尝试从其他机器发布apk或捆绑包时遇到此问题的用户，请按照以下步骤操作：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1608636|1608637|blockquote|1608638|1608639|1608640|Copy+debug.keystore+(C:\Users\username.android\debug.keystore)，来自用于构建应用程序|ordered-list-item|1608641|的第一个版本的计算机|1608642|1608643|选择Build+>+Generate+Signed+Bundle/APK|1608644|1608645|1608646|提供debug.keystore+file|1608647|的密钥存储路径|1608648|1608649|使用下面提到的默认值填充其他字段，然后构建|1608650|1608651|Keystore+name:+"debug.keystore"
Keystore+password:+"android"
Key+alias:+"androiddebugkey"
Key+password:+"android"
CN:+"CN=Android+Debug,O=Android,C=US"|code-block|syntax|javascript|1608652|entityMap^0|B|8|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|19|8|@$9|1A|A|1B|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|1C|8|@]|D|@]|E|$]]|$1|G|3|-4|5|H|7|1D|8|@]|D|@]|E|$]]|$1|I|3|-4|5|6|7|1E|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|1F|8|@]|D|@]|E|$]]|$1|K|3|L|5|M|7|1G|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|1H|8|@]|D|@]|E|$]]|$1|P|3|-4|5|6|7|1I|8|@]|D|@]|E|$]]|$1|Q|3|R|5|M|7|1J|8|@]|D|@]|E|$]]|$1|S|3|-4|5|6|7|1K|8|@]|D|@]|E|$]]|$1|T|3|-4|5|6|7|1L|8|@]|D|@]|E|$]]|$1|U|3|V|5|M|7|1M|8|@]|D|@]|E|$]]|$1|W|3|X|5|6|7|1N|8|@]|D|@]|E|$]]|$1|Y|3|-4|5|6|7|1O|8|@]|D|@]|E|$]]|$1|Z|3|10|5|M|7|1P|8|@]|D|@]|E|$]]|$1|11|3|-4|5|6|7|1Q|8|@]|D|@]|E|$]]|$1|12|3|13|5|14|7|1R|8|@]|D|@]|E|$15|16]]|$1|17|3|-4|5|6|7|1S|8|@]|D|@]|E|$]]]|18|$]]

For those who have released apk without a manually generated <code>keystore</code> and facing this issue when trying to release the apk or bundle from a different machine, follow the below steps:
<blockquote>
<ol>
<li>Copy debug.keystore (C:\Users\username\.android\debug.keystore) from the machine which used to build the first version of the App
</li>
<li>Select Build &gt; Generate Signed Bundle/APK
</li>
<li>Provide the Key store path to the debug.keystore file
</li>
<li>Fill the other fields with the default values mentioned below and build
</li>
</ol>
</blockquote>
<pre><code>Keystore name: &quot;debug.keystore&quot;
Keystore password: &quot;android&quot;
Key alias: &quot;androiddebugkey&quot;
Key password: &quot;android&quot;
CN: &quot;CN=Android Debug,O=Android,C=US&quot;
</code></pre>

blocks|key|1976186|text|​|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1976187|📷|atomic|offset|length|1976188|1976189|这对我很有效！|1976190|1976191|在第一次上传apk/+|1976192|到play+store时，你可能会生成private_key.pepk，然后你的密钥也可能会被更改。因此，如果您选择了default+key+alias+key0，那么请确保您选择了正确的别名，然后只继续。如果这些步骤正确，那么您捆绑包将被成功上传。|blockquote|style|BOLD|1976193|1976194|1976195|1976196|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/c5465b8cb2d938d196473e38e3af2068.png|imageAlt^0|0|0|1|0|0|0|0|0|0|J|G|25|4|0|0|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|14|8|@]|9|@$E|15|F|16|1|17]]|A|$]]|$1|G|3|4|5|6|7|18|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|19|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|1B|8|@]|9|@]|A|$]]|$1|M|3|N|5|O|7|1C|8|@$E|1D|F|1E|P|Q]|$E|1F|F|1G|P|Q]]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|11|12|-4]]]]

<a href="https://i.stack.imgur.com/tWqf2.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/tWqf2.png" alt="Verify the details as shown in image and body" /></a>
This is worked for me!
<hr />
<blockquote>
While uploading apk/bundle first time to play store you might generated
private_key.pepk then your key might be also changed. So if you selected default key alias key0 then make sure you selected proper alias then only proceed. If that steps is correct then your bundle will be upload successfully.
</blockquote>
<hr />

blocks|key|1976250|text|延迟回答(对于任何可能还在为这个话题而努力的人)-|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1976251|您可能忘记了该项目的.jks文件。|1976252|1976253|在文件资源管理器中搜索.jks文件。|ordered-list-item|1976254|1976255|1976256|将其连接到您的项目。|1976257|1976258|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|R|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|T|8|@]|9|@]|A|$]]|$1|J|3|K|5|G|7|U|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|V|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|N|$]]

Late answer(for any one possibly still struggling with this topic)-
You may have forgot the .jks file of that project.
<ol>
<li>Search for .jks files in File explorer.
</li>
<li>Connect it to your project.
</li>
</ol>

blocks|key|5504594|text|如果您正在将应用程序发布到playstore并发现错误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：那么，如果您在达到图片中显示的当前状态之前没有生成/更改应用程序包或重建/清理项目，那么请确保在play控制台上创建新的应用程序项目，因为play+console可能会混合这两个键。image|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|5504595|entityMap|0|LINK|mutability|MUTABLE|url|https://i.stack.imgur.com/EBBU9.jpg^0|R|3Q|71|5|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]]|D|@$9|Q|A|R|1|S]]|E|$]]|$1|F|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]]]

If you are publishing app to playstore and find error <code>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</code>:
Then,
If you have not generated/changed app bundle or rebuild/clean project before reaching the current state displayed in pic then make sure to make new app project on play console as play console might be mixing the two keys.
<a href="https://i.stack.imgur.com/EBBU9.jpg" rel="nofollow noreferrer">image</a>

blocks|key|1604995|text|在这个问题上浪费了几个小时之后，下面的解决方案对我很有效-|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1604996|当你创建签名包时，它被保存到某个位置，然后当它被拒绝时，你又去创建新的签名包，好吧，这就是错误发生的地方。|1604997|查看当您现在要创建另一个签名包时，您为它签名另一个文件夹，假设上一个是上次创建的，请确保您将签名密钥存储在的“同一文件夹”中，不需要创建任何新的签名密钥路径，只需使用您第一次创建时使用的路径。|offset|length|style|BOLD|1604998|See+this+image,+use+the+same+path+which+you+have+used+during+first+time|1604999|使用您第一次使用的相同JKS文件。现在，当您将创建包文件时，它将拥有正确的密钥。|1605000|谢谢！|1605001|entityMap|0|LINK|mutability|MUTABLE|url|https://i.stack.imgur.com/OLftT.png^0|0|0|2|Q|T|B|1H|8|27|H|0|0|1Z|0|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Z|8|@$F|10|G|11|H|I]|$F|12|G|13|H|I]|$F|14|G|15|H|I]|$F|16|G|17|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|18|8|@]|9|@$F|19|G|1A|1|1B]]|A|$]]|$1|L|3|M|5|6|7|1C|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1D|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]]|Q|$R|$5|S|T|U|A|$V|W]]]]

Well after wasting hours on this problem ,Below Solution works for me -
When you are creating signed bundle it gets saved to some location,
Then when it gets rejected,
you went again to make new Signed Bundle,
Well thats where the mistake happens.
See when now you will create another signed bundle,
you sign it another folder , assuming that previous one was made last time,
, make sure you store the signed key in the &quot;SAME FOLDER&quot;,
No need to make any new signed key path ,
JUST use the path you used while doing it for First time.
<a href="https://i.stack.imgur.com/OLftT.png" rel="nofollow noreferrer">See this image,
use the same path which you have used during first time</a>
Use the same JKS FILES as you have used for the first time.
NOW WHEN YOU WILL MAKE BUNDLES FILE,
IT WILL BE HAVING THE CORRECT KEY.
Thank You!!!

blocks|key|1605008|text|确保您使用正确的JKS进行应用程序签名。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1605009|常见的开发者错误，具有多种风格的Android应用程序使用不同的JKS文件。|1605010|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Make sure you are using the correct JKS for App Signing.
Common developer error, Android app with multiple flavours sign bundle using different JKS file.

blocks|key|1976346|text|我得到了相同的错误：enter+image+description+here|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1976347|在我的例子中，我改变了：|1976348|android+{
compileSdkVersion+30|code-block|syntax|javascript|1976349|使用|1976350|android+{
compileSdkVersion+31|1976351|和|1976352|targetSdkVersion+30|1976353|1976354|targetSdkVersion+31|1976355|而且它起作用了。希望它能为你工作。|1976356|entityMap|0|LINK|mutability|MUTABLE|url|https://i.stack.imgur.com/sLMTu.png^0|A|S|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|15|8|@]|9|@$A|16|B|17|1|18]]|C|$]]|$1|D|3|E|5|6|7|19|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|1A|8|@]|9|@]|C|$I|J]]|$1|K|3|L|5|6|7|1B|8|@]|9|@]|C|$]]|$1|M|3|N|5|H|7|1C|8|@]|9|@]|C|$I|J]]|$1|O|3|P|5|6|7|1D|8|@]|9|@]|C|$]]|$1|Q|3|R|5|H|7|1E|8|@]|9|@]|C|$I|J]]|$1|S|3|L|5|6|7|1F|8|@]|9|@]|C|$]]|$1|T|3|U|5|H|7|1G|8|@]|9|@]|C|$I|J]]|$1|V|3|W|5|6|7|1H|8|@]|9|@]|C|$]]|$1|X|3|-4|5|6|7|1I|8|@]|9|@]|C|$]]]|Y|$Z|$5|10|11|12|C|$13|14]]]]

I got the same error :
<a href="https://i.stack.imgur.com/sLMTu.png" rel="nofollow noreferrer">enter image description here</a>
In my case I changed :
<pre><code>android {
compileSdkVersion 30
</code></pre>
with
<pre><code>android {
compileSdkVersion 31
</code></pre>
and
<pre><code>targetSdkVersion 30
</code></pre>
with
<pre><code>targetSdkVersion 31
</code></pre>
and it worked. Hope it will work for you.

How do I sign my android app bundle with the correct signing key?

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

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

如何使用正确的签名密钥对我的android应用程序包进行签名？

问您的Android应用程序捆绑包使用错误的密钥签名。请确保使用正确的签名密钥对应用程序捆绑包进行签名，然后重试
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问您的Android应用程序捆绑包使用错误的密钥签名。请确保使用正确的签名密钥对应用程序捆绑包进行签名，然后重试EN