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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1394380 Title: QML cache not regenerated correctly on image update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android/+bug/1394380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
