diff options
| author | Christopher Tate <ctate@google.com> | 2015-07-29 19:23:58 -0700 |
|---|---|---|
| committer | Christopher Tate <ctate@google.com> | 2015-07-29 19:27:47 -0700 |
| commit | 2ad7e27362f682e3358b307bef23196be1c8b126 (patch) | |
| tree | 6ffa38e076eaac06c5df2e025b3279dc8403793d /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | a991c66c12da30d0240ac6c98736edee93d95977 (diff) | |
Fix issues around process teardown after full-data restore
The unified code path for cleanup was mistakenly looking at the
android:killAfterRestore manifest attribute even for full-data restore
operations. That attribute is only relevant for key/value payload
handling. We need to *always* kill after restore in the full-data
case because the app will otherwise be allowed to enter normal
component lifecycles without its correct Application / ContentProvider
state in force.
Bug 22704852
Change-Id: Ia63f985a35c28084c734389cfc49d3792173e5c7
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions