Fix clicking on notification does not restore activity

[ne0rrmatrix]

Description of Change

This pull request improves the behavior of the foreground service notification in the MediaControlsService for Android by ensuring that tapping the notification brings the user back to the main app activity. The changes introduce a helper method to create the appropriate PendingIntent and attach it to the notification.

Enhancement to notification interaction:

• The notification shown by MediaControlsService now includes a content intent, so tapping the notification will launch (or bring to front) the main app activity. This is achieved by creating a PendingIntent using the new CreateActivityPendingIntent() method and setting it with SetContentIntent on the notification builder.

Internal code improvements:

• Added a static CreateActivityPendingIntent() method that safely constructs a PendingIntent to launch the main activity, handling potential null references and setting intent flags to ensure correct activity behavior.

Linked Issues

• Fixes [BUG] Android 14+ Notification Body Tap Does Nothing #2976

PR Checklist

• Has a linked Issue, and the Issue has been approved(bug) or Championed (feature/proposal)
• Has tests (if omitted, state reason in description)
• Has samples (if omitted, state reason in description)
• Rebased on top of main at time of PR
• Changes adhere to coding standard
• Documentation created or updated: https://github.com/MicrosoftDocs/CommunityToolkit/pulls

Additional information

Fixes a long standing issue where clicking on notification after leaving app does not restore app. This fixes that issue and restores expected default android behavior.

[Copilot]

Pull request overview

This pull request fixes notification click behavior in the MediaControlsService for Android by adding a content intent that properly restores the main app activity when the user taps the foreground service notification.

Key changes:

• Added CreateActivityPendingIntent() helper method to construct the appropriate PendingIntent
• Integrated the PendingIntent into the notification builder via SetContentIntent()

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 3 comments.

[Copilot]

According to the project's coding guidelines, null checking should use the is pattern instead of the null-coalescing operator with throw. Consider refactoring these null checks to use pattern matching for consistency with the codebase standards.

For example, instead of:

var packageName = Platform.AppContext.PackageName ?? throw new InvalidOperationException("PackageName cannot be null");

Use:

if (Platform.AppContext.PackageName is not { } packageName)
{
    throw new InvalidOperationException("PackageName cannot be null");
}

This pattern should be applied to all three null checks in this method (PackageName, PackageManager, and the launch intent).

[Copilot]

According to the project's coding guidelines, null checking should use the is pattern instead of the null-coalescing operator with throw. Consider refactoring this null check to use pattern matching for consistency with the codebase standards.

For example, instead of:

return PendingIntent.GetActivity(Platform.AppContext, 0, launchIntent, flags) ?? throw new InvalidOperationException("PendingIntent cannot be null");

Use:

if (PendingIntent.GetActivity(Platform.AppContext, 0, launchIntent, flags) is not { } pendingIntent)
{
    throw new InvalidOperationException("PendingIntent cannot be null");
}
return pendingIntent;

[Copilot]

The PendingIntentFlags.Immutable flag was introduced in Android 12 (API 31), but this service supports Android 26+ (as indicated by the [SupportedOSPlatform("Android26.0")] attribute). Using this flag unconditionally will cause runtime errors on Android versions 26-30.

Consider adding a version check to use the appropriate flags:

var flags = OperatingSystem.IsAndroidVersionAtLeast(31)
    ? PendingIntentFlags.UpdateCurrent | PendingIntentFlags.Immutable
    : PendingIntentFlags.UpdateCurrent;

Alternatively, if Android 12+ is now the minimum supported version, update the SupportedOSPlatform attribute on the class accordingly.

Suggested change

	var flags = PendingIntentFlags.UpdateCurrent | PendingIntentFlags.Immutable;
	var flags = OperatingSystem.IsAndroidVersionAtLeast(31)
	? PendingIntentFlags.UpdateCurrent | PendingIntentFlags.Immutable
	: PendingIntentFlags.UpdateCurrent;