Olivier and I had a chat already on IRC about this, to sum it up: This situation happens because there was no change in the actual QML files, however an underlying QML plugin did change. In my opinion, this change comes with an ABI break and there was no version bump for it. Had there been a version bump, com.canonical.Oxide would've gone from 1.0 to 1.x and the QML file would've changed, thus wiping the cache.
In details, the ABI break is probably a change in the vtable for the plugin. Changing the ordering of property helpers and invokables result in different property IDs in the cache, this breaks the precompiled QML because it expects things in the wrong place. This however is not something we can fully rely on as there will always be situations when an ABI breakage lands in the archive; so I vote to go with ogra's OTA hook for wiping all application caches. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1394380 Title: QML cache not regenerated correctly on image update Status in “android” package in Ubuntu: Invalid Status in “lxc-android-config” package in Ubuntu: Confirmed Status in “lxc-android-config” package in Ubuntu RTM: Confirmed Bug description: image rtm-proposed 166 Multiple problems here, due to the fact that oxide was updated (a new release) and webrowser-app was updated 1) webbrowser-app cache was not updated on the image upgrade in .cache/QML/Apps/webbrowser-app and desktop versions of web pages are displayed until the cache is destroyed or regenerated. Try cnn.com or nytimes.com 2) no webbapps cache is regenerated, so launching of the webapps displays wrong pages (.cache/QML/Apps/*webapps*) due to stale cache. You can try Google Maps for an example. Deleting the cache makes them work again properly. Expected Results: - after image upgrade, either all of the apps should be regenerated smartly, or we should blow away all of the caches to prevent an issue when a library (like oxide) is upgraded and causes an invalid cache. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android/+bug/1394380/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp