[GH-ISSUE #1379] Abort and connect flags used uninitialized #1181

New issue

Closed

opened 2026-02-28 01:28:53 +03:00 by kerem · 0 comments

kerem commented

2026-02-28 01:28:53 +03:00

Owner

Originally created by @abaskin on GitHub (Mar 28, 2022).
Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/1379

Basic Infos

Hardware

WiFimanager Branch/Release: Master

Esp8266/Esp32: ESP8266

Hardware: NodeMCU

Core Version: 2.4.0

Description

On object creation the abort and connect flags are not initialized. They are initialized by startConfigPortal() but not by startWebPortal(). As a result when startWebPortal() is called (an on demand portal for example), process() will fail with a "process loop abort" error if the abort flag happens to contain a non-zero value.

Originally created by @abaskin on GitHub (Mar 28, 2022). Original GitHub issue: https://github.com/tzapu/WiFiManager/issues/1379 ### Basic Infos #### Hardware WiFimanager Branch/Release: Master Esp8266/Esp32: ESP8266 Hardware: NodeMCU Core Version: 2.4.0 ### Description On object creation the abort and connect flags are not initialized. They are initialized by startConfigPortal() but not by startWebPortal(). As a result when startWebPortal() is called (an on demand portal for example), process() will fail with a "process loop abort" error if the abort flag happens to contain a non-zero value.