Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v13.2.2 update #4

Merged
merged 303 commits into from
Jul 19, 2023
Merged

v13.2.2 update #4

merged 303 commits into from
Jul 19, 2023

Conversation

berkayatasoy
Copy link

No description provided.

hchokshi and others added 30 commits November 7, 2020 00:05
## [10.10.2](react-native-webview/react-native-webview@v10.10.1...v10.10.2) (2020-11-06)

### Bug Fixes

* **android:** Unset mWebChromeClient on WebViewManager rather than WebView ([react-native-webview#1720](react-native-webview#1720)) ([c95c0ea](react-native-webview@c95c0ea))
…20-6506 (react-native-webview#1747 by @mrcoinbase and @kelset -- THANK YOU!)

BREAKING CHANGE:

This release introduces the `setSupportMultipleWindows` prop for Android. This sets the underlying Android WebView setting `setSupportMultipleWindows`. This prop defaults to `true` (previously `false`), and serves to mitigate the security advisory [CVE-2020-6506](GHSA-36j3-xxf7-4pqg).

The primary way this new behavior changes existing React Native WebView implementations on Android is that links that open in new tabs/windows (such as `<a target="_blank">`) will now prompt to open in the system browser, rather than re-using the current WebView.

If this behavior is not desirable, you can set this new prop to `false`, but be aware that this exposes your app to the security vulnerability listed above. Make sure you have read and understand the whole advisory and relevant links.

iOS & Windows are unaffected.

```jsx
<WebView
  // ...
  setSupportMultipleWindows={true} // default: true
/>
```

Thanks to @mrcoinbase, @kelset, and @Titozzz for their work on this.
# [11.0.0](react-native-webview/react-native-webview@v10.10.2...v11.0.0) (2020-11-24)

### Features

* **android:** Introduce setSupportMultipleWindows to mitigate CVE-2020-6506 ([react-native-webview#1747](react-native-webview#1747) by [@mrcoinbase](https://github.com/mrcoinbase) and [@kelset](https://github.com/kelset) -- THANK YOU!) ([194c6a2](react-native-webview@194c6a2))

### BREAKING CHANGES

* **android:** This release introduces the `setSupportMultipleWindows` prop for Android. This sets the underlying Android WebView setting `setSupportMultipleWindows`. This prop defaults to `true` (previously `false`), and serves to mitigate the security advisory [CVE-2020-6506](GHSA-36j3-xxf7-4pqg).

The primary way this new behavior changes existing React Native WebView implementations on Android is that links that open in new tabs/windows (such as `<a target="_blank">`) will now prompt to open in the system browser, rather than re-using the current WebView.

If this behavior is not desirable, you can set this new prop to `false`, but be aware that this exposes your app to the security vulnerability listed above. Make sure you have read and understand the whole advisory and relevant links.

iOS & Windows are unaffected.

```jsx
<WebView
  // ...
  setSupportMultipleWindows={true} // default: true
/>
```

Thanks to @mrcoinbase, @kelset, and @Titozzz for their work on this.
* Fix onScroll event type

* Update documentation

* Address PR feedback
## [11.0.2](react-native-webview/react-native-webview@v11.0.1...v11.0.2) (2020-12-08)

### Bug Fixes

* **android:** changed initial value of nextLockIdentifier from 0 to 1 ([react-native-webview#1689](react-native-webview#1689)) ([53c0382](react-native-webview@53c0382))
Updates ReactWebViewClient to RNCWebViewClient
…native-webview#1077)

* fix:iOS13  scrollView.automaticallyAdjustsScrollIndicatorInsets default value YES which make the webview vertical indicator position in wrong offset

* added types and doc

Co-authored-by: BillHsieh <[email protected]>
Co-authored-by: xietian <[email protected]>
Co-authored-by: Thibault Malbranche <[email protected]>
Co-authored-by: Thibault Malbranche <[email protected]>
…tive-webview#1730)

* Added allowUniversalAccessFromFileURLs property to iOS and macOS
Updated the types to include allowUniversalAccessFromFileURLs and allowFileAccessFromFileURLs for iOS and macOS
Updated the Reference.md to include in the allowUniversalAccessFromFileURLs section iOS and macOS

* Updated platform in the type definition
* fix:iOS13  scrollView.automaticallyAdjustsScrollIndicatorInsets default value YES which make the webview vertical indicator position in wrong offset

* added types and doc

* fix: breaking bug for props not include under iOS13

Co-authored-by: BillHsieh <[email protected]>
Co-authored-by: xietian <[email protected]>
Co-authored-by: Thibault Malbranche <[email protected]>
Co-authored-by: Thibault Malbranche <[email protected]>
…iew#1768)

* Upgrade react-native-windows to 0.63.11

* Downgrade to 0.62.17
)

* iOS cookie available for resource requests

* Missig brace added

Co-authored-by: niwani <[email protected]>
TheKohan and others added 29 commits April 6, 2023 11:54
## [12.0.3](react-native-webview/react-native-webview@v12.0.2...v12.0.3) (2023-05-22)

### Bug Fixes

* **Android:** Don't crash while downloading file with % in filename ([react-native-webview#2861](react-native-webview#2861)) ([81e3aa4](react-native-webview@81e3aa4))
…eact-native-webview#2952)

We (Microsoft Office apps) are seeing the following crashes in certain OEMs (biased toward Samsung)
Exception java.lang.RuntimeException: Unable to get provider com.reactnativecommunity.webview.RNCWebViewFileProvider: java.lang.IllegalArgumentException: Missing android.support.FILE_PROVIDER_PATHS meta-data
  at android.app.ActivityThread.installProvider (ActivityThread.java:6840)
  at android.app.ActivityThread.installContentProviders (ActivityThread.java:6382)
  at android.app.ActivityThread.handleBindApplication (ActivityThread.java:6286)
  ...
Caused by java.lang.IllegalArgumentException: Missing android.support.FILE_PROVIDER_PATHS meta-data
  at androidx.core.content.FileProvider.d
  at androidx.core.content.FileProvider.h
  at androidx.core.content.FileProvider.e
  at androidx.core.content.FileProvider.attachInfoMAM
  ..

Upon further investigation, we found the hypothesis that some OEMs strip meta-data from the manifest (though we don't have any solid data to confirm).

This discussion is related : https://issuetracker.google.com/issues/237727754?pli=1
And this commit into AOSP : https://android-review.googlesource.com/c/platform/frameworks/support/+/1978527
…ve-webview#2897)

* [windows] Support headers and cookies in source prop

* minor fixes
## [12.2.1](react-native-webview/react-native-webview@v12.2.0...v12.2.1) (2023-06-10)

### Bug Fixes

* Revert "Missing android.support.FILE_PROVIDER_PATHS meta-data on some OEMs ([react-native-webview#2952](react-native-webview#2952))" ([e17a79b](react-native-webview@e17a79b))
…iew#2993)

* Update RNCWebView.java

* Update RNCWebView.java

* wip

* wip

* fix build on latest xcode

* add example + fix a few things

* Update RNCWebViewImpl.m

* fix macOS build
* feat: add webviewDebuggingEnabled prop & Android implementation

fix: use static RNCWebView.setWebContentsDebuggingEnabled

* feat: add iOS webviewDebuggingEnabled prop

* chore: remove "link generted with jump2header" comments

* chore: add missing props-index links in Reference.md

* feat: add webviewDebuggingEnabled reference docs

* fix: surround inspectable code blocks with compiler preprocessor to include only on appropriate versions


---------

Co-authored-by: Tom Bury <[email protected]>
)

BREAKING CHANGE: This affects an existing loading behavior so we marked it as breaking, just in case

Co-authored-by: Peter Lazar <[email protected]>
Co-authored-by: Thibault Malbranche <[email protected]>
# [13.0.0](react-native-webview/react-native-webview@v12.4.0...v13.0.0) (2023-06-10)

### Features

* Allow webview to load in background tab ([react-native-webview#2930](react-native-webview#2930)) ([40c9807](react-native-webview@40c9807))

### BREAKING CHANGES

* This affects an existing loading behavior so we marked it as breaking, just in case

Co-authored-by: Peter Lazar <[email protected]>
Co-authored-by: Thibault Malbranche <[email protected]>
…e-webview#2801) (react-native-webview#2994)

* feat: fraudulentWebsiteWarningEnabled
* chore: test new arch on CI

# Conflicts:
#	docs/Reference.md

* fix: missing type

* feat: add ios13 check

* Update src/WebViewTypes.ts

Co-authored-by: Caleb Clarke <[email protected]>

* Update docs/Reference.md

Co-authored-by: Caleb Clarke <[email protected]>

* implem adaptation

* Update ios-ci.yml

* Update ios-ci.yml

* Update android-ci.yml

* Update ios-ci.yml

* fix android new arch

* Update ios-ci.yml

---------

Co-authored-by: sunnylqm <[email protected]>
Co-authored-by: Caleb Clarke <[email protected]>
# Conflicts:
#	README.md
#	android/src/main/java/com/reactnativecommunity/webview/RNCWebViewManager.java
#	apple/RNCWebView.h
#	apple/RNCWebView.m
#	apple/RNCWebViewManager.m
#	src/WebViewTypes.ts
@berkayatasoy berkayatasoy merged commit cdecd91 into master Jul 19, 2023
2 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.