From 1b2ba83d4f49ec523d4e5c64179dc33b4e7b79ce Mon Sep 17 00:00:00 2001 From: Website Deployment Script Date: Thu, 9 Mar 2017 20:57:31 +0000 Subject: [PATCH] Updated docs for next --- releases/next/docs/scrollview.html | 2 +- releases/next/docs/troubleshooting.html | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/releases/next/docs/scrollview.html b/releases/next/docs/scrollview.html index 61b6fd82330..4ddde8ecb55 100644 --- a/releases/next/docs/scrollview.html +++ b/releases/next/docs/scrollview.html @@ -107,7 +107,7 @@ top of the screen when scrolling. For example, passing stickyHeaderIndices={[0]} will cause the first child to be fixed to the top of the scroll view. This property is not supported in conjunction with horizontal={true}.

ioszoomScale?: number #

The current scale of the scroll view content. The default value is 1.0.

Methods #

scrollTo(y?: number, object, x?: number, animated?: boolean) #

Scrolls to a given x, y offset, either immediately or with a smooth animation.

Example:

scrollTo({x: 0; y: 0; animated: true})

Note: The weird function signature is due to the fact that, for historical reasons, -the function also accepts separate arguments as as alternative to the options object. +the function also accepts separate arguments as an alternative to the options object. This is deprecated due to ambiguity (y before x), and SHOULD NOT BE USED.

scrollToEnd(options?: object) #

If this is a vertical ScrollView scrolls to the bottom. If this is a horizontal ScrollView scrolls to the right.

Use scrollToEnd({animated: true}) for smooth animated scrolling, scrollToEnd({animated: false}) for immediate scrolling. diff --git a/releases/next/docs/troubleshooting.html b/releases/next/docs/troubleshooting.html index c124920bfbf..bacd5a81567 100644 --- a/releases/next/docs/troubleshooting.html +++ b/releases/next/docs/troubleshooting.html @@ -6,7 +6,7 @@ sudo chown -R $USER 'RCTWebSocket', ]

Next, make sure you have run pod install and that a Pods/ directory has been created in your project with React installed. CocoaPods will instruct you to use the generated .xcworkspace file henceforth to be able to use these installed dependencies.

Argument list too long: recursive header expansion failed #

In the project's build settings, User Search Header Paths and Header Search Paths are two configs that specify where Xcode should look for #import header files specified in the code. For Pods, CocoaPods uses a default array of specific folders to look in. Verify that this particular config is not overwritten, and that none of the folders configured are too large. If one of the folders is a large folder, Xcode will attempt to recursively search the entire directory and throw above error at some point.

To revert the User Search Header Paths and Header Search Paths build settings to their defaults set by CocoaPods - select the entry in the Build Settings panel, and hit delete. It will remove the custom override and return to the CocoaPod defaults.

No transports available #

React Native implements a polyfill for WebSockets. These polyfills are initialized as part of the react-native module that you include in your application through import React from 'react'. If you load another module that requires WebSockets, such as Firebase, be sure to load/require it after react-native:

import React from 'react'; import Firebase from 'firebase';

Shell Command Unresponsive Exception #

If you encounter a ShellCommandUnresponsiveException exception such as:

Execution failed for task ':app:installDebug'. - com.android.builder.testing.api.DeviceException: com.android.ddmlib.ShellCommandUnresponsiveException

Try downgrading your Gradle version to 1.2.3 in android/build.gradle.

react-native init hangs #

If you run into issues where running react-native init hangs in your system, try running it again in verbose mode and refering to #2797 for common causes:

react-native init --verbose

You can edit the content above on GitHub and send us a pull request!