microsoft / microsoft/WindowsAppSDK

WNS: Revoked channel URL

Open
#4,446 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area-Notifications
Dominant language
C++
Stars
4.7k
Forks
471
Avg merge
3d 13h
Merged PRs (30d)
28

Description

Describe the bug

Hello, I'm trying to migrate my XAML Islands app to Windows App SDK 1.5. A background process (normal background app without visible window, not Windows Runtime Component) handles raw notifications from my server and send them to main process using App Service. I followed this article: https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/notifications/push-notifications/push-quickstart and I'm able to request new channel, send notifications from my server and receive them in my app.

I noticed that channels are sometimes revoked before the expiration time. I didn't observe any specific moment or pattern of revocation. However, new manager from Microsoft.Windows.PushNotifications namespace doesn't have ChannelsRevoked method and I don't know how to handle moment of revocation.

I don't think I should use PushNotificationChannelManager from Windows.Networking.PushNotifications. Can you help me? :)

Couple of logs from my server:

2024-05-26 20:20:45.419 +02:00 [INF] Notification sent. Status code: Gone, delivery status: revoked.
2024-05-26 20:20:45.419 +02:00 [WRN] X-WNS-Debug-Trace: AM3PEPF00006225
2024-05-26 20:20:45.419 +02:00 [WRN] X-WNS-Error-Description: Revoked channel URL
2024-05-26 20:20:45.420 +02:00 [WRN] X-WNS-Msg-ID: 3155CBC13625D6D0
Steps to reproduce the bug
  1. Create new project
  2. Follow this article: https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/notifications/push-notifications/push-quickstart
Expected behavior

No response

Screenshots

No response

NuGet package version

Windows App SDK 1.5.3: 1.5.240428000

Packaging type

Packaged (MSIX)

Windows version

Windows 11 version 22H2 (22621, 2022 Update)

IDE

Visual Studio 2022

Additional context

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Windows App SDK 1.5 push notifications quickstart and compare its channel-management guidance with the Microsoft.Windows.PushNotifications and Windows.Networking.PushNotifications APIs. Reproduce the packaged MSIX setup on Windows 11 22H2 and investigate when a server receives the “Revoked channel URL” response; done means the revocation behavior and supported handling path are documented.

Written by the indexing model from the issue text.

Assessment

Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.