I found that css variables do not work… Standard browser in Android 5.1 and Android 6.0 emulator is Chrome 39/44, but css variables works after 49 version of Chrome… So in that case… Framework7 v4 will not work on “naked” Android 5.1 and Android 6.0 due to old browser.

Thanks for the answer. You’re right, there is not much users with those Androids and I understand that. Emulator is just the fastest way to test bundle on a device and, unfortunately, it doesnt work.

Step back to v3 is a good variant too. But postcss (which I didn’t even think OMG) - probably is the best solution.

Thank you!

P.S. I’m using Framework7 since version 2, made a big application with it (up to 100k+ uploads both Android and iOS), now developing a new one and I was very exited after news on v4 with its stunning features. Thank you for your work!

Even though we, developers are there to move with recent technologies, sometimes our customers are somewhat more conservative and stick e.g. with Android 5. And that means we cannot upgrade to F7v4 (regarding these projects) until this is resolved.

Stats of our application saying there are less than <1% old androids (5/6) with Chrome lower than 49 version. So we are showing at startup some kind of popup with proposition to update system component and giving a link to Android System WebView on Google Play. But we didn’t test that yet.

Interesting, but looks like Android System Webview is not available on all devices. I have Android 8.1 device and I can’t install it, it says “Disabled”, not sure what it means.

I’m still thinking about doing that thing with postcss by doing some extra stuff. But even then, some features that highly rely on CSS variables like new large navbar won’t work at all. Not sure does it worth it or not

So what we’ve got? Very little amount of users, who didn’t update their phone for YEARS? I think it doesnt worth it to do anything with that. I think if user have old 5.1 or 6.0 android and he is using it every day - he updated that component in the past, but if he didn’t - at least we can ask him to do that.

Back to postcss thing: there are many places where variables depends on .classes, so, imo, it’s very difficult to properly re-work those styles back to plain css. Or not? To be honest I didn’t go deep into that, it looks too complicated challenge, so… I think it’s better to ask user to update.

I forgot one thing a wanted to say. If you’re developing an app supporting Android 5.1/6.0 you cannot test framework on Android Studio emulators, because of ancient webview by default and there are no Google Play, so you’re not able to update that component. And if you haven’t real devices on your table - you’re in trouble…

Sure, you can find .apk with GP, or even with fresh System WebView, BUT there are bug in cordova, when you’re trying to run app on emulator and it stuck up. The only way is I found to fix that - wipe all data. That means that you must do everything from scratch every time.

UPDATE: Installing latest Android System WebView on emulator (via APK) didn’t force system webview to update, but on a real device it works as expected (system webview updated).

I found three different manuals on how to install opengapps, but none of them work. I think problem in my OS (Windows 10)… I even cannot run adb in root mode (adb root) to change write rights in emulator.