After connected, AutoConnect menu performs but no happens.
</a>
</li>
<liclass="md-nav__item">
<ahref="#after-updating-to-autoconnect-v100-established-aps-disappear-from-open-ssids-with-esp32"title=" After updating to AutoConnect v1.0.0, established APs disappear from Open SSIDs with ESP32."class="md-nav__link">
After updating to AutoConnect v1.0.0, established APs disappear from Open SSIDs with ESP32.
</a>
</li>
<liclass="md-nav__item">
@ -964,6 +971,13 @@
After connected, AutoConnect menu performs but no happens.
</a>
</li>
<liclass="md-nav__item">
<ahref="#after-updating-to-autoconnect-v100-established-aps-disappear-from-open-ssids-with-esp32"title=" After updating to AutoConnect v1.0.0, established APs disappear from Open SSIDs with ESP32."class="md-nav__link">
After updating to AutoConnect v1.0.0, established APs disappear from Open SSIDs with ESP32.
</a>
</li>
<liclass="md-nav__item">
@ -1175,6 +1189,13 @@
<p>If you can access the <strong>AutoConnect root path</strong> as http://ESP8266IPADDRESS/_ac from browser, probably the sketch uses <em>ESP8266WebServer::handleClient()</em> without <ahref="api.html#handlerequest"><em>AutoConnect::handleRequest()</em></a>.<br/>
For AutoConnect menus to work properly, call <ahref="api.html#handlerequest"><em>AutoConnect::handleRequest()</em></a> after <em>ESP8266WebServer::handleClient()</em> invoked, or use <ahref="api.html#handleclient"><em>AutoConnect::handleClient()</em></a>. <ahref="api.html#handleclient"><em>AutoConnect::handleClient()</em></a> is equivalent <em>ESP8266WebServer::handleClient</em> combined <ahref="api.html#handlerequest"><em>AutoConnect::handleRequest()</em></a>.</p>
<p>See also the explanation <ahref="basicusage.html#esp8266webserver-hosted-or-parasitic">here</a>.</p>
<h2id="after-updating-to-autoconnect-v100-established-aps-disappear-from-open-ssids-with-esp32"><iclass="fa fa-question-circle"></i> After updating to AutoConnect v1.0.0, established APs disappear from Open SSIDs with ESP32.<aclass="headerlink"href="#after-updating-to-autoconnect-v100-established-aps-disappear-from-open-ssids-with-esp32"title="Permanent link">¶</a></h2>
<p>Since AutoConnect v1.0.0 for ESP32, the storage location in the flash of established credentials has moved from EEPROM to Preferences. After You update AutoConnect to v1.0.0, past credentials saved by v0.9.12 earlier will <em>not be accessible</em> from the AutoConnect menu - <strong>Open SSIDs</strong>. You need to transfer once the stored credentials from the EEPROM area to the Preferences area.</p>
<p>You can migrate the past saved credentials using <ahref="https://github.com/Hieromon/AutoConnect/tree/master/examples/CreditMigrate"><strong>CreditMigrate.ino</strong></a> which the examples folder contains.</p>
<divclass="admonition info">
<pclass="admonition-title">Needs to Arduino core for ESP32 1.0.2 or earlier</p>
<p>EEPROM area with arduino-esp32 core <strong>1.0.3</strong> has moved from <strong>partition</strong> to the <strong>nvs</strong>. CreditMigrate.ino requires arduino-esp32 core <strong>1.0.2</strong> or earlier to migrate saved credentials.</p>
</div>
<h2id="an-esp8266ap-as-softap-was-connected-but-captive-portal-does-not-start"><iclass="fa fa-question-circle"></i> An esp8266ap as SoftAP was connected but Captive portal does not start.<aclass="headerlink"href="#an-esp8266ap-as-softap-was-connected-but-captive-portal-does-not-start"title="Permanent link">¶</a></h2>
<p>Captive portal detection could not be trapped. It is necessary to disconnect and reset ESP8266 to clear memorized connection data in ESP8266. Also, It may be displayed on the smartphone if the connection information of esp8266ap is wrong. In that case, delete the connection information of esp8266ap memorized by the smartphone once.</p>
<h2id="connection-lost-immediately-after-establishment-with-ap"><iclass="fa fa-question-circle"></i> Connection lost immediately after establishment with AP<aclass="headerlink"href="#connection-lost-immediately-after-establishment-with-ap"title="Permanent link">¶</a></h2>
@ -5,6 +5,15 @@ For AutoConnect menus to work properly, call [*AutoConnect::handleRequest()*](ap
See also the explanation [here](basicusage.md#esp8266webserver-hosted-or-parasitic).
## <iclass="fa fa-question-circle"></i> After updating to AutoConnect v1.0.0, established APs disappear from Open SSIDs with ESP32.
Since AutoConnect v1.0.0 for ESP32, the storage location in the flash of established credentials has moved from EEPROM to Preferences. After You update AutoConnect to v1.0.0, past credentials saved by v0.9.12 earlier will *not be accessible* from the AutoConnect menu - **Open SSIDs**. You need to transfer once the stored credentials from the EEPROM area to the Preferences area.
You can migrate the past saved credentials using [**CreditMigrate.ino**](https://github.com/Hieromon/AutoConnect/tree/master/examples/CreditMigrate) which the examples folder contains.
!!! info "Needs to Arduino core for ESP32 1.0.2 or earlier"
EEPROM area with arduino-esp32 core **1.0.3** has moved from **partition** to the **nvs**. CreditMigrate.ino requires arduino-esp32 core **1.0.2** or earlier to migrate saved credentials.
## <iclass="fa fa-question-circle"></i> An esp8266ap as SoftAP was connected but Captive portal does not start.
Captive portal detection could not be trapped. It is necessary to disconnect and reset ESP8266 to clear memorized connection data in ESP8266. Also, It may be displayed on the smartphone if the connection information of esp8266ap is wrong. In that case, delete the connection information of esp8266ap memorized by the smartphone once.
Hieromon Ikasamo
5 years ago
