diff options
| author | Gavin Corkery <gavincorkery@google.com> | 2020-04-29 16:30:10 +0100 |
|---|---|---|
| committer | Gavin Corkery <gavincorkery@google.com> | 2020-05-11 22:33:52 +0100 |
| commit | 24b4ed567ed6d53b407bc8a92e3cd394f58e8d8c (patch) | |
| tree | ffde1510fce08cd4661fe5aa2ea5976820570033 /tools/aapt2/java/JavaClassGenerator.cpp | |
| parent | ff779f6d8e2588c64173b7087efe81214f9bb167 (diff) | |
Mark apex sessions as successful upon boot completion
Instead of marking apex sessions as successful immediately, wait
until the boot has completed. This ensures that the checkpoint
has been committed. This is necessary since the apex session
state lives in /metadata, so any changes to the session will
persist regardless of the checkpoint state. This change ensures
that APK and APEX sessions behave the same way if the device
reboots after activation, but before boot completion.
Create a new lifecycle class within Staging Manager to receive
calls for boot completion.
Test: atest ApexRollbackTests
Test: Manual test of rebooting device after activation and before
boot completion, and ensuring session is not marked as successful
Bug: 154705130
Change-Id: I822e46123d3f4d3d84e0c50c9aa791c1a81e8f50
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator.cpp')
0 files changed, 0 insertions, 0 deletions