[Bug] Wifi selection issue

[beareogaming]

Pre-submission checklist

• I checked that no other Bug Report describing my problem exists.
• I am running the latest stable or prerelease firmware.
• My board is on the list of maintained boards.
• I accept that this issue may be closed if any of the above are found to be untrue.

Board

wemos lolin s3

Firmware version

1.4.0

Flashing method

web flash tool, stable full wipe

Describe what happened as precisely as possible.

after flash while selecting wifi and filling credentials, it assigned my password to a random wifi network and changes from the green connection icon to white arrow, on a completely random network. seems to ignore the specific wifi network im selecting

Describe what you expected to happen instead.

selecting intended wifi network and connecting

In as much detail as possible, describe the exact steps you took to make the problem appear.

flash, connect to wifi, attempt to configure wifi

Other remarks

No response

[beareogaming]

not sure if its still a "issue" but apon clearing my cache it seems to work again. wont close because im not sure if its a issue that could be mitigated

[beareogaming]

I’m trying to flash a modified firmware (adding a beep sequence to confirm transmitter function and completing the transmitter pinout). When flashing from v1.4.0 or any development branch, the Web UI behaves incorrectly: UI errors occur, password fields don’t mask input, and the random wifi selection issue happens.

I’m cloning the repo, installing requirements, and flashing both firmware and frontend—if I don’t flash the frontend, the Web UI errors out due to a missing filesystem.

As a workaround, I first flash via the web flasher, then re-flash my custom firmware on top of it. This restores normal Web UI behavior, but it’s tedious and shouldn’t be necessary.

[LucHeart]

the development branches and beta are always considered broken
you can just flash both app and filesystem (frontend) independently via platformio, no need to pre flash

as for the original issue, am not sure what could be going on here, 1.4.0 has been out for over a year.