Removing a notification that isn't there isn't a big deal.
You shouldn't do it, but there's no need to fault your process. Bug: 6396830 Change-Id: I47c20b9829e4e8bb98862f33c3c52be1b5987f37
This commit is contained in:
@@ -489,7 +489,8 @@ public class StatusBarManagerService extends IStatusBarService.Stub
|
||||
synchronized (mNotifications) {
|
||||
final StatusBarNotification n = mNotifications.remove(key);
|
||||
if (n == null) {
|
||||
throw new IllegalArgumentException("removeNotification key not found: " + key);
|
||||
Slog.e(TAG, "removeNotification key not found: " + key);
|
||||
return;
|
||||
}
|
||||
if (mBar != null) {
|
||||
try {
|
||||
|
||||
Reference in New Issue
Block a user