Commit 0a693d08 authored Dec 13, 2022 by Michael Groover

Update receiver flag enforcement workaround for affected package

Android T allows apps to declare a runtime receiver as not exported
by invoking registerReceiver with a new RECEIVER_NOT_EXPORTED flag;
receivers registered with this flag will only receive broadcasts from
the platform and the app itself. However to ensure developers can
properly protect their receivers, all apps targeting U or later
registering a receiver for non-system broadcasts must specify either
the exported or not exported flag when invoking #registerReceiver;
if one of these flags is not provided, the platform will throw a
SecurityException. Some apps have already begun targeting U but
have not yet flagged their exposed receivers; this commit updates the
exemption for these apps to prevent them from crashing due to this
new enforcement while their receivers are updated.

Bug: 262396031
Test: Manually verified all affected apps were exempted.
Change-Id: Ieeb9834632eafba4941c67a5d3ae764d7c781fb3

parent 32765d94

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

+4 −3

Original line number	Diff line number	Diff line
		@@ -13564,9 +13564,10 @@ public class ActivityManagerService extends IActivityManager.Stub
		// updating their receivers to be exempt from this requirement until their receivers
		// are flagged.
		if (requireExplicitFlagForDynamicReceivers) {
		if ("com.google.android.apps.messaging".equals(callerPackage)) {
		// Note, a versionCode check for this package is not performed because it could
		// cause breakage with a subsequent update outside the system image.
		if ("com.shannon.imsservice".equals(callerPackage)) {
		// Note, a versionCode check for this package is not performed because this
		// package consumes the SecurityException, so it wouldn't be caught during
		// presubmit.
		requireExplicitFlagForDynamicReceivers = false;
		}
		}