Make sure to acknowledge stale broadcasts
If a broadcast arrives at a process but the receiver has been unregistered in the interval between dispatch and its arrival on the receiving process's side, we were simply dropping the broadcast entirely, leading to spurious ANRs and potentially issues involving future broadcasts being timed out incorrectly. Fix this by making sure to correctly 'finish' a broadcast even when the recipient app no longer has any receiver that matches the broadcast's profile. Change-Id: If990cab021a26668052cb536753f6c308d80a5b4
Loading
Please register or sign in to comment