Android crash while navigating back to stack screen .

Oath

I swear that I have completed these tasks before submitting:

• I have read the contribution guidelines here: https://git.io/JJ0Pg
• I have read the documentation here: https://git.io/JJcAl
• I have confirmed that this bug has not been reported yet

Decision table

• My issue does not look like “The HTML attribute ‘xxx’ is ignored” (unless we claim support for it),
• My issue does not look like “The HTML element <yyy> is not rendered”

Bug Report

07-29 17:41:49.173  6901  6901 F crashpad: dlopen: dlopen failed: library "libandroidicu.so" not found: needed by /system/lib/libharfbuzz_ng.so in namespace (default)
--------- beginning of crash
07-29 17:41:49.176  6410  6441 F libc    : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x1c in tid 6441 (RenderThread), pid 6410 (com.newmednav)
07-29 17:41:49.340  6904  6904 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
07-29 17:41:49.340  6904  6904 F DEBUG   : Build fingerprint: 'google/sdk_gphone_x86_arm/generic_x86_arm:11/RPB2.200611.009/6625208:userdebug/dev-keys'
07-29 17:41:49.340  6904  6904 F DEBUG   : Revision: '0'
07-29 17:41:49.340  6904  6904 F DEBUG   : ABI: 'x86'
07-29 17:41:49.340  6904  6904 F DEBUG   : Timestamp: 2020-07-29 17:41:49+0545
07-29 17:41:49.340  6904  6904 F DEBUG   : pid: 6410, tid: 6441, name: RenderThread  >>> com.newmednav <<<
07-29 17:41:49.340  6904  6904 F DEBUG   : uid: 10152
07-29 17:41:49.340  6904  6904 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x1c
07-29 17:41:49.340  6904  6904 F DEBUG   : Cause: null pointer dereference
07-29 17:41:49.340  6904  6904 F DEBUG   :     eax efbc2cb0  ebx eed5c69c  ecx eed52a80  edx 00000000
07-29 17:41:49.341  6904  6904 F DEBUG   :     edi d139ae90  esi 00000000
07-29 17:41:49.341  6904  6904 F DEBUG   :     ebp c086ed48  esp c086eb50  eip ee698c1c
07-29 17:41:49.425  6904  6904 F DEBUG   : backtrace:
07-29 17:41:49.425  6904  6904 F DEBUG   :       #00 pc 00247c1c  /system/lib/libhwui.so (android::uirenderer::skiapipeline::GLFunctorDrawable::onDraw(SkCanvas*)+1548) (BuildId: 434a9b68672e1dd2b15599730362463d)
07-29 17:41:49.425  6904  6904 F DEBUG   :       #01 pc 00303a57  /system/lib/libhwui.so (SkDrawable::draw(SkCanvas*, SkMatrix const*)+87) (BuildId: 434a9b68672e1dd2b15599730362463d)
07-29 17:41:49.425  6904  6904 F DEBUG   :       #02 pc 002f4606  /system/lib/libhwui.so (SkBaseDevice::drawDrawable(SkDrawable*, SkMatrix const*, SkCanvas*)+38) (BuildId: 434a9b68672e1dd2b15599730362463d)
07-29 17:41:49.425  6904  6904 F DEBUG   :       #03 pc 00659291  /system/lib/libhwui.so (SkGpuDevice::drawDrawable(SkDrawable*, SkMatrix const*, SkCanvas*)+353) (BuildId: 434a9b68672e1dd2b15599730362463d)
07-29 17:41:49.425  6904  6904 F DEBUG   :       #04 pc 002d9dc0  /system/lib/libhwui.so (SkCanvas::onDrawDrawable(SkDrawable*, SkMatrix const*)+48) (BuildId: 434a9b68672e1dd2b15599730362463d)

React Native

0.61.5

Libraries

• react-native-render-html: 4.2.2
• react-native-webview: 10.3.2
• react-native-screens: 2.8.0
• react-native-render-html-table-bridge: ^0.6.1,

Devices

• Device 1 emulator (Google Pixel 3a)
  • OS: Android 10.0
  • Environment: both

Description

1.Android app crashes while navigating back to stack screen after rendering table content and embedded videos from youtube. 2.Normal behavior when rendering normal html content 3.No crashes while disable {enableScreen } from react-native-screens

[marco2216]

The current equivalent to this solution, assuming you’re using @native-html/iframe-plugin, is as follows (optionally check if is android when applying this):

renderersProps={{
  iframe: {
    webViewProps: {
      style: { opacity: 0.99 },
    },
  },
}}

[jsamr]

@drb1 First of all, congratulations on the reproduction. That is pristine! So I did my little investigation, and this is what I found out:

• Some Android developers have reported that this native error can be worked around by disabling hardware acceleration, but eventually at the cost of lower performance (that part is to be verified yet), according to the documentation.

diff --git a/android/app/src/main/AndroidManifest.xml b/android/app/src/main/AndroidManifest.xml
index 433c7e2..c569e8f 100644
--- a/android/app/src/main/AndroidManifest.xml
+++ b/android/app/src/main/AndroidManifest.xml
@@ -15,6 +15,7 @@
         android:label="@string/app_name"
         android:configChanges="keyboard|keyboardHidden|orientation|screenSize|uiMode"
         android:launchMode="singleTask"
+        android:hardwareAccelerated="false"
         android:windowSoftInputMode="adjustResize">
         <intent-filter>
             <action android:name="android.intent.action.MAIN" />

Indeed, after disabling hardware acceleration, the app doesn’t crash anymore.

• A number of react-native-screens users have experienced the same issue (https://github.com/software-mansion/react-native-screens/issues/105 and https://github.com/software-mansion/react-native-screens/issues/214). Some claim it happens with react-native-webview, and relates to https://github.com/react-native-community/react-native-webview/issues/1069. This is obviously an upstream bug, and we will track it until it is fixed.