About P2P-INVITATION_RECEIVED handling

[wanted002]

Sometimes miraclecast sink will receive a P2P-INVITATION_RECEIVED wpas message instead of GO-NEG-REQUEST when I connect a source device to sink Not the 1st time . I think maybe the persistent p2p group on source device caused this(e.g. windows10). Any suggestions or guidance to handle this on sink side , please?

[albfan]

checking on logs for real connection:

TRACE: wpa: raw message: <3>P2P-INVITATION-RECEIVED sa=aa:aa:aa:aa:aa:aa go_dev_addr=aa:aa:aa:aa:aa:aa bssid=aa:aa:aa:aa:aa:aa unknown-network
DEBUG: supplicant: unhandled wpas-event: <3>P2P-INVITATION-RECEIVED sa=aa:aa:aa:aa:aa:aa go_dev_addr=aa:aa:aa:aa:aa:aa bssid=aa:aa:aa:aa:aa:aa unknown-network (supplicant_event() in ../src/wifi/wifid-supplicant.c:1518)
TRACE: wpa: raw message: IFNAME=p2p-dev-wlp0s20 <3>CTRL-EVENT-SCAN-STARTED 
TRACE: wpa: raw message: IFNAME=p2p-dev-wlp0s20 <3>CTRL-EVENT-SCAN-STARTED 
TRACE: wpa: raw message: <3>P2P-GO-NEG-REQUEST aa:aa:aa:aa:aa:aa dev_passwd_id=4 go_intent=14
DEBUG: supplicant: GO Negotiation Request from aa:aa:aa:aa:aa:aa (supplicant_event_p2p_go_neg_request() in ../src/wifi/wifid-supplicant.c:1086)
DEBUG: supplicant: connect to aa:aa:aa:aa:aa:aa via pbc/(null) (supplicant_peer_connect() in ../src/wifi/wifid-supplicant.c:760)
TRACE: wpa: raw message: <3>P2P-FIND-STOPPED 

that's probably sometihng to read on hostap repo:

https://w1.fi/cgit/hostap/tree/tests/hwsim/test_p2p_invitation.py

as the group is peristent it should allow to reconnect without pin, but we need to know what is the expected reply to continue

[jinhui123789]

I was wondering if this problem has been solved yet

[albfan]

A valid example of communication is needed to implement it

[ValdikSS]

Seems like Windows 10 expects the device to join the group it creates.
You need to pass join command to the p2p_connect.
Here's a working example: p2p_connect <MAC address> pbc persistent join