I have the same problem on two devices.
In the first one with android 7 I solved it with a factory reset; in the second one with android 5.1 I use it to do some tests.
I'm worried about our customers using our app.
I thought it was malware but the device is clean.
Let's hope someone from the Oracle staff will tell us something.
Hello, found the problem.
It's the latest update of Android System WebView:
Package name: com.google.android.webview
Version: 79.0.3945.79 (394507906)
File size: 34.8 MB
Updated: December 12, 2019
You need to uninstall the update and the app is working properly.
I ask MAF developers to fix the problem for the next version release.
Hello, same problem with the last update of Chrome (79.0.3945.79).
You need to uninstall the update to make sure MAF works properly.
Thanks for the spot-on answer.
Please brief me a bit how chrome's update is causing issues in MAF applications?
In a MAF application, the web view delivers the user interface by rendering the application markup as HTML 5.
Android’s WebView feature has morphed several times in the past few years. Android 4.4 KitKat first introduced a Chromium-based WebView component in 2013. Back then, it was built into the system, but it became a separately-updated component later down the road, with Android 5.0 Lollipop. With Android 7.0 Nougat, however, all WebView-related duties were just handled by Google Chrome in an effort to simplify things.
With Android 10, Google has reverted to the pre-Nougat behavior, and WebView is now handled by a separate app again. This newer implementation, according to a Google engineer, is called “Trichrome”.
We hope that we have no new incompatibilities with MAF.
So, Chrome 80 is available now, and it does not fix the problem. Asking our field service team to turn off auto updates and remain at an old level of Chrome isn't a long term solution. Has anyone figured out how to correct this?
unfortunately not. We are all waiting for Team MAF to respond on this important issue.
Has anyone found a solution to this problem? I am having the same issue.
Hi, problem solved!
For MAF versions lower than 2.6.2 it is necessary to override the .css by entering the following specifications:
That looks like the fix! thanks!