Experiments with the ESP32 SoC from AZ-Delivery and the recommended IDE board manager ESP32 Dev Module cause problems when you want to make a WiFi STA(ion) or an AP (Access Point) from the ESP32 module.
It appears that uploading the sketch leads to an error message in the IDE. The message is that the upload is blocked due to time out of the WDT Whatch Dog Timer.

Using board from AZ-Delivery
Type ESP32 Development Board Node SoC DevKit C V2 with WLAN/WIFIwith UART CP2102
Using recommended Board manager -ESP32 Dev Module- from Espressif.

Back Ground
The ESP-IDF has support for multiple types of watchdogs, with the two main ones being:
– The Interrupt Watchdog Timer and the
– Task Watchdog Timer (TWDT).

The Interrupt Watchdog Timer and the TWDT could be enabled using Project Configuration Menu, however the TWDT can also be enabled during runtime. The Interrupt Watchdog is responsible for detecting instances where FreeRTOS task switching is blocked for a prolonged period of time. The TWDT is responsible for detecting instances of tasks running without yielding for a prolonged period.
For moere information:
https://docs.espressif.com/projects/esp-idf/en/latest/esp32s3/api-reference/system/wdts.html

Solution
Change IDE board manager from:
– ESP32 Dev Module –
to the board manager
– DOIT ESP32 DEVKIT V1 –
the problem same to solved.

It is clear, as is also clear from the Espressif documentation, that the recommended Espressif board manager – ESP32 Dev Module – does not disable the Watch Dog Timer. Not even if you issue the command esp_task_wdt_deinit(); . If you want to disable the Watch Dog Timer, you have to do it in the board manager itself, as recommended by others who have encountered the same problem. The only tricky part is finding out where the IDE has stored the board manager.

Unlike many others who have encountered the same problem, my solution is very simple: change the board manager and make sure that the program component that is needed to log in to the home router is not included as a subroutine in the SetUp loop, but directly in the SetUp loop. Included as a subroutine, the WachDog timer is apparently still in the way.
It is a temporary solution, but it works.