The latest Android System WebView update to version 109.0.5454.117 caused issues on some Google TV devices. My application uses a browser with a transparent background. After updating the Android System WebView, navigation through the WebView in my application occurs with a delay (for example, if you press the button down, this will not happen immediately, but after a few seconds.). This doesn't happen on phones, but only on some Google TVs, most likely only where Android System WebView is 109.0.5454.117.
Does anyone know what could be the problem and what needs to be fixed?
It's been 17 days now and Google hasn't released an update to 109.0.5454.117 that would fix the problem.
About a year ago there was a similar problem, but Google quickly released an update and the problem was solved.
Can I add a stable version of the Android System WebView to my application myself?
Related
I am supporting a hybrid app built using IBM mobile first platform v7.1 and jQueryMobile framework in which we are facing UI element size issues on android platform. The font, button and all the other elements appearing too large on android app since last 2 weeks. However, the app was working fine few days back.This app is on google playstore and this issue persist over there as well
I don't know what has broken the app since nothing has been changed from the code perspective and its happening only on android OS version 6.0 and above. This might be an android OS version issue
Any Guidance or suggestions will be appreciated to identify the root cause or fixing the issue
Since there is a known bug in Android Kitkat versions (most commonly 4.4.2) that disallows users to open file upload dialog after tapping any HTML file element within WebView, can Android itself determine if current device suffers from this bug?
Determining only by Android version is not a good solution since not all devices running 4.4.2 suffer from this bug.
I had to deal with this problem too. Eventually I decided it's not worth it because not that many device modifies the stock webkit, so I applied the workaround based on version number alone (SDK_INT == 19)
However if webkit is really the culprit (and not some other system class), you may want to detect the webkit version: https://stackoverflow.com/a/29218966/828752
From https://developer.chrome.com/multidevice/webview/overview#what_version_of_chrome_is_it_based_on_:
The WebView shipped with Android 4.4 (KitKat) is based on the same
code as Chrome for Android version 30. This WebView does not have full
feature parity with Chrome for Android and is given the version number
30.0.0.0. The updated WebView shipped with Android 4.4.3 has the version number 33.0.0.0.
This detection method isnt very elegant however as there is no precise way to detect occurrence of this bug on a device best way is to count via javascript how many times a user has clicked the HTML FILE element.
If the counter of clicks exceeds some value (because the user is trying to get it work over and over) you know its not working. At this point by far most common version with this bug is 4.4.2 so you can activate this counter only when this Android version is detected for extra layer of precision.
Like I said, this detection method is quite messy however if Android has a bug this is as good as it gets. Users who dont experience this bug are unlikely to click more than once the HTML FILE element.
I have built hybrid app with Sencha touch 2.3 and till recent it was working fine but i recently updated the Android System Webview via Play Store (i have moto g running android 5.0.1) and now i am encountering various bugs in UI as follows :
The selectfield picker does not work correctly now. It behaves randomly. The store bound to it has data but no items are displayed in the picker when it opens. At times items do get displayed but you cannot select the items at bottom because picker always resets the selection to the item at top.
Few screens show up blank initially when rendered for the first time. As soon as user touches the screen and moves a little bit the whole screen/view becomes visible.
Also there might be other things that might have broken after updating the webview which i might not have discovered but this a big issue as far as developing for android is concerned with sencha touch. The webview updates are now pushed Over the Air and hence many things may break in future.
I also confirmed the above bugs in older versions of android wherein the webview has not been updated and the above bugs do not show up in.
I am thinking of using crosswalk as the solution to the issues with the webview. Anyone with the same issues or any tips regarding a fix ?
I ran into a similar issue with my Sencha Touch app (almost nothing rendered). Here is the workaround I used which seems to work great:
http://trevorbrindle.com/chrome-43-broke-sencha/
Thanks #Ian. The link was tremendously helpful and it solved the issue for now. Sencha has not officially released a build with these fixes so the overrides are the only solution right now.
For anyone facing same issues here is one more link from the Sencha Forums where all the issues sencha frameworks are facing with Chrome 43 are stated and solved.
https://www.sencha.com/forum/announcement.php?f=92&a=58
I am also stuck with same issue and i found solution we should not update the chrome. Better download 42.0.2311.152_chrome64_installer which is offline exe for chrome.
I'm currently using WebView.draw() to take a screenshot of the entire WebView and save it into a Bitmap (based off of this solution). It has worked perfectly up until now.
I was recently testing this functionality on a Nexus 5 (please note that on the Nexus 5 the WebView in question is bigger than the screen, so the user can scroll both horizontally and vertically) running Lollipop 5.1 and the latest update of Android System WebView (version 42.0.2311.137 at time of writing) when I noticed that the generated bitmap was wrong. It had the correct dimensions but instead of showing the whole WebView, it only had the part of the WebView that was visible to the user when the method was called.
I have tried uninstalling all updates to the Android System WebView (thus bringing it back to version 39 (1743759-arm) and with the factory version the functionality works fine. So this problem is due to a relatively recent update of the Android System WebView. I wasn't able to find a change log so I can't figure out what has changed and how to fix it.
Below is a quick visual explanation:
Has anyone else encountered this problem and found a possible solution ?
You need to call WebView.enableSlowWholeDocumentDraw() before creating any WebViews. That is, if you have any WebViews in your layout, make sure you call this method before calling setContentView() in your onCreate().
I have made HTML5 application which is using vmoss platform, similar to phonegap. The application was running smoothly on samsung galaxy 10.1 tab with android version 4.0.4. After the client updated the device to android 4.1.2 now he is complaining of following issues.
Calendar control not working in new version
Text box controls having focus issues
Application GUI Issues because response is very slow
The page where issue of slowness comes is the page where child pages are loaded inside one of its div.
Can someone tell me, is it android os update issue or what?
i think it's because of the platform not updated to work/cope well with version 4.1.2
this one is vmoss platform issue.
Better try to run simple Html page with all these control without using the VMOSS at backend and see if there will be any issue.
Some time the version of Jquery doesn't fully support by the browser.