diff --git a/docs/0.28/appstate.html b/docs/0.28/appstate.html
index e606c1b06c5..3f1d2888d97 100644
--- a/docs/0.28/appstate.html
+++ b/docs/0.28/appstate.html
@@ -126,7 +126,7 @@ render: function
handler
function
Yes
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.28/appstate/index.html b/docs/0.28/appstate/index.html
index e606c1b06c5..3f1d2888d97 100644
--- a/docs/0.28/appstate/index.html
+++ b/docs/0.28/appstate/index.html
@@ -126,7 +126,7 @@ render: function
handler
function
Yes
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.29/appstate.html b/docs/0.29/appstate.html
index 72aa3029e19..10302586b61 100644
--- a/docs/0.29/appstate.html
+++ b/docs/0.29/appstate.html
@@ -126,7 +126,7 @@ render: function
handler
function
Yes
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.29/appstate/index.html b/docs/0.29/appstate/index.html
index 72aa3029e19..10302586b61 100644
--- a/docs/0.29/appstate/index.html
+++ b/docs/0.29/appstate/index.html
@@ -126,7 +126,7 @@ render: function
handler
function
Yes
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.30/appstate.html b/docs/0.30/appstate.html
index 34da02cdc5c..4a232f7b9ee 100644
--- a/docs/0.30/appstate.html
+++ b/docs/0.30/appstate.html
@@ -126,7 +126,7 @@ render: function
handler
function
Yes
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.30/appstate/index.html b/docs/0.30/appstate/index.html
index 34da02cdc5c..4a232f7b9ee 100644
--- a/docs/0.30/appstate/index.html
+++ b/docs/0.30/appstate/index.html
@@ -126,7 +126,7 @@ render: function
handler
function
Yes
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.31/appstate.html b/docs/0.31/appstate.html
index 1cfdb0d8222..29f81325ef6 100644
--- a/docs/0.31/appstate.html
+++ b/docs/0.31/appstate.html
@@ -126,7 +126,7 @@ render: function
handler
function
Yes
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.31/appstate/index.html b/docs/0.31/appstate/index.html
index 1cfdb0d8222..29f81325ef6 100644
--- a/docs/0.31/appstate/index.html
+++ b/docs/0.31/appstate/index.html
@@ -126,7 +126,7 @@ render: function
handler
function
Yes
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.32/appstate.html b/docs/0.32/appstate.html
index ea8b750e725..736aed0ea36 100644
--- a/docs/0.32/appstate.html
+++ b/docs/0.32/appstate.html
@@ -126,7 +126,7 @@ render: function
handler
function
Yes
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.32/appstate/index.html b/docs/0.32/appstate/index.html
index ea8b750e725..736aed0ea36 100644
--- a/docs/0.32/appstate/index.html
+++ b/docs/0.32/appstate/index.html
@@ -126,7 +126,7 @@ render: function
handler
function
Yes
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.33/appstate.html b/docs/0.33/appstate.html
index 6c5ad57df21..be75b46d10d 100644
--- a/docs/0.33/appstate.html
+++ b/docs/0.33/appstate.html
@@ -126,7 +126,7 @@ render: function
handler
function
Yes
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.33/appstate/index.html b/docs/0.33/appstate/index.html
index 6c5ad57df21..be75b46d10d 100644
--- a/docs/0.33/appstate/index.html
+++ b/docs/0.33/appstate/index.html
@@ -126,7 +126,7 @@ render: function
handler
function
Yes
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.34/appstate.html b/docs/0.34/appstate.html
index a7e456ff7d2..ba5047d7875 100644
--- a/docs/0.34/appstate.html
+++ b/docs/0.34/appstate.html
@@ -126,7 +126,7 @@ render: function
handler
function
Yes
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.34/appstate/index.html b/docs/0.34/appstate/index.html
index a7e456ff7d2..ba5047d7875 100644
--- a/docs/0.34/appstate/index.html
+++ b/docs/0.34/appstate/index.html
@@ -126,7 +126,7 @@ render: function
handler
function
Yes
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.35/appstate.html b/docs/0.35/appstate.html
index e8a29260a6e..aadfb118476 100644
--- a/docs/0.35/appstate.html
+++ b/docs/0.35/appstate.html
@@ -126,7 +126,7 @@ render: function
handler
function
Yes
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.35/appstate/index.html b/docs/0.35/appstate/index.html
index e8a29260a6e..aadfb118476 100644
--- a/docs/0.35/appstate/index.html
+++ b/docs/0.35/appstate/index.html
@@ -126,7 +126,7 @@ render: function
handler
function
Yes
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.36/appstate.html b/docs/0.36/appstate.html
index 07343738f67..c72c41a02b9 100644
--- a/docs/0.36/appstate.html
+++ b/docs/0.36/appstate.html
@@ -126,7 +126,7 @@ render: function
handler
function
Yes
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.36/appstate/index.html b/docs/0.36/appstate/index.html
index 07343738f67..c72c41a02b9 100644
--- a/docs/0.36/appstate/index.html
+++ b/docs/0.36/appstate/index.html
@@ -126,7 +126,7 @@ render: function
handler
function
Yes
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.37/appstate.html b/docs/0.37/appstate.html
index 6c57e1a2d98..53ac2f37fd8 100644
--- a/docs/0.37/appstate.html
+++ b/docs/0.37/appstate.html
@@ -126,7 +126,7 @@ render: function
handler
function
Yes
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.37/appstate/index.html b/docs/0.37/appstate/index.html
index 6c57e1a2d98..53ac2f37fd8 100644
--- a/docs/0.37/appstate/index.html
+++ b/docs/0.37/appstate/index.html
@@ -126,7 +126,7 @@ render: function
handler
function
Yes
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.38/appstate.html b/docs/0.38/appstate.html
index 345861ad2ad..17924d90f6c 100644
--- a/docs/0.38/appstate.html
+++ b/docs/0.38/appstate.html
@@ -126,7 +126,7 @@ render: function
handler
function
Yes
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.38/appstate/index.html b/docs/0.38/appstate/index.html
index 345861ad2ad..17924d90f6c 100644
--- a/docs/0.38/appstate/index.html
+++ b/docs/0.38/appstate/index.html
@@ -126,7 +126,7 @@ render: function
handler
function
Yes
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.39/appstate.html b/docs/0.39/appstate.html
index f75d2bea37e..6eb4d0751be 100644
--- a/docs/0.39/appstate.html
+++ b/docs/0.39/appstate.html
@@ -126,7 +126,7 @@ render: function
handler
function
Yes
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.39/appstate/index.html b/docs/0.39/appstate/index.html
index f75d2bea37e..6eb4d0751be 100644
--- a/docs/0.39/appstate/index.html
+++ b/docs/0.39/appstate/index.html
@@ -126,7 +126,7 @@ render: function
handler
function
Yes
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.40/appstate.html b/docs/0.40/appstate.html
index a3ffd71ffab..75e4f835ecb 100644
--- a/docs/0.40/appstate.html
+++ b/docs/0.40/appstate.html
@@ -126,7 +126,7 @@ render: function
handler
function
Yes
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.40/appstate/index.html b/docs/0.40/appstate/index.html
index a3ffd71ffab..75e4f835ecb 100644
--- a/docs/0.40/appstate/index.html
+++ b/docs/0.40/appstate/index.html
@@ -126,7 +126,7 @@ render: function
handler
function
Yes
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.41/appstate.html b/docs/0.41/appstate.html
index 4f742e5a7a8..0d42c06fe4a 100644
--- a/docs/0.41/appstate.html
+++ b/docs/0.41/appstate.html
@@ -126,7 +126,7 @@ render: function
handler
function
Yes
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
+
removeEventListener()
removeEventListener(type, handler);
diff --git a/docs/0.41/appstate/index.html b/docs/0.41/appstate/index.html
index 4f742e5a7a8..0d42c06fe4a 100644
--- a/docs/0.41/appstate/index.html
+++ b/docs/0.41/appstate/index.html
@@ -126,7 +126,7 @@ render: function
handler
function
Yes
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
Add a handler to AppState changes by listening to the change event type and providing the handler
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
Add a handler to AppState changes by listening to the change event type and providing the handler
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
Add a handler to AppState changes by listening to the change event type and providing the handler
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
Add a handler to AppState changes by listening to the change event type and providing the handler
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
Add a handler to AppState changes by listening to the change event type and providing the handler
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
Add a handler to AppState changes by listening to the change event type and providing the handler
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
Add a handler to AppState changes by listening to the change event type and providing the handler
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
Add a handler to AppState changes by listening to the change event type and providing the handler
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
Add a handler to AppState changes by listening to the change event type and providing the handler
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
Add a handler to AppState changes by listening to the change event type and providing the handler
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
Add a handler to AppState changes by listening to the change event type and providing the handler
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
Add a handler to AppState changes by listening to the change event type and providing the handler
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
Add a handler to AppState changes by listening to the change event type and providing the handler
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
Add a handler to AppState changes by listening to the change event type and providing the handler
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
Add a handler to AppState changes by listening to the change event type and providing the handler
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
Add a handler to AppState changes by listening to the change event type and providing the handler
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
Add a handler to AppState changes by listening to the change event type and providing the handler
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
Add a handler to AppState changes by listening to the change event type and providing the handler
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and use addListener and listener.remove() directly. That will be a breaking change though, as both the method and event names are different (addListener events are currently required to be globally unique).
A component which enables customization of the keyboard input accessory view on iOS. The input accessory view is displayed above the keyboard whenever a TextInput has focus. This component can be used to create custom toolbars.
To use this component wrap your custom toolbar with the InputAccessoryView component, and set a nativeID. Then, pass that nativeID as the inputAccessoryViewID of whatever TextInput you desire. A basic example:
A component which enables customization of the keyboard input accessory view on iOS. The input accessory view is displayed above the keyboard whenever a TextInput has focus. This component can be used to create custom toolbars.
To use this component wrap your custom toolbar with the InputAccessoryView component, and set a nativeID. Then, pass that nativeID as the inputAccessoryViewID of whatever TextInput you desire. A basic example:
For web URLs, the protocol ("http://", "https://") must be set accordingly!
+
+
This method may behave differently in a simulator e.g. "tel:" links are not able to be handled in the iOS simulator as there's no access to the dialer app.