It said "userId" in NotificationManagerService and PreferencesHelper, but in practice was expecting its input to be a uid based on how it's implemented. It also seems most users were already passing in uids (particularly NotificationBackend).
Bug: 220469720
Test: manual verification of settings page, NMSTest, PreferencesHelperTest
Change-Id: I432bdfc7d2986a0a1111c210fd89671524b3885c
Bug: 219609105
Create os/IpcDataCache as a subclass of PropertyInvalidatedCache. The
APIs in the new class are the SystemApi for mainline modules.
Note that IpcDataCache.invalidateCache(String) is a new system API,
relative to the list in PropertyInvalidateCache. The new API is
static, which is the most common use case for invalidateCache calls.
The corresponding CTS test is updated in the next review. However, it
is also cloned into the current unit test.
Test: * atest FrameworksCoreTests:PropertyInvalidatedCacheTests
* atest FrameworksCoreTests:IpcDataCacheTest
Change-Id: I83ce97a4154b9065e0686ee99a25c90f955366ff
Sometimes an activity may be destroyed prematurely before the splash
screen animation begins. We can skip transferring the SplashScreenView
to client if the activity is finishing.
Also add more logs for future investigation.
Bug: 221436171
Bug: 170134300
Test: SplashscreenParametrizedTest
atest ActivityRecordTests SplashscreenTests
Change-Id: I0b5cdbc3d7ff14ad71139c3c5282a0554c40ea1e
This reverts commit c5bf49474f.
Reason for revert: API council decided not to expose it.
Bug: 202145402
Test: atest ActivityOptionsTest
Change-Id: I19c84a905f929e87f20a8dd28a3f45caf3e29c2c
Bug: 219609105
Change the meaning of "module" in PropertyInvalidatedCache to be a
string rather than an integer. One piece of the unit test has been
removed because of this.
Lint uncovered several lock errors. These are corrected as well.
The corresponding CTS test is updated in the next review.
Test:
* atest FrameworksCoreTests:PropertyInvalidatedCacheTests
Change-Id: Iaaa55974df2d22fc052d5b4b4744384c012f070a
Originally, View was implementing onBackInvokedDisptacherOwner, but now
only Activity and Dialog and since back event are related to the
window, it makes sense to move them into the android.window package
This follow up comment at:
ag/c/platform/frameworks/base/+/16764116/comments/e131f3ef_e3e1d2e0
Test: atest BackNavigationTests
Bug: 221401221
Change-Id: Ia2f26162beb6a41b6e162b31e599e882f8bf7320
Remove lock for cached state in ApplicationPackageManager.
Short-circut the instant app check for internal API calls.
Bug: 215305214
Test: presubmit
Change-Id: Ie122d76f6ea0e950fa25b22bea65f9938a3bf5f1
This optimizes the code by keeping only one remote connection.
Also fixed a typo in WindowManagerService: "StateState" -> "State".
Bug: 216630470
Bug: 220379118
Test: atest CtsWindowManagerDeviceTestCases:KeyguardTests
Change-Id: I8abb64f750e91db7048279f5217b63d35959c3b6
Only show a permission prompt if the activity is a launcher, the calling
app is the same as the opened intent app, or the
isEligibleForLegacyPermissionPrompt ActivityOption is set. Also prevents
the dialog from showing while the keyguard is locked.
Test: atest NotificationPermissionTest
Bug: 194833441
Fixes: 220891438
Change-Id: Ie5381af045d538a5b822bb1ccdf62b1dd916114f
