From 3fdaa91c2c665870f3782229b4f8b3283b736cd0 Mon Sep 17 00:00:00 2001 From: Website Deployment Script Date: Thu, 11 Jan 2018 22:59:42 +0000 Subject: [PATCH] Deploy website Deploy website version based on 8c1372dce3e59780f98c930ea289d62d08b09580 --- docs/next/signed-apk-android.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/next/signed-apk-android.html b/docs/next/signed-apk-android.html index 17695a899a8..c6d42c5510e 100644 --- a/docs/next/signed-apk-android.html +++ b/docs/next/signed-apk-android.html @@ -1,10 +1,10 @@ -Generating Signed APK · React Native

React Native

next

Edit

Generating Signed APK

Android requires that all apps be digitally signed with a certificate before they can be installed, so to distribute your Android application via Google Play store, you'll need to generate a signed release APK. The Signing Your Applications page on Android Developers documentation describes the topic in detail. This guide covers the process in brief, as well as lists the steps required to package the JavaScript bundle.

Generating a signing key

You can generate a private signing key using keytool. On Windows keytool must be run from C:\Program Files\Java\jdkx.x.x_x\bin.

$ keytool -genkey -v -keystore my-release-key.keystore -alias my-key-alias -keyalg RSA -keysize 2048 -validity 10000