From 79ae4d12a6ce96b41fa308018e004607e6e16068 Mon Sep 17 00:00:00 2001 From: bahdotsh Date: Thu, 5 Nov 2026 19:29:17 +0530 Subject: [PATCH] docs(bindings): changelog entry for the Wi-Fi Direct enable fix in #686 #686 fixed two things. Enabling Wi-Fi Direct stopped the manager only while RUNNING, which shipped in 0.31.0, so it gets an entry. The stranded listener after a throw, and #683's bind-before-STARTING and accept timeout fixes, all repair code #681 added after 0.31.0, so they reached no user and get one clause on #681's entry instead. --- CHANGELOG.md | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index e1779e99..15b09b05 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -145,7 +145,18 @@ archived by series under [docs/changelog/](docs/changelog/); see the at all. A listener that cannot take 8988 now binds a free port and advertises that one. A group's clients can only dial 8988, so an app without it never creates a Wi-Fi Direct group and joins instead. A start - that cannot bind any port now fails rather than advertising one. + that cannot bind any port now fails rather than advertising one, and a + start that fails at any point leaves nothing running. + +- **Enabling Wi-Fi Direct on Android no longer starts it a second time over + a start in progress.** `enableTransport('wifiDirect')` stopped the manager + first only when it was running, while the Internet branch also stopped it + when it was starting. An enable that found a start still in progress, or a + start that had thrown partway and left the manager starting, started it + again over what the first start had brought up: a second broadcast receiver + over the first, and a second listener for the port the first one held. The + Wi-Fi Direct branch now stops a starting manager as the Internet branch + does. - **Frames for a Bluetooth neighbor no longer leave through a relay that cannot reach it.** The application dispatch sent a message for a recipient