diff options
| author | Christopher Tate <ctate@google.com> | 2016-04-25 17:08:56 -0700 |
|---|---|---|
| committer | Christopher Tate <ctate@google.com> | 2016-04-27 15:07:26 -0700 |
| commit | 5cf5578a457e448dda9fd47943e91f0f3b67690f (patch) | |
| tree | 3035c71ca3f290dad8b66f037d071996c05dde9e /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | 68d180bbd1892ee5112c76be842a40a7251ed5a5 (diff) | |
Make sure FIRST_LAUNCH is after PACKAGE_ADDED
If an app undergoes restore during install, it is considered 'started'
and the FIRST_LAUNCH broadcast needs to go out. However, this must not
take place until after the restore operation has fully completed, in
order to avoid publishing the app's existence while it may still be in
an incoherent state. We now make this broadcast part of POST_INSTALL
in the restore case.
Bundled apps are in the 'started' state regardless, so no FIRST_LAUNCH
broadcast is ever sent for them -- this CL does not change that
existing behavior even in the case of setup-time data restore of
factory-installed packages.
Bug 28173625
Change-Id: Ibcc3758576662dc447b75476173a0d008a9fe4da
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions