Wi-Fi network not saved despite Blueprint convergence: Android Wi-Fi framework rejection

Android

When a Wi-Fi network is configured in a Blueprint but does not appear under Saved Networks on the device, the Blueprint may still show as fully converged in the Esper Console — leaving the device without the expected network connection.

Why this happens

Blueprint convergence confirms that the Esper Agent delivered the configuration to the device — it does not confirm that Android accepted it. The Android Wi-Fi framework validates network configurations independently, and if it rejects an addition (due to a duplicate entry, a malformed credential, or an internal framework error), it silently removes the configuration after repeated failed attempts. The Esper Agent has no way to override this Android-level rejection.

Steps to resolve

1. Confirm the Blueprint is converged, not just applied. In the Esper Console, go to Devices & Groups → [Device Name] → Blueprint and verify the status shows Converged. If the status is not Converged, resolve Blueprint sync issues first before continuing — a non-converged Blueprint is a separate problem from an Android framework rejection.
2. Check the Esper Agent logs for Wi-Fi framework errors. Connect the device to a computer via USB, then run the following command in a terminal:

   adb shell logcat -d -s EsperDPC WifiManager WifiNetworkSuggestion

   Look for repeated lines indicating failure to add or enable the network, followed by removal of the Wi-Fi configuration. These entries confirm the Android Wi-Fi framework is rejecting the configuration rather than the Esper Agent failing to send it.
3. Collect a bug report from the device. In the Esper Console, go to Devices & Groups → [Device Name], select Actions, then choose Bug Report. Wait for the report to generate and download it. The bug report contains full Android framework logs that identify exactly why the Wi-Fi framework is rejecting the configuration — this is required context for any further troubleshooting.
4. Re-apply the Blueprint. In the Esper Console, go to Devices & Groups, select the affected device or group, navigate to Blueprint, and click Re-apply. Wait for the Blueprint to converge again. Re-applying forces the Esper Agent to reattempt the Wi-Fi configuration push, which may succeed if the earlier rejection was caused by a transient Android framework state.
5. Manually add the Wi-Fi network as a temporary workaround. If re-applying the Blueprint does not restore the saved network, open Settings → Wi-Fi → Add Network directly on the device and enter the SSID, security type, and password. This restores connectivity while the root cause is investigated and does not affect Blueprint configuration.

Verify: On the device, open Settings → Wi-Fi → Saved Networks and confirm the network appears. In the Esper Console, go to Devices & Groups → [Device Name] → Device Info → Network and confirm the network is listed as connected. Both should reflect the saved network within a few minutes of a successful Blueprint re-application.

If this doesn't resolve it

If the Wi-Fi network still does not appear after re-applying the Blueprint, contact Esper Support with the following:

• The bug report downloaded in Step 3
• The Esper Agent version from Devices & Groups → [Device Name] → Device Info
• The device make, model, and Android version
• The number of devices affected and whether they share the same Blueprint and group
• The output of the adb logcat command from Step 2

--- **Improved title:** Wi-Fi network missing from Saved Networks despite Blueprint convergence

Still need help?

If your Wi-Fi networks aren't saving after Blueprint convergence due to Android framework rejection, submit a support ticket and include your Blueprint configuration, device logs showing the framework rejection error, and the Android version running on your devices.