IBM MobileFirst 8 发布至Google Play Store的APK签名：密钥库选择疑问

Great question—this is a common spot where developers get tripped up when combining MobileFirst (MFP) with Google Play releases. Let’s break down the purpose of each keystore and which one you need for your Play Store upload:

Key Differences Between the Two Keystores #

• IBM MFP Console Keystore: This keystore is tied directly to MFP platform integration. It’s used for securing communication between your app and the MFP server, enabling push notifications via MFP, or validating app access to MFP services. It has nothing to do with signing your APK for Google Play distribution.
• Locally Created Keystore: This is the one you need for Google Play. Google requires every app uploaded to the Play Store to be signed with a unique, developer-controlled keystore. This signature identifies you as the app’s publisher, and you’ll need the exact same keystore for all future app updates (losing it means you can’t update your existing app—you’d have to submit a new app with a different package name).

Step-by-Step Guidance for Your Scenario #

1. For Google Play Publishing: Stick with creating or using your local keystore through Android Studio’s Generate Signed Bundle or APK wizard. You can either create a new keystore here (using the "Create new..." option) or select an existing one if you’ve already made one for previous releases.
2. For MFP Integration: If your app uses MFP features (like server calls, push), you’ll still need to configure the MFP keystore within your app’s MFP settings—this is a separate step from the Play Store signing process.

Critical Note #

Backup your local release keystore! Store it in a secure, encrypted location (like an external hard drive or password-protected cloud storage). Losing this keystore is a nightmare—Google won’t let you upload updates to your existing app without it.

内容的提问来源于stack exchange，提问作者rohan