diff options
| author | Da Xing <qiyueliuhuo813@gmail.com> | 2018-11-18 20:10:17 +0800 |
|---|---|---|
| committer | Xin Li <delphij@google.com> | 2019-09-06 04:39:57 +0000 |
| commit | 70876ce13f2e334d5b75597f3a2a0717d0c944ff (patch) | |
| tree | 35986a195aec2f7756f5ed7a1b4e21020011fa5a /tests/Codegen/src/com/android/codegentest/SampleDataClassTest.java | |
| parent | d191463bb0a528d3dc97a21b85ad83374b27c239 (diff) | |
Crash app on foreground service notification error.
Resolved issue 118612296.
On any notification error, the NMS silently cancels the notification,
including foreground service notifications. Thus, an app could pass in a
garbage notification deliberately and start a foreground service silently.
This patch resolved this issue by judging the notification's flag, and if
it is a foreground notification, still crash the app as previous platforms,
and if it is a normal notification, don't crash the app.
Background: In 3ad4cdd1, which was merged into Android 9 release, the crash
behaviour is removed. But it is an important rule that foreground services
guaranteed to show an ongoing notification.
Test: Run the sample apk provided in the issue, it's main thread received
a RemoteServiceException: Bad notification posted from package...
as intended behaviour.
Bug: 118612296
Merged-In: I94d9de50bb03c33666471e3dbd9c721e9278f7cb
Change-Id: Ice6faab055e2dacd3d2d12803fcf51e13d3b0f21
Diffstat (limited to 'tests/Codegen/src/com/android/codegentest/SampleDataClassTest.java')
0 files changed, 0 insertions, 0 deletions