## [8.0.6](https://github.com/react-native-community/react-native-webview/compare/v8.0.5...v8.0.6) (2020-01-30)

### Bug Fixes

* **Android:** Revert "Redirected URLs now redirect correctly. ([#991](https://github.com/react-native-community/react-native-webview/issues/991))" ([#1177](https://github.com/react-native-community/react-native-webview/issues/1177)) ([344aab5](https://github.com/react-native-community/react-native-webview/commit/344aab5))

This reverts commit acf1ad7560.

## [8.0.5](https://github.com/react-native-community/react-native-webview/compare/v8.0.4...v8.0.5) (2020-01-26)

### Bug Fixes

* **Android:** Redirected URLs now redirect correctly. ([#991](https://github.com/react-native-community/react-native-webview/issues/991)) ([acf1ad7](https://github.com/react-native-community/react-native-webview/commit/acf1ad7))

Co-authored-by: Jamon Holmgren <jamon@infinite.red>
Co-authored-by: Jason Safaiyeh <safaiyeh@protonmail.com>

## [8.0.4](https://github.com/react-native-community/react-native-webview/compare/v8.0.3...v8.0.4) (2020-01-20)

### Bug Fixes

* **iOS:** Meta method 'UIScrollViewContentInsetAdjustmentBehavior:' conflict warning ([e6edc6d](https://github.com/react-native-community/react-native-webview/commit/e6edc6d)), closes [/github.com/facebook/react-native/blob/master/React/Views/ScrollView/RCTScrollViewManager.m#L40](https://github.com//github.com/facebook/react-native/blob/master/React/Views/ScrollView/RCTScrollViewManager.m/issues/L40)

This converter is already defined in
[RCTScrollViewManager.m](https://github.com/facebook/react-native/blob/master/React/Views/ScrollView/RCTScrollViewManager.m#L40).

Redefining it in react-native-webview can cause undefined behaviour when
used. Since ScrollView is unlikely to go away, we can take a dependency on it.

All current tests should pass.

When building a React Native app with `react-native-webview`, the following
warning can be seen in the build logs:

```
Meta method 'UIScrollViewContentInsetAdjustmentBehavior:' in category from /~/Library/Developer/Xcode/DerivedData/App-geojljebaazfrrgvxfkjjpiwmdlg/Build/Products/Debug-iphonesimulator/React-Core/libReact-Core.a(RCTScrollViewManager.o) conflicts with same method from another category
```

The warning should go away after removing the offending function.

Co-authored-by: Jason Safaiyeh <safaiyeh@protonmail.com>

## [8.0.3](https://github.com/react-native-community/react-native-webview/compare/v8.0.2...v8.0.3) (2020-01-08)

### Bug Fixes

* **whitelisted origins:** Prevent handling of un-whitelisted URLs ([0442126](https://github.com/react-native-community/react-native-webview/commit/0442126))

* Preventing an unhandled promise rejection when: a URL is loaded by the WebView, but the URL isn't in the origin whitelist, so it is handed off to the OS to handle by calling Linking.openURL(), but Linking.openURL has an error.  The code wasn't catching the error, so this would result in an unhandled promise rejection. Now the error is being caught.

* Fixing a problem where a URL is handled to the OS to deal with, via Linking.openURL, and also loaded in the WebView by making those cases mutually exclusive (they weren't previously).  In more detail: when a URL is loaded by the WebView that isn't in the origin whitelist it is handled off to the OS to handle by calling Linking.openURL.  But, if the onShouldStartLoadWithRequest prop is set, then that function would also be called, and then that would determine whether the URL should be loaded.  This can result in a situation where the URL is passed to Linking.openURL and onShouldStartLoadWithRequest returns true so it is also loaded in the WebView.  The client can fix this by duplicating the origin whitelist logic in their onShouldStartLoadWithRequest of course, but this change makes it so they don't have to.

Co-authored-by: Jason Safaiyeh <safaiyeh@protonmail.com>

* docs: add Lean core badge

* docs: adjust badge style