microsoft / microsoft/WindowsAppSDK
Calling `AppNotificationManager.Default.Register()` throws COMException (0x00703FD)
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 4.7k
- Forks
- 471
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 28
Description
### Describe the bug
I've followed the quickstart for using application notifications
Exception:
`System.Runtime.InteropServices.COMException (0x800703FD): Cannot create a stable subkey under a volatile parent key.`
### Steps to reproduce the bug
1. Create new MAUI project
2. Follow the quickstart for app notifications: https://learn.microsoft.com/en-gb/windows/apps/windows-app-sdk/notifications/app-notifications/app-notifications-quickstart
3. Run project
### Expected behavior
No exception and the notifications working properly.
### Screenshots
_No response_
### NuGet package version
Windows App SDK 1.3.2: 1.3.230602002
### Packaging type
Unpackaged
### Windows version
Windows 11 version 22H2 (22621, 2022 Update)
### IDE
Visual Studio 2022
### Additional context
Related: https://github.com/CommunityToolkit/WindowsCommunityToolkit/issues/4858
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure in a new unpackaged MAUI project by following the Windows App SDK app-notifications quickstart and calling AppNotificationManager.Default.Register() on Windows 11 22H2 with Windows App SDK 1.3.2. Start from that registration entry point and compare the result with the related CommunityToolkit issue. Done means registration completes without the COMException and notifications work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100