Update troubleshooting docs

Author: satya164

website/versioned_docs/version-4.x/troubleshooting.md

@@ -7,6 +7,8 @@ original_id: troubleshooting
 
 This section attempts to outline issues that can happen during setup and may not be related to React Navigation itself. Also see [common mistakes](common-mistakes.md).
 
+Before troubleshooting an issue, make sure that you have upgraded to **the latest available versions** of the packages. You can install the latest versions by installing the packages again (e.g. `npm install package-name`).
+
 ## I'm getting an error "Unable to resolve module" after updating to the latest version
 
 This might happen for 2 reasons:
@@ -25,7 +27,7 @@ expo start -c
 If you're not using Expo, run:
 
 ```sh
-react-native start --reset-cache
+npx react-native start --reset-cache
 ```
 
 If the module points to an npm package (i.e. the name of the module doesn't with `./`), then it's probably due to a missing peer dependency. To fix this, install the dependency in your project:
@@ -62,7 +64,45 @@ This and some similar errors might occur if you didn't link the [`react-native-g
 
 Now rebuild the app and test on your device or simulator.
 
-## I linked RNGestureHandler library but gestures won't work on Android
+## I'm getting an error "TypeError: Cannot read property 'bind' of undefined" or "TypeError: propListener.apply is not a function"
+
+This error can often happen if you have a Babel plugin that compiles the code in a non-spec compliant way. For example:
+
+```sh
+["@babel/plugin-proposal-class-properties", { "loose": true}]
+```
+
+The above compiles class properties in `loose` mode, which is not spec compliant. To prevent such issues, avoid using any additional Babel plugins or presets which change the way Metro compiles code by default. Your `babel.config.js` should look like this:
+
+```js
+module.exports = {
+  presets: ['module:metro-react-native-babel-preset'],
+};
+```
+
+Or if you're using Expo:
+
+```js
+module.exports = {
+  presets: ['babel-preset-expo'],
+};
+```
+
+If you have additional options configured here, try removing them to see if it fixes the issue. After changing config, always clear the cache.
+
+If you're using Expo, run:
+
+```sh
+expo start -c
+```
+
+If you're not using Expo, run:
+
+```sh
+npx react-native start --reset-cache
+```
+
+## I linked `react-native-gesture-handler` library but gestures won't work on Android
 
 This might happen if you didn't update your MainActivity.java file (or wherever you create an instance of ReactActivityDelegate), so that it uses the root view wrapper provided by this library.
 

website/versioned_docs/version-5.x/hello-react-navigation.md

@@ -134,7 +134,7 @@ Sometimes we might want to pass additional props to a screen. We can do that wit
    </Stack.Screen>
    ```
 
-> Note: By default, React Navigation applies optimizations to screen components to prevent unnecessary renders. Using a render callback removes those optimizations. So if you use a render callback, you'll need to ensure that you use [`React.memo`](https://reactjs.org/docs/react-api.html#reactmemo) or [`React.PureComponent`](https://reactjs.org/docs/react-api.html#reactpurecomponent) for your screen components to prevent avoid performance issues.
+> Note: By default, React Navigation applies optimizations to screen components to prevent unnecessary renders. Using a render callback removes those optimizations. So if you use a render callback, you'll need to ensure that you use [`React.memo`](https://reactjs.org/docs/react-api.html#reactmemo) or [`React.PureComponent`](https://reactjs.org/docs/react-api.html#reactpurecomponent) for your screen components to avoid performance issues.
 
 ## What's next?
 

website/versioned_docs/version-5.x/troubleshooting.md

@@ -7,6 +7,8 @@ original_id: troubleshooting
 
 This section attempts to outline issues that users frequently encounter when first getting accustomed to using React Navigation. These issues may or may not be related to React Navigation itself.
 
+Before troubleshooting an issue, make sure that you have upgraded to **the latest available versions** of the packages. You can install the latest versions by installing the packages again (e.g. `npm install package-name`).
+
 ## I'm getting an error "Unable to resolve module" after updating to the latest version
 
 This might happen for 2 reasons:
@@ -67,17 +69,13 @@ react-native unlink react-native-gesture-handler
 If you're testing on iOS and use Mac, make sure you have run `pod install` in the `ios/` folder:
 
 ```sh
-cd ios; pod install; cd ..
+cd ios
+pod install
+cd ..
 ```
 
 Now rebuild the app and test on your device or simulator.
 
-## I linked RNGestureHandler library but gestures won't work on Android
-
-This might happen if you didn't update your MainActivity.java file (or wherever you create an instance of ReactActivityDelegate), so that it uses the root view wrapper provided by this library.
-
-Check how to do it [here](https://software-mansion.github.io/react-native-gesture-handler/docs/getting-started.html).
-
 ## Pressing buttons don't do anything
 
 Make sure you're not connected to Chrome Debugger. When connected to Chrome Debugger, you might encounter various issues related to timing, such as button presses and animations not working correctly.