Skip to content

AppNotificationManager doesn't support multiple app entries. #6402

@bkaankose

Description

@bkaankose

Describe the bug

I have a packaged MSIX which has 2 app entries in package.manifest. "App A" and "App B". I want to be able to raise app notifications from App A with the name of App B, and vice versa.

Previously this was possible using with ToastNotificationManager.CreateToastNotifier that takes applicationId as parameter, but AppNotificationManager.Default does not support this.

Also, having 2 different com server for app notification handling crashes AppNotificationManager.Default.Register() crash with COMException that says "The class is configured to run as a security id different from the caller", which is expected but blocks the notification handling for the second registry.

Steps to reproduce the bug

  1. Create another entry under tag in your package.appxmanifest.
  2. Define desktop:Extension and com:Extension for both of the application entries in package.appxmanifest.
  3. Run the app.

You'll see that AppNotificationManager.Default.Register() crashes with COMException. Also, there is no API to create notifications between app entries.

Expected behavior

AppNotificationManager should be extended with better APIs to handle multiple app entries.

Screenshots

No response

NuGet package version

2.0.250930001-experimental1

Packaging type

Packaged (MSIX)

Windows version

Insider Build (xxxxx)

IDE

Visual Studio 2022-preview

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions