expo: android 5.1.1 and simulator, WebView error on SDK36 and Exponent_2.14

Expo CLI 3.4.1 environment info: System: OS: Windows 10 Binaries: Yarn: 1.19.1 - C:\Users\Administrator\AppData\Roaming\npm\yarn.CMD npm: 6.9.0 - D:\Program Files\nodejs\npm.CMD

Android: real device: V5.1.1, simulator(nox): V5.1.1500190725 expo Client: 2.14.0 SDK: 36 error happen on expo client and standalone android

note: webview working fine on SDK 35 and expo client 2.13 only, 2.14 will shows String resource ID #0x2040003 on real device.

Steps to Reproduce

  1. expo upgrade
  2. change WebView from ‘react-native’ to ‘react-native-WebView’
  3. yarn start
  4. enter Webview Page, error happen

Expected Behavior

It should render a webview page.

Actual Behavior

On my android simulator(nox), which is android V5.1.1500190725, it will shows net::ERR_CACHE_MISS.
I found this open issue on react-native-webview, https://github.com/react-native-community/react-native-webview/issues/1101 and still waiting reply. Then I tried to run on my real device, the error becomes String resource ID #0x2040003

IMG_20200103_103038 IMG_20200103_103108

After I search the 0x2040003 error on google, it seems like this is a common issue on android V5.1.1 with context, however for some reasons, I have to use V5.1.1.

I downgrade my sdk to 35, and it shows same error, until I reinstall expo client 2.13, WebView works fine.

Reproducible Demo

<WebView source={{ uri: 'google.com', }} onNavigationStateChange={this.onNavigationStateChange} startInLoadingState // scalesPageToFit javaScriptEnabled style={{ flex: 1, paddingTop: StatusBar.currentHeight }} />

Thank you!

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 18 (7 by maintainers)

Commits related to this issue

Most upvoted comments

It looks like 1.2.0 came out of alpha yesterday. Any ideas when this will be folded into Expo?

https://developer.android.com/jetpack/androidx/releases/core

@brentvatne Okay so we need to wait for react-native-webview to do something (after more than 2 years?) … I guess I will inform the client that Android 5.x can’t be maintained.