touch-packages team mailing list archive

[Oliver Grawert <ogra@xxxxxxxxxx>]

that might be, but what if we change the format of teh cache content,
what if we get another category of apps that behave the same... i belive
invalidating the cache after system upgrades is a good thing to prevent
us from any such possibilities

-- 
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