on master help sign in
android: update docs to match steps that are now handled by ob deploy
commit4fdd14bccec767bc02fc1083f9cb2a5df2510fe6 authorLuigy Leon <luichi.19@gmail.com> dateMon 19 Nov 2018, 18:06 (8 years ago) parentc1e0cc0
1 file changed−29
README.md−29
README.md−29
@@ -262,35 +262,6 @@ This should copy over and install the application on your device (if you see a
262262
263263#### Releasing to Play Store
264264
265−##### Configure signing
266−
267−The previous section would have generated a debug version of the app. In order to build a release version you will need to sign your app. Obelisk can automatically sign the app during build if you provide it with your keystore file in `default.nix`.
268−
269−First, if you do not already have a keystore, create it as follows (for more information, see the [Android documentation](https://developer.android.com/studio/publish/app-signing#signing-manually)):
270−
271−```
272−nix-shell -E "let pkgs = import <nixpkgs> {}; in pkgs.mkShell { buildInputs = [ pkgs.jdk9 ]; }" --run "keytool -genkey -v -keystore myandroidkey.jks -keyalg RSA -keysize 2048 -validity 10000 -alias myandroidalias"
273−```
274−
275−(Be sure to give an appropriate keystore filename and key alias string above.)
276−
277−The `keytool` command will ask you for some details, including a keystore password and a key password (we will use these passwords further below). It will now have created a `myandroidkey.jks` file under the current directory. Move that to somewhere safe, and note down its full path.
278−
279−Now edit your project's `default.nix` and tell Obelisk of your app's keystore file. Your `default.nix` should look like this after the edit:
280−
281−```nix
282− ...
283− android.applicationId = "com.example.myapp";
284− android.displayName = "My App";
285− android.releaseKey =
286− { storeFile = /path/to/myandroidkey.jks;
287− storePassword = "abcd1234";
288− keyAlias = "myandroidalias";
289− keyPassword = "abcd1234";
290− };
291− ...
292−```
293−
294265##### Build a release version
295266
296267After having configured signing for your app, you may proceed to build a release version of the app. This is no different to how you build the non-release version, so consult the section [Android](#android) further above for exact instructions on building and deploying to your device.