microsoft / microsoft/WindowsAppSDK-Samples
PushNotifications sample says to request WNS channel using Azure AppId instead of Azure ObjectId
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 1k
- Forks
- 335
- Avg merge
- 5d 1h
- Merged PRs (30d)
- 8
Description
Both of the following documents say to use the Azure AppId to request a WNS push notification channel:
- https://github.com/microsoft/WindowsAppSDK-Samples/blob/main/Samples/Notifications/Push/cpp-console-unpackaged/cpp-console-unpackaged.cpp
- https://github.com/microsoft/WindowsAppSDK-Samples/tree/main/Samples/Notifications/Push
However, the Push Notifications quick start says that the Azure AppId should be used for the server-side push notification registration and that the Azure ObjectId should be used to request a WNS push notification channel:
Which one of these is the correct? We have been successful using the Azure ObjectID to request a channel on the client, but I am a little nervous that this may break in the future as requesting a channel using the Azure AppID seems to return a channel Uri as well.
I didn't want to cross-post this issue to both repos, but perhaps this should also be posted as an issue on https://github.com/MicrosoftDocs?
Contributor guide
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
Read Samples/Notifications/Push/cpp-console-unpackaged/cpp-console-unpackaged.cpp and the Push sample documentation, then compare their identifier guidance with the linked push-quickstart.md. Verify which Azure identifier is correct for requesting a WNS channel and update the inconsistent sample guidance so the sample and quick start agree.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100