Display the iOS share sheet. The options object should contain
one or both of message and url and can additionally have
a subject or excludedActivityTypes:
url (string) - a URL to share
message (string) - a message to share
subject (string) - a subject for the message
excludedActivityTypes (array) - the activites to exclude from the ActionSheet
NOTE: if url points to a local file, or is a base64-encoded
uri, the file it points to will be loaded and shared directly.
diff --git a/releases/next/docs/alert.html b/releases/next/docs/alert.html
index 293c5d8115c..1d0e2d3877c 100644
--- a/releases/next/docs/alert.html
+++ b/releases/next/docs/alert.html
@@ -13,7 +13,7 @@ of a neutral, negative and a positive button:
If you specify one butt
{text:'Cancel', onPress:()=> console.log('Cancel Pressed'), style:'cancel'},{text:'OK', onPress:()=> console.log('OK Pressed')},]
-)
This optional argument should
be either a single-argument function or an array of buttons. If passed
a function, it will be called when the user taps 'OK'.
If passed an array of button configurations, each button should include
@@ -19,7 +19,7 @@ cross-platform support if you don't need to create iOS-only prompts.
This optional argument should
be either a single-argument function or an array of buttons. If passed
a function, it will be called with the prompt's value when the user
diff --git a/releases/next/docs/animated.html b/releases/next/docs/animated.html
index d80b547bd7e..7d369102d20 100644
--- a/releases/next/docs/animated.html
+++ b/releases/next/docs/animated.html
@@ -58,18 +58,18 @@ event loop. This does influence the API, so keep that in mind when it seems a
little trickier to do something compared to a fully synchronous system.
Checkout Animated.Value.addListener as a way to work around some of these
limitations, but use it sparingly since it might have performance
-implications in the future.
Starts an array of animations in order, waiting for each to complete
before starting the next. If the current running animation is stopped, no
-following animations will be started.
Starts an array of animations all at the same time. By default, if one
of the animations is stopped, they will all be stopped. You can override
-this with the stopTogether flag.
Standard value for driving animations. One Animated.Value can drive
multiple properties in a synchronized fashion, but can only be driven by one
mechanism at a time. Using a new mechanism (e.g. starting a new animation,
-or calling setValue) will stop any previous ones.
Sets an offset that is applied on top of whatever value is set, whether via
setValue, an animation, or Animated.event. Useful for compensating
-things like the start of a pan gesture.
Adds an asynchronous listener to the value so you can observe updates from
animations. This is useful because there is no way to
-synchronously read the value because it might be driven natively.
Stops any running animation or tracking. callback is invoked with the
final value after stopping the animation, which is useful for updating
-state to match the animation position with layout.
2D Value for driving 2D animations, such as pan gestures. Almost identical
API to normal Animated.Value, but multiplexed. Contains two regular
Animated.Values under the hood. Example:
class DraggableView extends React.Component{constructor(props){
@@ -123,7 +123,7 @@ API to normal Animated.Value, but multiplexed. Contains two regula
</Animated.View>);}
- }
'use strict';
diff --git a/releases/next/docs/appregistry.html b/releases/next/docs/appregistry.html
index 8750ff3e649..7e2f4d6dc4d 100644
--- a/releases/next/docs/appregistry.html
+++ b/releases/next/docs/appregistry.html
@@ -6,7 +6,7 @@ for the app and then actually run the app when it's ready by invoking
AppRegistry.unmountApplicationComponentAtRootTag with the tag that was
pass into runApplication. These should always be used as a pair.
AppRegistry should be required early in the require sequence to make
sure the JS execution environment is setup before other modules are
-required.
Saves the photo or video to the camera roll / gallery.
On Android, the tag must be a local image or video URI, such as "file:///sdcard/img.png".
On iOS, the tag can be any image URI (including local, remote asset-library and base64 data URIs)
or a local video file URI (remote or data URIs are not supported for saving video at this time).
If the tag has a file extension of .mov or .mp4, it will be inferred as a video. Otherwise
it will be treated as a photo. To override the automatic choice, you can pass an optional
-type parameter that must be one of 'photo' or 'video'.
Returns a Promise which will resolve with the new URI.
The available keys for the options object are:
date (Date object or timestamp in milliseconds) - date to show by default
minDate (Date or timestamp in milliseconds) - minimum date that can be selected
* maxDate (Date object or timestamp in milliseconds) - minimum date that can be selected
Returns a Promise which will be invoked an object containing action, year, month (0-11),
day if the user picked a date. If the user dismissed the dialog, the Promise will
still be resolved with action being DatePickerAndroid.dismissedAction and all the other keys
being undefined. Always check whether the action before reading the values.
Note the native date picker dialog has some UI glitches on Android 4 and lower
-when using the minDate and maxDate options.
Initial dimensions are set before runApplication is called so they should
be available before any other require's are run, but may be updated later.
Note: Although dimensions are available immediately, they may change (e.g
due to device rotation) so any rendering logic or styles that depend on
these constants should try to call this function on every render, rather
diff --git a/releases/next/docs/drawerlayoutandroid.html b/releases/next/docs/drawerlayoutandroid.html
index a953c24b6b9..26d19f18d1c 100644
--- a/releases/next/docs/drawerlayoutandroid.html
+++ b/releases/next/docs/drawerlayoutandroid.html
@@ -37,7 +37,7 @@ from the edge of the window.
Make the drawer take the entire screen and draw the background of the
status bar to allow it to open over the status bar. It will only have an
-effect on API 21+.
Try to open the given url with any of the installed apps.
You can use other URLs, like a location (e.g. "geo:37.484847,-122.148386"), a contact,
or any other URL that can be opened with the installed apps.
NOTE: This method will fail if the system doesn't know how to open the specified URL.
-If you're passing in a non-http(s) URL, it's best to check {@code canOpenURL} first.
NOTE: For web URLs, the protocol ("http://", "https://") must be set accordingly!
You can provide custom extraction and hasChanged functions for section
headers and rows. If absent, data will be extracted with the
defaultGetRowData and defaultGetSectionHeaderData functions.
The default extractor expects data of one of the following forms:
{ sectionID_1:{ rowID_1: <rowData1>,...},...}
or
{ sectionID_1:[ <rowData1>, <rowData2>,...],...}
or
[[ <rowData1>, <rowData2>,...],...]
The constructor takes in a params argument that can contain any of the
-following:
Clones this ListViewDataSource with the specified dataBlob and
rowIdentities. The dataBlob is just an arbitrary blob of data. At
construction an extractor to get the interesting information was defined
(or the default was used).
The rowIdentities is a 2D array of identifiers for rows.
@@ -32,13 +32,13 @@ assumed that the keys of the section data are the row identities.
Note: Th
passes the functions defined at construction to a new data source with
the data specified. If you wish to maintain the existing data you must
handle merging of old and new data separately and then pass that into
-this function as the dataBlob.
This performs the same function as the cloneWithRows function but here
you also specify what your sectionIdentities are. If you don't care
about sections you should safely be able to use cloneWithRows.
sectionIdentities is an array of identifiers for sections.
ie. ['s1', 's2', ...]. If not provided, it's assumed that the
-keys of dataBlob are the section identities.
Determines the type of background drawable that's going to be used to
display feedback. It takes an object with type property and extra data
depending on the type. It's recommended to use one of the static
-methods to generate that dictionary.
Creates an object that represent android theme's default background for borderless
selectable elements (?android:attr/selectableItemBackgroundBorderless).
-Available on android API level 21+.
Creates an object that represents ripple drawable with specified color (as a
string). If property borderless evaluates to true the ripple will
render outside of the view bounds (see native actionbar buttons as an
example of that behavior). This background type is available on Android
diff --git a/releases/next/docs/touchableopacity.html b/releases/next/docs/touchableopacity.html
index ab5fd6d8757..15e6b1db1fa 100644
--- a/releases/next/docs/touchableopacity.html
+++ b/releases/next/docs/touchableopacity.html
@@ -11,7 +11,7 @@ easy to add to an app without weird side-effects.
NOTE: VibrationIOS is being deprecated. Use Vibration instead.
The Vibration API is exposed at VibrationIOS.vibrate(). On iOS, calling this
function will trigger a one second vibration. The vibration is asynchronous
so this method will return immediately.
There will be no effect on devices that do not support Vibration, eg. the iOS
-simulator.
'use strict';var React =require('react');var ReactNative =require('react-native');
diff --git a/releases/next/docs/viewpagerandroid.html b/releases/next/docs/viewpagerandroid.html
index 0d1642eaa98..ede06ad1366 100644
--- a/releases/next/docs/viewpagerandroid.html
+++ b/releases/next/docs/viewpagerandroid.html
@@ -44,8 +44,8 @@ The page scrolling state can be in 3 states:
callback will have following fields:
- position - index of page that has been selected
Function that allows custom handling of any web view requests. Return
true from the function to continue loading the request and false
to stop loading.