DApp doesn't load on Android 6.0

[tomlinton]

As reported by @franck. The DApp gives an endless loading indicator on Android 6.0. Console reveals Unexpected token ....

This is due to the older version of Chromium used in that version of Android (so its not Android specific, but old version of Chromium specific) not supporting es6 and I suspect the DApp is missing the correct babel transforms/preset.

[franckc]

A user reported this issue, on two of his devices:

• Android Version 6.0.1
• Android 5.1. Phone Meizu. Flyme 6.3.0.0G

I recommended he updates his webview package but his device did not allow him to update...

[rtman]

@tomlinton @franckc sounds like babel-es6-polyfill would do the trick?

[franckc]

@rtman I'm not very familiar with the mobile side of things but it would seem to me you are right.

@tomlinton a) does Ryan's suggestion sound good to you ? b) Do you know if this issue is reproducible under the Android simulator so that if @rtman tries to fix it by using babel-es6-polyfill he can verify the fix works ?

[tomlinton]

I have tried that (and a host of others).

Yep you can reproduce it in an Android simulator. Or you can also use a workaround to install an older version of chrome (<= 44 in Android 6.0 from memory).

[tomlinton]

Another approach I've tried with no success was setting the targets for @babel/preset-env via a browserlist query to something very wide, e.g. "browserslist": "> 0.1%, Android 67".