Issue metadata
Sign in to add a comment
|
Android System Webview update causes ReactNative WebView to hang/fail
Reported by
br...@pukkasoft.com,
Apr 7 2017
|
||||||||||||||||||||||
Issue descriptionDevice name: Various Android phones and tablets (5.1, 6.0, 7.0, 7.1) From "Settings > About Chrome" Application version: Android System Webview: 57.0.2987.132 Operating system: Android URLs (if applicable): Steps to reproduce: (1) Update to Android System Webview 57.0.2987.126 or .132 (2) App no longer successfully responds to a tap which should render a WebView in ReactNative app (3) Expected result: The RaceHero app (https://play.google.com/store/apps/details?id=com.racehero_mobile&hl=en) is a wrapper for https://racehero.io/events. What should happen when tapping the "BMW" event in the attached video is a small loader animation plays (which is the flickering it appears) and then the app would load a WebView for https://racehero.io/events/bmw-virginia-intl-raceway-2017. Actual result: Instead of loading the event, it flickers, fails in some way and stays on the list screen. The attached video is short but shows how the tap fails to load the event screen and stays on the list screen. This worked prior to the most recent Android System Webview release.
,
Apr 7 2017
Hello Thanks for reporting the issue. Issue is reproducible on 57.0.2987.132.
,
Apr 7 2017
,
Apr 7 2017
Issue is also being tracked at Titanium Appcelerator: https://jira.appcelerator.org/browse/TIMOB-24540
,
Apr 13 2017
From the log, every time it repros: 04-13 18:43:24.743 6887 6887 W cr_BindingManager: Cannot call determinedVisibility() - never saw a connection for the pid: 6887 04-13 18:43:24.793 861 1462 I WindowManager: Destroying surface Surface(name=com.racehero_mobile/com.racehero_mobile.MainActivity) called by ... I'll wait for bisect.
,
Apr 13 2017
determinedVisibility happens one happens on every time webview launches in single process mode, and it's a meaningless message for single process anyway
,
Apr 13 2017
anyone on test team working on bisect?
,
Apr 14 2017
boliu@: Not yet. We will work on it & update soon.
,
Apr 14 2017
I will bisect this and update asap. Thanks.
,
Apr 14 2017
Bisect Range: https://chromium.googlesource.com/chromium/src/+log/57.0.2959.0..57.0.2960.0?pretty=fuller&n=10000 Last good build: 57.0.2959.0 First broken build: 57.0.2960.0 I tried to bisect by CL on Nexus6/MOB31V with AOSP build, but the app does not render. I'm trying to bisect using N device and will comment here if I can narrow down to a CL.
,
Apr 14 2017
Could not bisect by CL as the app does not render even on device with Android N/AOSP build.
,
Jun 12 2017
Brian, on what device do you reproduce this for Android L/M/N? Given that this is a regression in 57 which shipped quite a while ago, I'm marking this as P3.
,
Jun 12 2017
,
Jun 12 2017
My personal Android device is an older Moto G (Android 5.1, latest patch level 2016-03-01) but my colleague reproduced it on his phone. I had verifiable reports, in addition to my phone, on: Android 7 (2017-03-01 security) Android 6 (2016-08-1 security) We have changed our ReactNative app to use a different approach to the webview so this is not happening in the latest version of our app in the app store but as far as we're aware, the issue above is still happening.
,
Jun 13 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 13 2018
If the current version of the app no longer repros, then it would be difficult to debug this. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by br...@pukkasoft.com
, Apr 7 2017