Seeing this message when switching to an upgraded esp32 platform. ([142629][E][NetworkClient.cpp:323] setSocketOption(): fail on 0, errno: 9, "Bad file number")

[nPn-]

First, excellent library, and thank you very much for contributing it!!!

I did see this issue which had this message as part of it #140, but in that issue the requests failed and seemed to be memory related. I think I am ok with memory.
From my log:

--- Memory Report ---
Total PSRAM size: 8388608 bytes
Free Heap: 180356 bytes
Min Free Heap: 160900 bytes
Max Alloc Block: 106484 bytes
Remaining stack for task: 11972 bytes

I updated my platform to use the pio fork, mainly because I want to use a library that I think wants to use gcc 14 / gnu+23

Now I get the following message when pushing to RTDB and posting Messaging.
posting event: {"event_type":"on","event_time":1769146643000} <- this is my log messge
[142629][E][NetworkClient.cpp:323] setSocketOption(): fail on 0, errno: 9, "Bad file number"
[142637][E][NetworkClient.cpp:323] setSocketOption(): fail on 0, errno: 9, "Bad file number"
[142646][E][NetworkClient.cpp:323] setSocketOption(): fail on 0, errno: 9, "Bad file number"
[142654][E][NetworkClient.cpp:323] setSocketOption(): fail on 0, errno: 9, "Bad file number"
no error <- again this is my log indication that did not report an error

The data shows up in the database and the message is received, so I think everything is still working fine, it's just this message.
Is there anything I can do to fix this, or, post an issue (not sure which library is the source of the message)

Here is the relevant portion of my platformio.ini file

; platform = espressif32
; Use the PIOArduino fork for Arduino 3.x and modern GCC 14 support
platform = https://github.com/pioarduino/platform-espressif32/releases/download/53.03.11/platform-espressif32.zip
; platform_packages =
;     toolchain-xtensa-esp32s3@~14.2.0 ; Force 2026 toolchain version
framework = arduino
lib_deps = 
	mobizt/FirebaseClient@^2.2.5
	ArduinoOTA
	links2004/WebSockets@^2.7.2
	**bblanchon/ArduinoJson@^7.4.2**
monitor_speed = 115200
build_flags = 
	-D ARDUINO_USB_MODE=1
	-D ARDUINO_USB_CDC_ON_BOOT=1
	-DDEBUG_FIREBASE
	-std=gnu++23
build_unflags = 
	-std=gnu++11
	-std=gnu++17
board_build.filesystem = littlefs

[env:seeed_xiao_esp32s3_serial]
board = seeed_xiao_esp32s3

[mobizt]

That is the WiFIClientSecure (NetworkClientSecure) debug message.
It reports when you do something that related to working with socket that is currently closed or not yet open e.g. set timeout.

You should check its connection status to make sure it is connected to server before set the timeout or do something with socket via setting its options.

[nPn-]

I am posting this answer in case anyone else using this (awesome) library somehow hits this and thinks it a library issue.

It turns out this was an issue with NetworkClientSecure that was fixed in this PR. I found it after I came up with the same fix and did a last search of the issues on arduino-esp32 before submitting my own issue, which would have been marked a duplicate.

platform = https://github.com/pioarduino/platform-espressif32/releases/download/53.03.11/platform-espressif32.zip
was a bad choice. It has the checks that triggered the messages I posted, but not the fix to NetworkClientSecure.

I just upgraded to the latest available at the time of this writing and the messages are gone with out me having to hack NetworkClientSecure