On Windows, ciot_wifi_start() starts the underlying TCP interface, but ciot_wifi_stop() now returns CIOT_ERR_OK without actually stopping anything. This can leave the TCP/netif state running while callers believe Wi-Fi has stopped (and it hides the previous explicit NOT_SUPPORTED). Consider calling ciot_tcp_stop(base->tcp) (and updating status/state accordingly), or keep returning NOT_SUPPORTED if stop isn’t implemented on this platform.
CIOT_ERR_NULL_CHECK(self);
ciot_wifi_base_t *base = &self->base;
return ciot_tcp_stop(base->tcp);
Originally posted by @Copilot in #41 (comment)
On Windows, ciot_wifi_start() starts the underlying TCP interface, but ciot_wifi_stop() now returns CIOT_ERR_OK without actually stopping anything. This can leave the TCP/netif state running while callers believe Wi-Fi has stopped (and it hides the previous explicit NOT_SUPPORTED). Consider calling ciot_tcp_stop(base->tcp) (and updating status/state accordingly), or keep returning NOT_SUPPORTED if stop isn’t implemented on this platform.
Originally posted by @Copilot in #41 (comment)