New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 770461 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug


Show other hotlists

Hotlists containing this issue:
Hotlist-1


Sign in to add a comment

Android System WebView 61.0.3163.98 (20-sep) Broke HTML5 App on several devices (Not All)

Reported by mma...@gmail.com, Sep 30 2017

Issue description

We are the developers for Mobile Banking HTML5 based App and app last version was release 28-May and was working fine on all devices then when some device auto updated to  Android System WebView 61.0.3163.98 (20-sep) the app starts the browser but nothing shows in the browser just a white screen 

Sample Device names: 
    Sony xperia c4 OS 5.1 
    HTC Desire 728G OS 5.1
    Lenovo A6020a46 OS 5.1.1
    OPPO A1601 – Android version 5.1
    Samsung S7
    Sony Aqua 4 - Android version 6
    (maybe others)
Android version: 5.1,5.1.1,6 (maybe others)
WebView version (from system settings -> Apps -> Android System WebView):
61.0.3163.98 (20-sep) And also the following beta versions until 28-Sep
Application: https://play.google.com/store/apps/details?id=com.CA.Push&hl=en
Application version: Current 2.0.1 


Steps to reproduce:
(1) Open App 

Expected result:
App loads web view and shows the App Menu 

Actual result:
App Loads web view then white screen user cant do anything 

 
Cc: sandeepkumars@chromium.org
 Issue 770460  has been merged into this issue.
Cc: nyerramilli@chromium.org ligim...@chromium.org
Labels: Needs-triage-Mobile Triaged-Mobile Needs-Feedback
Unable to reproduce the issue in Android. Able to see the app menu.

Steps Followed
1. Installed banki by Credit Agricole from playstore
2. Launched the app
3. Able to see the app menu.

WebView versions tested
61.0.3163.98

OS
Android 7.1.2, 6.0.1, 5.0.0, 5.1.1

Android Devices
7.1.2 Pixel XL Build/N2G48E, 6.0.1: SM-J710F Build/MMB29K, 5.0.0:; Micromax A106 Build/LRX21M, 5.1.1; SM J200G Build/LMY47X

@mmazmy: Could you please let us know if we missed any steps from our end. If possible please provide a screen cast that would help us in further triaging of the issue.

Thanks!!


Comment 3 by mma...@gmail.com, Oct 4 2017

Thanks for your reply please find attached a screen video showing the case

Please also note that we tried to recompile the app again using latest Android and Xamarin lib and the output apk does not have this case (you can get the recompiled APK from https://www.dropbox.com/s/2uexxq3ivsnglbs/com.CA.Push.apk?dl=0)

which basically mean that the new view view has broken some compatibility with older Apps

 
WhatsApp Video 2017-10-04 at 5.44.34 PM.mp4
1.6 MB View Download
Project Member

Comment 4 by sheriffbot@chromium.org, Oct 4 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "sandeepkumars@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 5 by mma...@gmail.com, Oct 4 2017

please use the following link for the newly compiled apk https://app.box.com/s/vlzayn2wmqk0ob9qidrilvqsijm4omat (ignore the link in the previous message)
Cc: ntfschr@chromium.org
Labels: Needs-Feedback
Your last apk is broken (INSTALL_PARSE_FAILED_NO_CERTIFICATES).

Please attach a minimal APK which can reproduce the issue, or (even better) point us to an entry in the play store.

Comment 7 by mma...@gmail.com, Oct 6 2017

you can get a signed version from https://app.box.com/s/73srjhizpjkelkzcumgjkju2qj5zmdll
Project Member

Comment 8 by sheriffbot@chromium.org, Oct 6 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "ntfschr@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: Needs-Feedback
I just tried the APK from c#7 on Nexus 6 / Android L (5.1) / 61.0.3163.97. No repro.

> Please also note that we tried to recompile the app again using latest Android and Xamarin lib and the output apk does not have this case

This confuses me. "Does not have this case" sounds like "the problem is now fixed." What issues remain?
demo.mp4
11.4 MB View Download

Comment 10 by mma...@gmail.com, Oct 6 2017

Two issues here:

1- Compatibility with existing Store version is broken ... is this a planned broke  or is it explain in any way or it should be fixed in coming webview (if this is unintended then when is the fix for it so that we can decide if we would release a new version to store only to fix this issue 

2- Upon more extensive testing we also found other side effects in the latest web view even with the work build .. the effect is that some devices are performing way bad than they did before this web view was applied 

Attached are two videos one showing the normal performance normally expected and running on some devices and other video showing Slow performance (note that the same device performing slow if we remove the latest web view would perform normal)

Any explanation or advise on how to handle  issue 2  ?



Normal Performance.mp4
2.0 MB View Download
Slow Perf.mp4
1.6 MB View Download
Project Member

Comment 11 by sheriffbot@chromium.org, Oct 6 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "ntfschr@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: Needs-Feedback
I just tried com.CA.Push from the play store, WebView 61.0.3163.97. I see no issue.

> Compatibility with existing Store version is broken ... is this a planned broke

No, not planned (as far as I'm aware). If I could reproduce the breakage, I might be able to better confirm.

Even if it's not planned, this might be tricky to diagnose unless we can repro. It's not clear what your app is actually doing.

Let me know what the correct repro steps are, this is still rather unclear to me.

Comment 13 by mma...@gmail.com, Oct 7 2017

What about your assessment of the 2nd point related to performance as shown in the previously attached video ??
Project Member

Comment 14 by sheriffbot@chromium.org, Oct 7 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "ntfschr@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: Needs-Feedback
Again, it's hard to say. I don't know what your app is doing, so I can't make any comment on why performance has changed. In general, performance regressions are things we want to avoid/fix.

---

Can you provide a minimal APK which demonstrates the broken HTML5 page? Please provide a compiled APK as well as zipped source code.
Labels: WV-Triaged
Modifying Label

Labels: -Triaged-Mobile
@mmazmy: Could you please respond to comment #15?

Thanks!!
Status: WontFix (was: Unconfirmed)
Closing this issue as WontFix, due to lack of response from reporter.

@mmazmy: Please feel free to log a new issue if you face any?

Thanks!!

Sign in to add a comment