diff --git a/docs/0.28/appstate.html b/docs/0.28/appstate.html index 1592ed14010..c325e1f6599 100644 --- a/docs/0.28/appstate.html +++ b/docs/0.28/appstate.html @@ -126,7 +126,7 @@ render: functionhandlerfunctionYes -

TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just 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).

removeEventListener()

removeEventListener(type, handler);
diff --git a/docs/0.28/appstate/index.html b/docs/0.28/appstate/index.html
index 1592ed14010..c325e1f6599 100644
--- a/docs/0.28/appstate/index.html
+++ b/docs/0.28/appstate/index.html
@@ -126,7 +126,7 @@ render: functionhandlerfunctionYes
 
 
-
TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just 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).

 

 
removeEventListener()

 
removeEventListener(type, handler);
diff --git a/docs/0.28/asyncstorage.html b/docs/0.28/asyncstorage.html
index 5f4500f7a37..0c0c12e8b47 100644
--- a/docs/0.28/asyncstorage.html
+++ b/docs/0.28/asyncstorage.html
@@ -1,4 +1,4 @@
-AsyncStorage · React Native
Edit
AsyncStorage
AsyncStorage is a simple, asynchronous, persistent, key-value storage system that is global to the app. It should be used instead of LocalStorage.

+        
Edit
AsyncStorage
AsyncStorage is an asynchronous, persistent, key-value storage system that is global to the app. It should be used instead of LocalStorage.

 
It is recommended that you use an abstraction on top of AsyncStorage instead of AsyncStorage directly for anything more than light usage since it operates globally.

-
On iOS, AsyncStorage is backed by native code that stores small values in a serialized dictionary and larger values in separate files. On Android, AsyncStorage will use either RocksDB or SQLite based on what is available. This JS code is a simple facade that provides a clear JS API, real Error objects, and simple non-multi functions. Each method returns a Promise object.

+
On iOS, AsyncStorage is backed by native code that stores small values in a serialized dictionary and larger values in separate files. On Android, AsyncStorage will use either RocksDB or SQLite based on what is available. This JS code is a facade that provides a clear JS API, real Error objects, and non-multi functions. Each method returns a Promise object.

 
Methods

 
    
 
  • getItem
    • 
diff --git a/docs/0.28/asyncstorage/index.html b/docs/0.28/asyncstorage/index.html
index 5f4500f7a37..0c0c12e8b47 100644
--- a/docs/0.28/asyncstorage/index.html
+++ b/docs/0.28/asyncstorage/index.html
@@ -1,4 +1,4 @@
-AsyncStorage · React Native
Edit
AsyncStorage
AsyncStorage is a simple, asynchronous, persistent, key-value storage system that is global to the app. It should be used instead of LocalStorage.

+        
Edit
AsyncStorage
AsyncStorage is an asynchronous, persistent, key-value storage system that is global to the app. It should be used instead of LocalStorage.

 
It is recommended that you use an abstraction on top of AsyncStorage instead of AsyncStorage directly for anything more than light usage since it operates globally.

-
On iOS, AsyncStorage is backed by native code that stores small values in a serialized dictionary and larger values in separate files. On Android, AsyncStorage will use either RocksDB or SQLite based on what is available. This JS code is a simple facade that provides a clear JS API, real Error objects, and simple non-multi functions. Each method returns a Promise object.

+
On iOS, AsyncStorage is backed by native code that stores small values in a serialized dictionary and larger values in separate files. On Android, AsyncStorage will use either RocksDB or SQLite based on what is available. This JS code is a facade that provides a clear JS API, real Error objects, and non-multi functions. Each method returns a Promise object.

 
Methods

 
    
 
  • getItem
    • 
diff --git a/docs/0.28/scrollview.html b/docs/0.28/scrollview.html
index 0cf0cae9690..39ca09bae33 100644
--- a/docs/0.28/scrollview.html
+++ b/docs/0.28/scrollview.html
@@ -69,7 +69,7 @@
               }
             });
         
Edit
ScrollView
Component that wraps platform ScrollView while providing integration with touch locking "responder" system.

-
Keep in mind that ScrollViews must have a bounded height in order to work, since they contain unbounded-height children into a bounded container (via a scroll interaction). In order to bound the height of a ScrollView, either set the height of the view directly (discouraged) or make sure all parent views have bounded height. Forgetting to transfer {flex: 1} down the view stack can lead to errors here, which the element inspector makes easy to debug.

+
Keep in mind that ScrollViews must have a bounded height in order to work, since they contain unbounded-height children into a bounded container (via a scroll interaction). In order to bound the height of a ScrollView, either set the height of the view directly (discouraged) or make sure all parent views have bounded height. Forgetting to transfer {flex: 1} down the view stack can lead to errors here, which the element inspector can be utilized to debug.

 
Doesn't yet support other contained responders from blocking this scroll view from becoming the responder.

 
Props

 
    
@@ -451,8 +451,8 @@
 
    The style of the scroll indicators.
    
 
      
 
    • default (the default), same as black.
      • 
-
    • black, scroll indicator is black. This style is good against a white content background.
      • 
-
    • white, scroll indicator is white. This style is good against a black content background.
      • 
+
    • black, scroll indicator is dark in color. This style is good against a light content background.
      • 
+
    • white, scroll indicator is light in color. This style is good against a dark content background.
      • 
 
    
 
diff --git a/docs/0.28/scrollview/index.html b/docs/0.28/scrollview/index.html
index 0cf0cae9690..39ca09bae33 100644
--- a/docs/0.28/scrollview/index.html
+++ b/docs/0.28/scrollview/index.html
@@ -69,7 +69,7 @@
               }
             });
         
    Edit
    ScrollView
    Component that wraps platform ScrollView while providing integration with touch locking "responder" system.
    
-
    Keep in mind that ScrollViews must have a bounded height in order to work, since they contain unbounded-height children into a bounded container (via a scroll interaction). In order to bound the height of a ScrollView, either set the height of the view directly (discouraged) or make sure all parent views have bounded height. Forgetting to transfer {flex: 1} down the view stack can lead to errors here, which the element inspector makes easy to debug.
    
+
    Keep in mind that ScrollViews must have a bounded height in order to work, since they contain unbounded-height children into a bounded container (via a scroll interaction). In order to bound the height of a ScrollView, either set the height of the view directly (discouraged) or make sure all parent views have bounded height. Forgetting to transfer {flex: 1} down the view stack can lead to errors here, which the element inspector can be utilized to debug.
    
 
    Doesn't yet support other contained responders from blocking this scroll view from becoming the responder.
    
 
    Props
    
 
      
@@ -451,8 +451,8 @@
 
      The style of the scroll indicators.
      
 
        
 
      • default (the default), same as black.
        • 
-
      • black, scroll indicator is black. This style is good against a white content background.
        • 
-
      • white, scroll indicator is white. This style is good against a black content background.
        • 
+
      • black, scroll indicator is dark in color. This style is good against a light content background.
        • 
+
      • white, scroll indicator is light in color. This style is good against a dark content background.
        • 
 
      
 
    
 
    
diff --git a/docs/0.29/appstate.html b/docs/0.29/appstate.html
index 5ec110fbcf7..4a2cd71a7ef 100644
--- a/docs/0.29/appstate.html
+++ b/docs/0.29/appstate.html
@@ -126,7 +126,7 @@ render: function
    
 
    handlerfunctionYes
    
 
 
    
-
    TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just 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).
    
 
    
 
    removeEventListener()
    
 
    removeEventListener(type, handler);
diff --git a/docs/0.29/appstate/index.html b/docs/0.29/appstate/index.html
index 5ec110fbcf7..4a2cd71a7ef 100644
--- a/docs/0.29/appstate/index.html
+++ b/docs/0.29/appstate/index.html
@@ -126,7 +126,7 @@ render: functionhandlerfunctionYes
 
 
-
    TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just 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).
    
 
    
 
    removeEventListener()
    
 
    removeEventListener(type, handler);
diff --git a/docs/0.29/scrollview.html b/docs/0.29/scrollview.html
index bac3d985735..dfaac35e2d7 100644
--- a/docs/0.29/scrollview.html
+++ b/docs/0.29/scrollview.html
@@ -69,7 +69,7 @@
               }
             });
         
Edit
ScrollView
Component that wraps platform ScrollView while providing integration with touch locking "responder" system.

-
Keep in mind that ScrollViews must have a bounded height in order to work, since they contain unbounded-height children into a bounded container (via a scroll interaction). In order to bound the height of a ScrollView, either set the height of the view directly (discouraged) or make sure all parent views have bounded height. Forgetting to transfer {flex: 1} down the view stack can lead to errors here, which the element inspector makes easy to debug.

+
Keep in mind that ScrollViews must have a bounded height in order to work, since they contain unbounded-height children into a bounded container (via a scroll interaction). In order to bound the height of a ScrollView, either set the height of the view directly (discouraged) or make sure all parent views have bounded height. Forgetting to transfer {flex: 1} down the view stack can lead to errors here, which the element inspector can be utilized to debug.

 
Doesn't yet support other contained responders from blocking this scroll view from becoming the responder.

 
Props

 
    
@@ -451,8 +451,8 @@
 
    The style of the scroll indicators.
    
 
      
 
    • default (the default), same as black.
      • 
-
    • black, scroll indicator is black. This style is good against a white content background.
      • 
-
    • white, scroll indicator is white. This style is good against a black content background.
      • 
+
    • black, scroll indicator is dark in color. This style is good against a light content background.
      • 
+
    • white, scroll indicator is light in color. This style is good against a dark content background.
      • 
 
    
 
diff --git a/docs/0.29/scrollview/index.html b/docs/0.29/scrollview/index.html
index bac3d985735..dfaac35e2d7 100644
--- a/docs/0.29/scrollview/index.html
+++ b/docs/0.29/scrollview/index.html
@@ -69,7 +69,7 @@
               }
             });
         
    Edit
    ScrollView
    Component that wraps platform ScrollView while providing integration with touch locking "responder" system.
    
-
    Keep in mind that ScrollViews must have a bounded height in order to work, since they contain unbounded-height children into a bounded container (via a scroll interaction). In order to bound the height of a ScrollView, either set the height of the view directly (discouraged) or make sure all parent views have bounded height. Forgetting to transfer {flex: 1} down the view stack can lead to errors here, which the element inspector makes easy to debug.
    
+
    Keep in mind that ScrollViews must have a bounded height in order to work, since they contain unbounded-height children into a bounded container (via a scroll interaction). In order to bound the height of a ScrollView, either set the height of the view directly (discouraged) or make sure all parent views have bounded height. Forgetting to transfer {flex: 1} down the view stack can lead to errors here, which the element inspector can be utilized to debug.
    
 
    Doesn't yet support other contained responders from blocking this scroll view from becoming the responder.
    
 
    Props
    
 
      
@@ -451,8 +451,8 @@
 
      The style of the scroll indicators.
      
 
        
 
      • default (the default), same as black.
        • 
-
      • black, scroll indicator is black. This style is good against a white content background.
        • 
-
      • white, scroll indicator is white. This style is good against a black content background.
        • 
+
      • black, scroll indicator is dark in color. This style is good against a light content background.
        • 
+
      • white, scroll indicator is light in color. This style is good against a dark content background.
        • 
 
      
 
    
 
    
diff --git a/docs/0.30/appstate.html b/docs/0.30/appstate.html
index 7b20d9f4474..8ce61072507 100644
--- a/docs/0.30/appstate.html
+++ b/docs/0.30/appstate.html
@@ -126,7 +126,7 @@ render: function
    
 
    handlerfunctionYes
    
 
 
    
-
    TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just 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).
    
 
    
 
    removeEventListener()
    
 
    removeEventListener(type, handler);
diff --git a/docs/0.30/appstate/index.html b/docs/0.30/appstate/index.html
index 7b20d9f4474..8ce61072507 100644
--- a/docs/0.30/appstate/index.html
+++ b/docs/0.30/appstate/index.html
@@ -126,7 +126,7 @@ render: functionhandlerfunctionYes
 
 
-
    TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just 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).
    
 
    
 
    removeEventListener()
    
 
    removeEventListener(type, handler);
diff --git a/docs/0.31/appstate.html b/docs/0.31/appstate.html
index 4a3d6079223..dc8c7559171 100644
--- a/docs/0.31/appstate.html
+++ b/docs/0.31/appstate.html
@@ -126,7 +126,7 @@ render: functionhandlerfunctionYes
 
 
-
    TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just 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).
    
 
    
 
    removeEventListener()
    
 
    removeEventListener(type, handler);
diff --git a/docs/0.31/appstate/index.html b/docs/0.31/appstate/index.html
index 4a3d6079223..dc8c7559171 100644
--- a/docs/0.31/appstate/index.html
+++ b/docs/0.31/appstate/index.html
@@ -126,7 +126,7 @@ render: functionhandlerfunctionYes
 
 
-
    TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just 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).
    
 
    
 
    removeEventListener()
    
 
    removeEventListener(type, handler);
diff --git a/docs/0.32/appstate.html b/docs/0.32/appstate.html
index 61f816aab2e..3eb6510a7ee 100644
--- a/docs/0.32/appstate.html
+++ b/docs/0.32/appstate.html
@@ -126,7 +126,7 @@ render: functionhandlerfunctionYes
 
 
-
    TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just 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).
    
 
    
 
    removeEventListener()
    
 
    removeEventListener(type, handler);
diff --git a/docs/0.32/appstate/index.html b/docs/0.32/appstate/index.html
index 61f816aab2e..3eb6510a7ee 100644
--- a/docs/0.32/appstate/index.html
+++ b/docs/0.32/appstate/index.html
@@ -126,7 +126,7 @@ render: functionhandlerfunctionYes
 
 
-
    TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just 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).
    
 
    
 
    removeEventListener()
    
 
    removeEventListener(type, handler);
diff --git a/docs/0.33/appstate.html b/docs/0.33/appstate.html
index edfd79782a1..82c50ed1980 100644
--- a/docs/0.33/appstate.html
+++ b/docs/0.33/appstate.html
@@ -126,7 +126,7 @@ render: functionhandlerfunctionYes
 
 
-
    TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just 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).
    
 
    
 
    removeEventListener()
    
 
    removeEventListener(type, handler);
diff --git a/docs/0.33/appstate/index.html b/docs/0.33/appstate/index.html
index edfd79782a1..82c50ed1980 100644
--- a/docs/0.33/appstate/index.html
+++ b/docs/0.33/appstate/index.html
@@ -126,7 +126,7 @@ render: functionhandlerfunctionYes
 
 
-
    TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just 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).
    
 
    
 
    removeEventListener()
    
 
    removeEventListener(type, handler);
diff --git a/docs/0.34/appstate.html b/docs/0.34/appstate.html
index 578362d8e3e..586f179d6e7 100644
--- a/docs/0.34/appstate.html
+++ b/docs/0.34/appstate.html
@@ -126,7 +126,7 @@ render: functionhandlerfunctionYes
 
 
-
    TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just 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).
    
 
    
 
    removeEventListener()
    
 
    removeEventListener(type, handler);
diff --git a/docs/0.34/appstate/index.html b/docs/0.34/appstate/index.html
index 578362d8e3e..586f179d6e7 100644
--- a/docs/0.34/appstate/index.html
+++ b/docs/0.34/appstate/index.html
@@ -126,7 +126,7 @@ render: functionhandlerfunctionYes
 
 
-
    TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just 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).
    
 
    
 
    removeEventListener()
    
 
    removeEventListener(type, handler);
diff --git a/docs/0.35/appstate.html b/docs/0.35/appstate.html
index 20e6e2b429b..c2cffb76bb1 100644
--- a/docs/0.35/appstate.html
+++ b/docs/0.35/appstate.html
@@ -126,7 +126,7 @@ render: functionhandlerfunctionYes
 
 
-
    TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just 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).
    
 
    
 
    removeEventListener()
    
 
    removeEventListener(type, handler);
diff --git a/docs/0.35/appstate/index.html b/docs/0.35/appstate/index.html
index 20e6e2b429b..c2cffb76bb1 100644
--- a/docs/0.35/appstate/index.html
+++ b/docs/0.35/appstate/index.html
@@ -126,7 +126,7 @@ render: functionhandlerfunctionYes
 
 
-
    TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just 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).
    
 
    
 
    removeEventListener()
    
 
    removeEventListener(type, handler);
diff --git a/docs/0.36/appstate.html b/docs/0.36/appstate.html
index cc148b48426..e58453b585b 100644
--- a/docs/0.36/appstate.html
+++ b/docs/0.36/appstate.html
@@ -126,7 +126,7 @@ render: functionhandlerfunctionYes
 
 
-
    TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just 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).
    
 
    
 
    removeEventListener()
    
 
    removeEventListener(type, handler);
diff --git a/docs/0.36/appstate/index.html b/docs/0.36/appstate/index.html
index cc148b48426..e58453b585b 100644
--- a/docs/0.36/appstate/index.html
+++ b/docs/0.36/appstate/index.html
@@ -126,7 +126,7 @@ render: functionhandlerfunctionYes
 
 
-
    TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just 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).
    
 
    
 
    removeEventListener()
    
 
    removeEventListener(type, handler);
diff --git a/docs/0.37/appstate.html b/docs/0.37/appstate.html
index a7345d24010..9fb6f866825 100644
--- a/docs/0.37/appstate.html
+++ b/docs/0.37/appstate.html
@@ -126,7 +126,7 @@ render: functionhandlerfunctionYes
 
 
-
    TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just 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).
    
 
    
 
    removeEventListener()
    
 
    removeEventListener(type, handler);
diff --git a/docs/0.37/appstate/index.html b/docs/0.37/appstate/index.html
index a7345d24010..9fb6f866825 100644
--- a/docs/0.37/appstate/index.html
+++ b/docs/0.37/appstate/index.html
@@ -126,7 +126,7 @@ render: functionhandlerfunctionYes
 
 
-
    TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just 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).
    
 
    
 
    removeEventListener()
    
 
    removeEventListener(type, handler);
diff --git a/docs/0.38/appstate.html b/docs/0.38/appstate.html
index 1e98391585b..03dc20997e2 100644
--- a/docs/0.38/appstate.html
+++ b/docs/0.38/appstate.html
@@ -126,7 +126,7 @@ render: functionhandlerfunctionYes
 
 
-
    TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just 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).
    
 
    
 
    removeEventListener()
    
 
    removeEventListener(type, handler);
diff --git a/docs/0.38/appstate/index.html b/docs/0.38/appstate/index.html
index 1e98391585b..03dc20997e2 100644
--- a/docs/0.38/appstate/index.html
+++ b/docs/0.38/appstate/index.html
@@ -126,7 +126,7 @@ render: functionhandlerfunctionYes
 
 
-
    TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just 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).
    
 
    
 
    removeEventListener()
    
 
    removeEventListener(type, handler);
diff --git a/docs/0.39/appstate.html b/docs/0.39/appstate.html
index 013aebc41b3..21ec4203b2e 100644
--- a/docs/0.39/appstate.html
+++ b/docs/0.39/appstate.html
@@ -126,7 +126,7 @@ render: functionhandlerfunctionYes
 
 
-
    TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just 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).
    
 
    
 
    removeEventListener()
    
 
    removeEventListener(type, handler);
diff --git a/docs/0.39/appstate/index.html b/docs/0.39/appstate/index.html
index 013aebc41b3..21ec4203b2e 100644
--- a/docs/0.39/appstate/index.html
+++ b/docs/0.39/appstate/index.html
@@ -126,7 +126,7 @@ render: functionhandlerfunctionYes
 
 
-
    TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just 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).
    
 
    
 
    removeEventListener()
    
 
    removeEventListener(type, handler);
diff --git a/docs/0.40/appstate.html b/docs/0.40/appstate.html
index f1def5b5a95..4302f7fd854 100644
--- a/docs/0.40/appstate.html
+++ b/docs/0.40/appstate.html
@@ -126,7 +126,7 @@ render: functionhandlerfunctionYes
 
 
-
    TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just 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).
    
 
    
 
    removeEventListener()
    
 
    removeEventListener(type, handler);
diff --git a/docs/0.40/appstate/index.html b/docs/0.40/appstate/index.html
index f1def5b5a95..4302f7fd854 100644
--- a/docs/0.40/appstate/index.html
+++ b/docs/0.40/appstate/index.html
@@ -126,7 +126,7 @@ render: functionhandlerfunctionYes
 
 
-
    TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just 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).
    
 
    
 
    removeEventListener()
    
 
    removeEventListener(type, handler);
diff --git a/docs/0.41/appstate.html b/docs/0.41/appstate.html
index 8bf073c3843..a6d1016a64d 100644
--- a/docs/0.41/appstate.html
+++ b/docs/0.41/appstate.html
@@ -126,7 +126,7 @@ render: functionhandlerfunctionYes
 
 
-
    TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just 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).
    
 
    
 
    removeEventListener()
    
 
    removeEventListener(type, handler);
diff --git a/docs/0.41/appstate/index.html b/docs/0.41/appstate/index.html
index 8bf073c3843..a6d1016a64d 100644
--- a/docs/0.41/appstate/index.html
+++ b/docs/0.41/appstate/index.html
@@ -126,7 +126,7 @@ render: functionhandlerfunctionYes
 
 
-
    TODO: now that AppState is a subclass of NativeEventEmitter, we could deprecate addEventListener and removeEventListener and just 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).
    
 
    
 
    removeEventListener()
    
 
    removeEventListener(type, handler);