Crash on android if get back on navigation with table
See original GitHub issueOath
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
- [x ] My issue does not look like “The HTML attribute ‘xxx’ is ignored” (unless we claim support for it),
- [ x] My issue does not look like “The HTML element
<yyy>
is not rendered”
Bug Report
Setup
React Native
System:
OS: macOS 11.0.1
CPU: (8) x64 Intel(R) Core(TM) i5-8257U CPU @ 1.40GHz
Memory: 24.70 MB / 8.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 12.18.3 - /usr/local/bin/node
Yarn: Not Found
npm: 6.14.6 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.9.3 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 14.2, DriverKit 20.0, macOS 11.0, tvOS 14.2, watchOS 7.1
Android SDK:
API Levels: 29, 30
Build Tools: 28.0.3, 29.0.2, 30.0.3
System Images: android-30 | Google APIs Intel x86 Atom
Android NDK: Not Found
IDEs:
Android Studio: 4.1 AI-201.8743.12.41.7199119
Xcode: 12.2/12B45b - /usr/bin/xcodebuild
Languages:
Java: 1.8.0_282 - /usr/bin/javac
Python: 2.7.16 - /usr/bin/python
npmPackages:
@react-native-community/cli: Not Found
react: 16.13.1 => 16.13.1
react-native: 0.63.4 => 0.63.4
react-native-macos: Not Found
npmGlobalPackages:
*react-native*: Not Found
Libraries
- react-native-render-html: 5.1.0
- react-native-webview: 11.4.4
- react-native-screens: 3.2.0
- @react-navigation/stack@5.14.5
- @react-navigation/drawer@5.12.5
- @react-navigation/native@5.9.4
Devices
- Device 1 Xiaomi mi 8
- OS: Android 10
- Diagnostic:
- Environment:
Reproduction
render html with given code a<br/>a<br/>a<br/>a<br/>a<br/>a<br/>a<br/>a<br/>a<br/>a<br/>a<br/>a<br/>a<br/>a<br/>a<br/>a<br/>a<br/>a<br/>a<br/>a<br/>a<br/>a<br/>a<br/>a<br/>a<br/><table><tr><td>123123</td></tr></table>
swipe left on react-navigation it will crash #393
I’ve tried many ways like set opacity for table to 0.99 but it doesn’t work (https://stackoverflow.com/questions/63171131/when-rendering-iframes-with-html-android-crashes-while-navigating-back-to-s/63171413#63171413)
the only way to work around is set animationEnabled: false
Issue Analytics
- State:
- Created 2 years ago
- Comments:7
Top Results From Across the Web
App crash by "back" to maps fragment - android - Stack Overflow
The cause for the issue is, whenever onCreateView() for that fragment is called, the xml file will be inflated which will inflate the...
Read more >Fix an Android device that freezes or won't respond
Try the following steps if your phone: Freezes Stops responding Is stuck with the screen on After each step, restart your phone to...
Read more >Here's how to fix constant app crashes in Android 12 beta
If you're seeing constant app crashes on Android 12, just go to the Settings menu, tap Apps, All apps, then scroll down to...
Read more >Inspect GPU rendering speed and overdraw
If this segment is large, it could indicate that a custom animator or input callback is spending too much time processing. View binding...
Read more ><uses-sdk> | Android Developers
If the application were to be somehow installed on a platform with a lower API Level, then it would crash at run-time when...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’ve reported the issue here: https://github.com/react-navigation/react-navigation/issues/9755
Not much more I can do, hopefully it will be fixed upstream at some point.
In the meantime, you can check workarounds proposed in this StackOverflow post.
I am closing because this issue has to be fixed upstream and workarounds have been provided.