Tim Tim 2, 3 3 gold badges 16 16 silver badges 12 12 bronze badges. Posted my second ever question and I get a "Tumbleweed" for my first badge!!!
Please mock me gently :- — Tim. Add a comment. Active Oldest Votes. Improve this answer. CommonsWare CommonsWare k gold badges silver badges bronze badges. Thanks — Nick. A useful trick is to save the output to a file, so you can grab the key.
Show 1 more comment. Valery Viktorovsky 6, 3 3 gold badges 34 34 silver badges 43 43 bronze badges. You saved me a headache or two — zabawaba Shouldn't those be backslashes, instead of forward slashes, on Windows? FYI, if you use jdk1. More people should explain like you! Ok I did this in Windows 7 bit system. Community Bot 1 1 1 silver badge. One needs simply to add a '-v' in the command in step 3. The default is 'android'.
Goddard Goddard 2, 26 26 silver badges 35 35 bronze badges. This seemed far harder to find than it needs to be for OSX. ApkBuilderMain and then call com. Just wanted to share it This should probably be a comment and not an answer. The next section describes some important terms and concepts related to app signing and security.
Java Keystores. A public key certificate. You must keep the upload key secret. However, you can share the certificate that is generated using your upload key. You may generate an upload key in one of the following ways:. This is used to register public key s with API providers; it's intended to be shared, as it does not contain your private key. A certificate fingerprint is a short and unique representation of a certificate that is often requested by API providers alongside the package name to register an app to use their service.
Other fingerprints can also be computed by downloading the original certificate. Because the debug certificate is created by the build tools and is insecure by design, most app stores including the Google Play Store do not accept apps signed with a debug certificate for publishing. Android Studio automatically stores your debug signing information in a signing configuration so you do not have to enter it every time you debug.
A signing configuration is an object consisting of all of the necessary information to sign your app, including the keystore location, keystore password, key name, and key password. For more information about how to build and run apps for debugging, see Build and Run Your App.
The self-signed certificate used to sign your app for debugging has an expiration date of 30 years from its creation date. When the certificate expires, you get a build error. To fix this problem, simply delete the debug. The next time you build and run a debug version of your app, Android Studio regenerates a new keystore and debug key. When you are ready to publish your app, you need to sign your app and upload it to an app store, such as Google Play.
When publishing your app to Google Play for the first time, you must also configure Play App Signing. Play App Signing is optional for apps created before August This section shows you how to properly sign your app for release and configure Play App Signing.
If you don't already have an upload key, which is useful when configuring Play App Signing, you can generate one using Android Studio as follows:. On the New Key Store window, provide the following information for your keystore and key, as shown in figure 2. Figure 2. Create a new upload key and keystore in Android Studio. If you would like to build and sign your app with your upload key, continue to the section about how to Sign your app with your upload key.
If you only want to generate the key and keystore, click Cancel. If you already have an upload key, use it to sign your app. If instead your app is already signed and published to the Google Play store with an existing app signing key, use it to sign your app and make sure to encrypt and export it to opt your app in to Play App Signing.
To sign your app using Android Studio, and export an existing app signing key, follow these steps:. Specify the path to your keystore, the alias for your key, and enter the passwords for both.
If you haven't yet prepared your upload keystore and key, first Generate an upload key and keystore and then return to complete this step. Figure 3. Sign your app with your upload key. You can then use your encrypted app signing key to opt in an existing app into Play App Signing.
In the next window shown in figure 4 , select a destination folder for your signed app, select the build type, choose the product flavor s if applicable. If you are building and signing an APK, you need to select which Signature Versions you want your app to support. To learn more, read about app signing schemes. Figure 4. Generate a signed version of your app for the selected product flavors.
Figure 5. Click the link in the popup to analyze or locate your app bundle, or locate your exported signing key. After Android Studio finishes building your signed app, you can either locate or analyze your app by clicking on the appropriate option in the pop-up notification.
If you selected the option to export your signing key, you can quickly navigate to it by clicking the dropdown arrow in the bottom right corner of the popup to expand it and clicking Show Exported Key File , as shown in figure 5. Otherwise, continue to the page about how to Upload your app to the Play Console. As described earlier in this page, configuring Play App Signing is required to sign your app for distribution through Google Play except for apps created before August , which may continue distributing self-signed APKs.
The steps you need to take depend on whether your app has not yet been published to Google Play, or your app is already signed and was published before August using an existing app signing key.
To configure signing for an app that has not yet been published to Google Play, proceed as follows:. In the section called App Bundles , click Browse files to locate and upload the app you signed using your upload key. If you need to create a new upload key for you app, go to the section about how to Reset a lost or compromised private upload key. Google Play now signs your app with your existing key when deploying it to users.
However, one of the most important benefits to Play App Signing is the ability to separate the key you use to sign the artifact you upload to Google Play from the key that Google Play uses to sign your app for distribution to users. So, consider following the steps in the next section to generate and register a separate upload key. When you're publishing an app that is not signed by an upload key, the Google Play Console provides the option to register one for future updates to the app.
That way, Google keeps your signing key secure, and you have the option to reset a lost or compromised private upload key. This section describes how to create an upload key, generate an upload certificate from it, and register that certificate with Google Play for future updates of your app.
Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. Google Cloud. Learn more about Collectives on Stack Overflow. The Overflow Blog. Does ES6 make JavaScript frameworks obsolete? Podcast Do polyglots have an edge when it comes to mastering programming Featured on Meta.
Now live: A fully responsive profile. Linked Related Hot Network Questions. Question feed. Stack Overflow works best with JavaScript enabled.
0コメント