microsoft / microsoft/WindowsAppSDK
Push notification http response status code 500
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
Hello, we recently have discovered a large number of 500 errors occurring when using WNS HTTP API for notification pushes.
https://dm3p.notify.windows.com/?token={myToken}
Could you please assist us in investigating this issue? Below are some cases, and if you need any additional information, please let me know.
{"MsgID":"4D1862580BFBB38D","DebugTrace":"SG2PEPF0002029C","DeviceStatus":"unknown","ErrCode":500,"ErrDesc":""}
{"MsgID":"3081ACF9115CFFE1","DebugTrace":"SG2PEPF000202DB","DeviceStatus":"unknown","ErrCode":500,"ErrDesc":""}
{"MsgID":"9A1C1567B8EF24E","DebugTrace":"SG2PEPF00045883","DeviceStatus":"unknown","ErrCode":500,"ErrDesc":""}
Steps to reproduce the bug
1
Expected behavior
No response
Screenshots
No response
NuGet package version
None
Packaging type
No response
Windows version
No response
IDE
No response
Additional context
No response
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
Start with the WNS HTTP API endpoint and the three 500-response samples in the issue, then gather the missing reproduction details such as request type, payload, headers, and timing. Done means the failure can be reproduced or narrowed to an actionable WNS or Windows App SDK cause; the issue names no source files or tests.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100