WiFiDirect cppwinrt can not get "PairingRequested" callback after GO/GC calls PairingRequested()

Open
#1,406 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start with the WifiDirect/cppwinrt sample and trace WiFiDirectConnectionParameters::PairAsync(...).get() together with the PairingRequested callback handler. Reproduce the GO and GC pairing flow, including the already-paired and unknown-failure results, and verify whether the callback processes the expected WiFiDirectConfigurationMethod.

Written by the indexing model from the issue text.

Description

bug

Which sample are you reporting a bug in?

WifiDirect/cppwinrt

Describe the bug
I am using the above sample code to build a WifiDirect GO and GC command line utilities. When the GO and GC utilities do pairing with WiFiDirectConnectionParameters::PairAsync(...).get(), GC always returns "The device object has already been paired" and GO always returns "An unknown failure occurred." WiFiDirectConnectionParameters::PairingRequested call back handler never get called.
The interesting thing is that they are already paired even with the error result. They can even ping/iperf each other.
The problem is that the pairing event handler which processes the WiFiDirectConfigurationMethod(ProvidePin/DisplayPin/PushButton) won't get called. This will expose security problems. I saw people post same problem here: https://learn.microsoft.com/en-us/answers/questions/827554/i-use-pairasync-method-to-pair-another-wifidirect .
I wonder if anyone saw this problem and have any idea of it.

To Reproduce

Expected behavior
WiFiDirectConnectionParameters::PairingRequested call back handler should be called after pairing.

Screenshots

Configuration

Additional context

Dominant language
JavaScript
Stars
9.7k
Forks
7.8k
No merged PRs in 30d

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.

More from microsoft/Windows-universal-samples

All issues in microsoft/Windows-universal-samples

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.