You need to enable JavaScript to run this app.
优惠活动
大模型
产品
解决方案
定价
更多

Ionic 3(Cordova) cordova-plugin-googleplus Play商店安装后Error 10求助

Ionic Cordova APK Installs from Google Play with Error 10, But Works When Sideloaded

Let's break down what's likely causing this Error 10 issue and how to fix it—this is almost always related to Google Sign-In SHA-1 certificate mismatches, especially with Google Play's app signing system.

1. Google Play's App Signing Service Is Overriding Your APK Signature

When you upload your APK to Google Play, if you're using App Signing by Google Play (enabled by default for most new apps), Google re-signs your APK with its own dedicated release key. This means the SHA-1 certificate your app uses when downloaded from the Play Store is not the same as the one from your local keystore.

You configured Google Sign-In with your local keystore's SHA-1, but the Play Store version relies on Google's release key SHA-1—this mismatch triggers Error 10 during Google Sign-In validation.

2. Fix Step 1: Get Google Play's Release Key SHA-1

  • Log into your Google Play Console and navigate to your app
  • Go to Release > Setup > App Signing (in the left sidebar)
  • Copy the SHA-1 certificate fingerprint listed under "App signing certificate"

3. Fix Step 2: Update Google Cloud Console Credentials

  • Open your Google Cloud Console project linked to the app
  • Go to APIs & Services > Credentials
  • Find the Android client ID you created for Google Sign-In, then edit it
  • Add the Google Play app signing SHA-1 you just copied (you can keep your local SHA-1 too, to support sideloaded testing)

4. Double-Check Your Local Signing Workflow

Wait a second—looking at your steps, you generated a keystore named release-HMC.keystore but signed your APK with release-key.keystore. Are these the same file? If not, that's another critical mismatch:

  • You fetched the SHA-1 from release-HMC.keystore, but signed your upload APK with release-key.keystore—so even before Google Play re-signs it, your upload APK's SHA-1 doesn't match what you configured.
  • Make sure you're using the same keystore for both signing the APK and generating the SHA-1 you added to Google Cloud.

5. Quick Additional Checks

  • Confirm the Google+ API is enabled in the correct Google Cloud project (it's easy to mix up projects!)
  • Verify your app's package name in config.xml exactly matches the package name linked to your Google Sign-In client ID.

Once you update the SHA-1 in Google Cloud with the Play Store's app signing certificate, the Error 10 should disappear for users downloading from the Play Store.

内容的提问来源于stack exchange,提问作者Ravindra Vairagi

相关产品推荐
方舟 Agent Plan

超全模态模型 × Harness 升级,最新支持 Deepseek-V4.1-Flash、GLM-5.3 系列、Doubao-Seedream-5.0-pro、Kimi-K3 (部分), 限时 9.9 元起

最近更新时间:2026.05.15 03:42:15