So recently, there were various updates of Chrome which caused temporary havoc to anyone with List or Grid controls on their .apk’s
Thankfully the issue was resolved (it was iScroll components which were ‘fixed’ to work with the the new Chrome versions.
Anyway, over the course of this adventure…we’ve discovered an annoying occurrence…
Sometimes when we (or our customers) upgrade Chrome on a tablet / phone, the phone says ‘new version = 57’ but phonegap (and IIS logs from webservices) still report e.g. Chrome version 52…
Which is a big issue, because version 52 does not work well with the latest versions of NSB…
So…the question is…why does it happen that a Chrome update doesn’t ‘take’ properly and replace the chrome components used by the app?
It has done on some devices but not on others…
Very strange…
Thanks,
Neil
Here is what Google has to say about this:
https://support.google.com/chrome/answer/95414?co=GENIE.Platform%3DAndroid&hl=en&oco=1
George Henne
NS BASIC Corporation
http://www.nsbasic.com
Hi George,
Yes, that’s pretty much what should happen.
in practice we have devices which ‘update’ to new versions of chrome and yet the app is saying they’re on older versions (after reboots and app reinstalls).
Weird, but true…
Thanks,
Neil
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.