IssueTracker

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

Please mention the steps to be followed for reproducing the issue with the given sample apk.

Android full bug report capturing

After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory.

Alternate method

Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.

Screen record of the issue, for clarity

Please capture screen record or video of the issue using the following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4\

Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.

Thank you for reporting this issue. We have shared this with our product and engineering team and will update this issue with more information as it becomes available.

Our engineering team responded :

It is indeed related to the changes applied for Safer Implicit Intents, this is the intended behaviour.

To fix this issue, the developer will need to make the intent explicit (either explicit by package or explicit by component), the following change will fix it:

@Composable
fun Greeting(name: String, modifier: Modifier = Modifier, context: Context) {
    Button(onClick = { context.sendBroadcast(Intent("com.example.action")) }) {}
}

should become something like:

@Composable
fun Greeting(name: String, modifier: Modifier = Modifier, context: Context) {
    val intent = Intent("com.example.action")
    intent.setPackage(context.getPackageName())
    Button(onClick = { context.sendBroadcast(intent) }) {}
}

We’ll be closing this issue due to not having enough actionable information. If you continue to have this issue, please open a new issue and add the relevant information along with a reference link to the earlier issue.

I have registered the receiver with a custom action.

Sending like this:

 Intent intent = new Intent("com.gt-broadcast-refresh");
 requireActivity().sendBroadcast(intent);

Receiving like this:

 if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.TIRAMISU) {
            requireActivity().registerReceiver(refreshUIReceiver, new IntentFilter("com.gt-broadcast-refresh"), Context.RECEIVER_NOT_EXPORTED);
 } else {
            requireActivity().registerReceiver(refreshUIReceiver, new IntentFilter("com.gt-broadcast-refresh"));
 }

It will work in the emulator with an Android 14 device, but it will not work on a real device, such as the Google Pixel 8 Pro, because it will not listen to the action. I have configured the registration based on the Google documentation for Android 14.

should I need to add any extra flag or permission while sending the custom action?

All, I found the solution for all requireActivity().registerReceiver() calls. They will only listen for the action if the action is sent with the package name of the application. So whenever we send a broadcast, we should also set the package with the intent using intent.setPackage(getPackageName()). Then, the registered receiver will be able to listen for the action.

Reference link: https://developer.android.com/about/versions/14/behavior-changes-14#runtime-receivers-exported

Unbelievable, 9 months later this is still not in the docs.