Add workaround for bug in Linking.getInitialUrl

Author: satya164

website/versioned_docs/version-5.x/deep-linking.md

@@ -52,8 +52,17 @@ function App() {
   const [initialState, setInitialState] = React.useState();
 
   React.useEffect(() => {
-    getInitialState()
-      .catch(() => {})
+    Promise.race(
+      getInitialState(),
+      new Promise(resolve =>
+        // Timeout in 150ms if `getInitialState` doesn't resolve
+        // Workaround for https://github.com/facebook/react-native/issues/25675
+        setTimeout(resolve, 150)
+      )
+    )
+      .catch(e => {
+        console.error(e);
+      })
       .then(state => {
         if (state !== undefined) {
           setInitialState(state);
@@ -75,6 +84,8 @@ function App() {
 }
 ```
 
+> Note: The `getInitialState` function uses React Native's `Linking.getInitialUrl()` under the hood. Currently there seems to be bug ([facebook/react-native#25675](https://github.com/facebook/react-native/issues/25675)) which results in it never resolving on Android.
+
 Often, directly translating path segments to route names may not be the expected behavior. For example, you might want to parse the path `/feed/latest` to something like:
 
 ```js