microsoft / microsoft/Windows-classic-samples
WiFiDirectLegacyAP | decline connection does not wor
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 5.7k
- Forks
- 3.3k
- PR merge metrics
- No merged PRs in 30d
Description
The client is not rejected even when i decline the connection..
The client still gets an IP and i can communicate with the WifiLegacy server
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 by locating the WiFiDirectLegacyAP sample and reproducing the declined-connection flow described in the issue. Inspect how the decline decision is handled and verify the client's resulting network state. Done means a declined client is rejected, does not receive an IP, and cannot communicate with the WiFiLegacy server.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100