Post

Replies

Boosts

Views

Activity

Reply to During the Wi-Fi Aware's pairing process, Apple is unable to recognize the follow-up PMF sent by Android.
Hi sengui. We attempted to pair an Android device (Galaxy S25) with the iOS Wi-Fi Aware Demo, but the process was unsuccessful. We received an "onPairingSetupFailed" callback without any specific error message. Could you share how you managed to successfully complete the pairing process between Android and iOS? Is there any other way to contact you? My email is wuhaibinaaron with 163mail suffix Thanks
Sep ’25
Reply to Bug: Wi-Fi Aware (NAN) Subscriber Mode: nwPath.availableInterfaces Does Not Include nan0 Interface After Successful Peer Connection
Sorry for the typo earlier. To clarify: after connecting via Wi‑Fi Aware, we need to establish multiple additional NWConnection instances and send URLSession requests over the Wi‑Fi Aware network. However, we’re encountering a system "Nexus assignment error" when attempting to create NWConnections using the nan0 interface. Could you please demonstrate how to properly establish these extra NWConnections and send URLSession data through them?
Mar ’26
Reply to Bug: Wi-Fi Aware (NAN) Subscriber Mode: nwPath.availableInterfaces Does Not Include nan0 Interface After Successful Peer Connection
Thanks for your reply!We have successfully connected an iOS device with a non-iOS device via Wi-Fi Aware, and established multiple TCP connections. However, we still have a throughput issue: when the iOS device acts as a Subscriber, and sends an HTTP request over an already-established TCP connection to download resources from the non-iOS device, we observe slow download speeds — only around 20 MB/s. We compared iOS system logs and found: When the non-iOS device connects to iOS, the timeslot bitmap used is ff ff 00 00 ff ff. When iOS connects to iOS, all timeslots are used. Could this be the reason for the large difference in transmission rates? Is this caused by configuration, or what leads to the reduced timeslot allocation? Log 1: Non-iOS device connecting to iOS default 16:33:33.204715+0800 kernel wlan0:com.apple.p2p.nan0: Availability: map 0, channel 6 (20M), timeBmap: 1111 1111 1111 1111 0000 0000 0000 0000 1111 1111 1111 1111 ( ff ff 00 00 ff ff ) default 16:33:33.204792+0800 kernel wlan0:com.apple.p2p.nan0: Availability: map 1, channel 149 (80M), timeBmap: 1111 1111 1111 1111 0000 0000 0000 0000 1111 1111 1111 1111 ( ff ff 00 00 ff ff ) Log 2: iOS connecting to iOS default 17:49:12.767874+0800 kernel wlan0:com.apple.p2p: Availability: map 0, channel 6 (20M), timeBmap: 1111 1111 1111 1111
Mar ’26
Reply to Bug: Wi-Fi Aware (NAN) Subscriber Mode: nwPath.availableInterfaces Does Not Include nan0 Interface After Successful Peer Connection
To supplement: iOS connecting to iOS log``` default 17:49:12.767874+0800 kernel wlan0:com.apple.p2p: Availability: map 0, channel 6 (20M), timeBmap: 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 ( ff ff ff ff ff ff ff ff ) default 17:49:12.767894+0800 kernel wlan0:com.apple.p2p: Availability: map 1, channel 149 (80M), timeBmap: 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 ( ff ff ff ff ff ff ff ff )
Mar ’26
Reply to During the Wi-Fi Aware's pairing process, Apple is unable to recognize the follow-up PMF sent by Android.
Hi sengui. We attempted to pair an Android device (Galaxy S25) with the iOS Wi-Fi Aware Demo, but the process was unsuccessful. We received an "onPairingSetupFailed" callback without any specific error message. Could you share how you managed to successfully complete the pairing process between Android and iOS? Is there any other way to contact you? My email is wuhaibinaaron with 163mail suffix Thanks
Replies
Boosts
Views
Activity
Sep ’25
Reply to During the Wi-Fi Aware's pairing process, Apple is unable to recognize the follow-up PMF sent by Android.
@sengui
Replies
Boosts
Views
Activity
Sep ’25
Reply to Wi-Fi Aware between iOS 26 and Android device
HI sengui @sengui Could you explain the procedure for completing the pairing process between an Android and an iOS device? Additionally, we would appreciate it if you could provide the demo code for the Android side.
Replies
Boosts
Views
Activity
Sep ’25
Reply to Bug: Wi-Fi Aware (NAN) Subscriber Mode: nwPath.availableInterfaces Does Not Include nan0 Interface After Successful Peer Connection
Sorry for the typo earlier. To clarify: after connecting via Wi‑Fi Aware, we need to establish multiple additional NWConnection instances and send URLSession requests over the Wi‑Fi Aware network. However, we’re encountering a system "Nexus assignment error" when attempting to create NWConnections using the nan0 interface. Could you please demonstrate how to properly establish these extra NWConnections and send URLSession data through them?
Replies
Boosts
Views
Activity
Mar ’26
Reply to Bug: Wi-Fi Aware (NAN) Subscriber Mode: nwPath.availableInterfaces Does Not Include nan0 Interface After Successful Peer Connection
Thanks for your reply!We have successfully connected an iOS device with a non-iOS device via Wi-Fi Aware, and established multiple TCP connections. However, we still have a throughput issue: when the iOS device acts as a Subscriber, and sends an HTTP request over an already-established TCP connection to download resources from the non-iOS device, we observe slow download speeds — only around 20 MB/s. We compared iOS system logs and found: When the non-iOS device connects to iOS, the timeslot bitmap used is ff ff 00 00 ff ff. When iOS connects to iOS, all timeslots are used. Could this be the reason for the large difference in transmission rates? Is this caused by configuration, or what leads to the reduced timeslot allocation? Log 1: Non-iOS device connecting to iOS default 16:33:33.204715+0800 kernel wlan0:com.apple.p2p.nan0: Availability: map 0, channel 6 (20M), timeBmap: 1111 1111 1111 1111 0000 0000 0000 0000 1111 1111 1111 1111 ( ff ff 00 00 ff ff ) default 16:33:33.204792+0800 kernel wlan0:com.apple.p2p.nan0: Availability: map 1, channel 149 (80M), timeBmap: 1111 1111 1111 1111 0000 0000 0000 0000 1111 1111 1111 1111 ( ff ff 00 00 ff ff ) Log 2: iOS connecting to iOS default 17:49:12.767874+0800 kernel wlan0:com.apple.p2p: Availability: map 0, channel 6 (20M), timeBmap: 1111 1111 1111 1111
Replies
Boosts
Views
Activity
Mar ’26
Reply to Bug: Wi-Fi Aware (NAN) Subscriber Mode: nwPath.availableInterfaces Does Not Include nan0 Interface After Successful Peer Connection
To supplement: iOS connecting to iOS log``` default 17:49:12.767874+0800 kernel wlan0:com.apple.p2p: Availability: map 0, channel 6 (20M), timeBmap: 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 ( ff ff ff ff ff ff ff ff ) default 17:49:12.767894+0800 kernel wlan0:com.apple.p2p: Availability: map 1, channel 149 (80M), timeBmap: 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 1111 ( ff ff ff ff ff ff ff ff )
Replies
Boosts
Views
Activity
Mar ’26
Reply to Bug: Wi-Fi Aware (NAN) Subscriber Mode: nwPath.availableInterfaces Does Not Include nan0 Interface After Successful Peer Connection
Hi I have summarized some logs and related questions in case FB22454367 and look forward to your reply! Cheer
Replies
Boosts
Views
Activity
3w
Reply to Bug: Wi-Fi Aware (NAN) Subscriber Mode: nwPath.availableInterfaces Does Not Include nan0 Interface After Successful Peer Connection
Hi Does Wi-Fi Aware currently support the QUIC protocol? We have made attempts to modify the official demo to adopt QUIC, but all efforts have been unsuccessful. Thanks
Replies
Boosts
Views
Activity
2w