You can do anything in your task as long as it doesn't touch UI: network requests, timers and so on. Once your task completes (i.e. the promise is resolved), React Native will go into "paused" mode (unless there are other tasks running, or there is a foreground app).
+You can do anything in your task such as network requests, timers and so on, as long as it doesn't touch UI. Once your task completes (i.e. the promise is resolved), React Native will go into "paused" mode (unless there are other tasks running, or there is a foreground app).
Yes, this does still require some native code, but it's pretty thin. You need to extend HeadlessJsTaskService and override getTaskConfig, e.g.:
public class MyTaskService extends HeadlessJsTaskService {
diff --git a/docs/next/headless-js-android/index.html b/docs/next/headless-js-android/index.html
index 5924cebaa97..8d801e377f2 100644
--- a/docs/next/headless-js-android/index.html
+++ b/docs/next/headless-js-android/index.html
@@ -39,7 +39,7 @@
// do stuff
};
You can do anything in your task as long as it doesn't touch UI: network requests, timers and so on. Once your task completes (i.e. the promise is resolved), React Native will go into "paused" mode (unless there are other tasks running, or there is a foreground app).
+You can do anything in your task such as network requests, timers and so on, as long as it doesn't touch UI. Once your task completes (i.e. the promise is resolved), React Native will go into "paused" mode (unless there are other tasks running, or there is a foreground app).
Yes, this does still require some native code, but it's pretty thin. You need to extend HeadlessJsTaskService and override getTaskConfig, e.g.:
public class MyTaskService extends HeadlessJsTaskService {
diff --git a/docs/next/signed-apk-android.html b/docs/next/signed-apk-android.html
index 672a3fb7b67..26754f617b9 100644
--- a/docs/next/signed-apk-android.html
+++ b/docs/next/signed-apk-android.html
@@ -36,7 +36,16 @@
This command prompts you for passwords for the keystore and key, and to provide the Distinguished Name fields for your key. It then generates the keystore as a file called my-release-key.keystore.
The keystore contains a single key, valid for 10000 days. The alias is a name that you will use later when signing your app, so remember to take note of the alias.
-On Mac if you not sure where is your jdk bin folder is then perform the following command to find it, $ /usr/libexec/java_home it will output the directroy of jdk which looks like this, /Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home then navigate to that directory by the following command, $ cd /Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home/ Now you can perform the keytool command with sudo permission as shown below, $ sudo keytool -genkey -v -keystore my-release-key.keystore -alias my-key-alias -keyalg RSA -keysize 2048 -validity 10000 Note: Remember to keep your keystore file private and never commit it to version control.
On Mac, if you're not sure where your jdk bin folder is, then perform the following command to find it:
+$ /usr/libexec/java_home
+It will output the directory of the jdk, which will look something like this:
+/Library/Java/JavaVirtualMachines/jdkX.X.X_XXX.jdk/Contents/Home
+Navigate to that directory by using the command $ cd /your/jdk/path and use the keytool command with sudo permission as shown below.
$ sudo keytool -genkey -v -keystore my-release-key.keystore -alias my-key-alias -keyalg RSA -keysize 2048 -validity 10000
+Note: Remember to keep your keystore file private and never commit it to version control.
my-release-key.keystore file under the android/app directory in your project folder.This command prompts you for passwords for the keystore and key, and to provide the Distinguished Name fields for your key. It then generates the keystore as a file called my-release-key.keystore.
The keystore contains a single key, valid for 10000 days. The alias is a name that you will use later when signing your app, so remember to take note of the alias.
-On Mac if you not sure where is your jdk bin folder is then perform the following command to find it, $ /usr/libexec/java_home it will output the directroy of jdk which looks like this, /Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home then navigate to that directory by the following command, $ cd /Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home/ Now you can perform the keytool command with sudo permission as shown below, $ sudo keytool -genkey -v -keystore my-release-key.keystore -alias my-key-alias -keyalg RSA -keysize 2048 -validity 10000 Note: Remember to keep your keystore file private and never commit it to version control.
On Mac, if you're not sure where your jdk bin folder is, then perform the following command to find it:
+$ /usr/libexec/java_home
+It will output the directory of the jdk, which will look something like this:
+/Library/Java/JavaVirtualMachines/jdkX.X.X_XXX.jdk/Contents/Home
+Navigate to that directory by using the command $ cd /your/jdk/path and use the keytool command with sudo permission as shown below.
$ sudo keytool -genkey -v -keystore my-release-key.keystore -alias my-key-alias -keyalg RSA -keysize 2048 -validity 10000
+Note: Remember to keep your keystore file private and never commit it to version control.
my-release-key.keystore file under the android/app directory in your project folder.