Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit e8d7c840 authored by Christopher Tate's avatar Christopher Tate
Browse files

No need to post FGS notifications after process death 

If the app dies during the deferral, we don't actually need to post the
FGS notification.  Since some of the service-related bookkeeping gets
reset as part of teardown, this avoids potential invalid accesses.

Bug: 197070543
Bug: 200555680
Test: atest CtsAppTestCases:android.app.cts.ServiceTest
Test: atest CtsAppTestCases:android.app.cts.NotificationManagerTest
Change-Id: I8a5eb91bb6070910ac973c195d118962265aec05
parent 44e5c9a0

services/core/java/com/android/server/am/ServiceRecord.java

+3 −3
Original line number Diff line number Diff line
@@ -927,9 +927,9 @@ final class ServiceRecord extends Binder implements ComponentName.WithComponentN 
    }



    public void postNotification() {

        if (isForeground && foregroundNoti != null && app != null) {

            final int appUid = appInfo.uid;

            final int appPid = app.getPid();

        if (isForeground && foregroundNoti != null) {

            // Do asynchronous communication with notification manager to

            // avoid deadlocks.

            final String localPackageName = packageName;