Apps not starting until QML cache is deleted
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical System Image |
Confirmed
|
Medium
|
Alejandro J. Cura | ||
| click (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
I've seen this a couple of times now:
When an app, or the whole system crashes/runs out of battery or similar, it can mess up the qml cache for apps. The app then won't start any more until the qml cache is deleted manually, or eventually some update of the app is rolled out that makes the cache realize it is out of date. This manifests itself in the app sitting there on the splash screen or just being white and never finish loading.
Admittedly this does not happen very often, however, the problem is that there is no way out of this for a normal user. Once a user runs into this situation, the app is basically non existent any more. Neither rebooting the phone, nor reinstalling the app resolves the situation. Currently I know of a customer which can't launch the telegram app until we meet end of march because I can't instruct her to use the terminal to clear the qml cache...
| Pat McGowan (pat-mcgowan) wrote | #1 |
| Changed in canonical-devices-system-image: | |
| assignee: | nobody → Alejandro J. Cura (alecu) |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
The cache is also cleared on a system update which I am not sure is a feature.
I would think uninstalling the app should clear the QML cache to work around this.